How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PagerDuty Teams API

A team is a collection of Users and Escalation Policies that represent a group of people within an organization.

PagerDuty Teams API is one of 38 APIs that PagerDuty publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Team. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, and an AsyncAPI specification.

This API exposes 14 operations across 8 paths, and defines 12 schemas. It is described by OpenAPI 3.0.2, at version 2.0.0.

Requests are made against a single base URL, https://api.pagerduty.com.

14 operations 8 paths 12 schemas 3 DELETE5 GET3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
2.0.0
Base URL
https://api.pagerduty.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

PagerDuty Teams API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_key). By default, every request must be authenticated.

  • api_key — The API Key with format Token token=

Paths & Operations 14

Across 8 paths, the API surfaces 14 operations — 3 DELETE, 5 GET, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Teams 14

A team is a collection of Users and Escalation Policies that represent a group of people within an organization.

POST
/teams
PagerDuty Create a team
createTeam 2 params body → 201400401402403429
GET
/teams
PagerDuty List teams
listTeams 6 params → 200400401402403429
GET
/teams/{id}
PagerDuty Get a team
getTeam 4 params → 200400401402403404429
DELETE
/teams/{id}
PagerDuty Delete a team
deleteTeam 4 params → 204401402403429
PUT
/teams/{id}
PagerDuty Update a team
updateTeam 3 params body → 200401402403404429
GET
/teams/{id}/audit/records
PagerDuty List audit records for a team
listTeamsAuditRecords 7 params → 200400401402403404429500
DELETE
/teams/{id}/escalation_policies/{escalation_policy_id}
PagerDuty Remove an escalation policy from a team
deleteTeamEscalationPolicy 4 params → 204400401402403404429
PUT
/teams/{id}/escalation_policies/{escalation_policy_id}
PagerDuty Add an escalation policy to a team
updateTeamEscalationPolicy 4 params → 204400401402403404429
GET
/teams/{id}/members
PagerDuty List members of a team
listTeamUsers 7 params → 200400401403404429
GET
/teams/{id}/notification_subscriptions
PagerDuty List Team Notification Subscriptions
getTeamNotificationSubscriptions 2 params → 200400401403404429
POST
/teams/{id}/notification_subscriptions
PagerDuty Create Team Notification Subscriptions
createTeamNotificationSubscriptions 2 params body → 200400401403422
POST
/teams/{id}/notification_subscriptions/unsubscribe
Unsubscribe the given Team from Notifications on the matching Subscribable entities. Scoped OAuth requires: subscribers.write
removeTeamNotificationSubscriptions 2 params body → 200401403404422
DELETE
/teams/{id}/users/{user_id}
PagerDuty Remove a user from a team
deleteTeamUser 4 params → 204400401402403404429
PUT
/teams/{id}/users/{user_id}
PagerDuty Add a user to a team
updateTeamUser 4 params body → 204400401402403404429

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are AuditRecord (9 properties), NotificationSubscriptionWithContext (6 properties), NotificationSubscription (5 properties), Pagination (4 properties). Each schema is shown below with its type and property counts.

NotificationSubscription
object
An object describing the relationship of a NotificationSubscriber and a NotificationSubscribable.
5 properties
AuditMetadata
object
1 property
UserReference
Team
NotificationSubscriptionWithContext
object
An object describing the relationship of a NotificationSubscriber and a NotificationSubscribable with additional context on status of subscription attempt.
6 properties
CursorPagination
object
2 properties 2 required
AuditRecord
object
An Audit Trail record
9 properties 5 required
Reference
AuditRecordResponseSchema
NotificationSubscribable
object
A reference of a subscribable entity.
2 properties
Pagination
object
4 properties
Tag

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagerduty-teams-api-openapi.yml Raw ↑

Other APIs PagerDuty publishes across the network.

PagerDuty Events API
PagerDuty Abilities API
PagerDuty Add-Ons API
PagerDuty Alert Grouping Settings API
PagerDuty Analytics API
PagerDuty Audit API
PagerDuty Automation Actions API
PagerDuty Business Services API
PagerDuty Change Events API
PagerDuty Change Tags API
PagerDuty Custom Fields API
PagerDuty Escalation Policies API
Where this information came from

This is an independent, third-party profile of PagerDuty Teams API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.