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 Extensions API

Extensions are representations of Extension Schema objects that are attached to Services.

PagerDuty Extensions 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 Extensions. 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 6 operations across 3 paths, and defines 73 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.

6 operations 3 paths 73 schemas 1 DELETE2 GET2 POST1 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 Extensions 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 6

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

Extensions 6

Extensions are representations of Extension Schema objects that are attached to Services.

GET
/extensions
PagerDuty List extensions
listExtensions 9 params → 200400401403
POST
/extensions
PagerDuty Create an extension
createExtension 2 params body → 201400401402403
GET
/extensions/{id}
PagerDuty Get an extension
getExtension 4 params → 200400401403404
DELETE
/extensions/{id}
PagerDuty Delete an extension
deleteExtension 3 params → 204401403404
PUT
/extensions/{id}
PagerDuty Update an extension
updateExtension 3 params body → 200401402403404
POST
/extensions/{id}/enable
PagerDuty Enable an extension
enableExtension 3 params → 200400401403404

Schemas 73

The contract defines 73 schemas that model the data the API accepts and returns. The most detailed are WebhooksV1IncidentData (15 properties), Notification (8 properties), IncidentsRespondersReference (7 properties), WebhooksV1Service (5 properties). Each schema is shown below with its type and property counts.

EscalationRule
object
4 properties 2 required
OutboundIntegrationReference
NotifyLogEntry
ResolveLogEntry
Notification
object
8 properties
Context
object
4 properties 1 required
ReachTriggerLimitLogEntry
IncidentReference
ExtensionSchemaReference
Team
Priority
Service
IncidentBody
object
1 property 1 required
NotificationRuleReference
ContentBasedAlertGroupingConfiguration
object
The configuration for Content Based Alert Grouping
4 properties
Channel
object
Polymorphic object representation of the means by which the action was channeled. Has different formats depending on type, indicated by channel[type]. Will be…
5 properties 1 required
ResolveReason
object
2 properties
LogEntryReference
ResponderRequestTargetReference
object
4 properties
FlexibleTimeWindowIntelligentAlertGroupingConfig
object
The configuration for Intelligent Alert Grouping. Note that this configuration is only available for certain plans.
2 properties
AcknowledgerReference
Assignment
object
2 properties 2 required
ReachAckLimitLogEntry
IntegrationReference
TeamReference
WebhooksV1Message
object
A message containing information about a single PagerDuty action.
4 properties
AlertCount
object
3 properties
Extension
ExhaustEscalationPathLogEntry
ConferenceBridge
object
2 properties
IncidentUrgencyRule
User
TimeBasedAlertGroupingConfiguration
object
The configuration for Time Based Alert Grouping
1 property
LogEntry
UrgencyChangeLogEntry
WebhookIncidentAction
Action
object
A message containing information about a single PagerDuty action.
3 properties
UnacknowledgeLogEntry
Webhook
object
Information about the configured webhook.
5 properties
UserReference
WebhooksV1IncidentData
object
The incident details at the time of the state change.
15 properties
WebhooksV1Service
object
The service on which the incident occurred.
5 properties
AcknowledgeLogEntry
EscalationPolicy
Acknowledgement
object
2 properties 2 required
EscalationTargetReference
RepeatEscalationPathLogEntry
AgentReference
AssignLogEntry
TriggerLogEntry
ResponderRequest
object
5 properties
AnnotateLogEntry
AlertGroupingParameters
object
Defines how alerts on this service will be automatically grouped into incidents. Note that the alert grouping features are available only on certain plans. To…
2 properties
SupportHours
object
5 properties
AddonReference
WebhookObject
AutoPauseNotificationsParameters
object
Defines how alerts on this service are automatically suspended for a period of time before triggering, when identified as likely being transient. Note that aut…
2 properties
WebhooksV1AssignedTo
object
2 properties
ScheduledAction
object
3 properties 3 required
IncidentsRespondersReference
object
7 properties
DelegateLogEntry
Incident
IncidentUrgencyType
object
2 properties
ContactMethodReference
WebhooksV1AssignedToUser
object
The user assigned to the incident.
4 properties
Reference
EscalateLogEntry
ServiceReference
SnoozeLogEntry
EscalationPolicyReference
IncidentAction
object
An incident action is a pending change to an incident that will automatically happen at some future time.
3 properties 2 required
Pagination
object
4 properties
Tag

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagerduty-extensions-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 Extensions 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.