teams
Overview
Name | teams |
Type | Resource |
Id | pagerduty.teams.teams |
Fields
Name | Datatype | Description |
---|---|---|
id | string | |
name | string | The name of the team. |
description | string | The description of the team. |
_type | string | The type of object being created. |
html_url | string | a URL at which the entity is uniquely displayed in the Web app |
parent | object | |
self | string | the API show URL at which the object is accessible |
summary | string | A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name , though it is not intended to be an identifier. |
type | string | A string that determines the schema of the object. This must be the standard name for the entity, suffixed by _reference if the object is a reference. |
Methods
Name | Accessible by | Required Params | Description |
---|---|---|---|
get_team | SELECT | id | Get details about an existing team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.read |
list_teams | SELECT | List teams of your PagerDuty account, optionally filtered by a search query. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.read | |
create_team | INSERT | data__team | Create a new Team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.write |
delete_team | DELETE | id | Remove an existing team. Succeeds only if the team has no associated Escalation Policies, Services, Schedules and Subteams. All associated unresovled incidents will be reassigned to another team (if specified) or will loose team association, thus becoming account-level (with visibility implications). Note that the incidents reassignment process is asynchronous and has no guarantee to complete before the API call return. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.write |
_get_team | EXEC | id | Get details about an existing team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.read |
_list_teams | EXEC | List teams of your PagerDuty account, optionally filtered by a search query. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.read | |
update_team | EXEC | id, data__team | Update an existing team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the API Concepts Document Scoped OAuth requires: teams.write |