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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
PagerDuty

PagerDuty Incidents API

An incident represents a problem or an issue that needs to be addressed and resolved. Incidents trigger on a service, which prompts notifications to go out to on-call responders per the service's escalation policy.

Documentation Provider Profile APIs.io OpenAPI GitHub

PagerDuty Incidents 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 Incidents. 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 26 operations across 18 paths, and defines 75 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.

26 operations 18 paths 75 schemas 12 GET7 POST7 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
Contact
PagerDuty Support
Resource Areas
1

Authentication & Security 1

PagerDuty Incidents 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 26

Across 18 paths, the API surfaces 26 operations — 12 GET, 7 POST, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Incidents 26

An incident represents a problem or an issue that needs to be addressed and resolved. Incidents trigger on a service, which prompts notifications to go out to on-call responders p…

GET
/incidents
PagerDuty List incidents
listIncidents 17 params → 200400401402403429
PUT
/incidents
PagerDuty Manage incidents
updateIncidents 6 params body → 200400401403413429
POST
/incidents
PagerDuty Create an Incident
createIncident 3 params body → 201400401403429
GET
/incidents/{id}
PagerDuty Get an incident
getIncident 4 params → 200400401403404429
PUT
/incidents/{id}
PagerDuty Update an incident
updateIncident 4 params body → 200401403404429
GET
/incidents/{id}/alerts
PagerDuty List alerts for an incident
listIncidentAlerts 10 params → 200400401403429
PUT
/incidents/{id}/alerts
PagerDuty Manage alerts
updateIncidentAlerts 7 params body → 200400401403413429
GET
/incidents/{id}/alerts/{alert_id}
PagerDuty Get an alert
getIncidentAlert 4 params → 200400401403404429
PUT
/incidents/{id}/alerts/{alert_id}
PagerDuty Update an alert
updateIncidentAlert 5 params body → 200401403404429
PUT
/incidents/{id}/business_services/{business_service_id}/impacts
PagerDuty Manually change an Incident's Impact on a Business Service.
putIncidentManualBusinessServiceAssociation 3 params body → 200400401403422429
GET
/incidents/{id}/business_services/impacts
PagerDuty List Business Services impacted by the given Incident
getIncidentImpactedBusinessServices 2 params → 200400401403422429
GET
/incidents/{id}/custom_fields/values
PagerDuty Get Custom Field Values
getIncidentFieldValues 1 param → 200403404500
PUT
/incidents/{id}/custom_fields/values
PagerDuty Update Custom Field Values
setIncidentFieldValues 1 param body → 201403404500
GET
/incidents/{id}/log_entries
PagerDuty List log entries for an incident
listIncidentLogEntries 11 params → 200400401403404429
PUT
/incidents/{id}/merge
PagerDuty Merge incidents
mergeIncidents 4 params body → 200400401403404429
GET
/incidents/{id}/notes
PagerDuty List notes for an incident
listIncidentNotes 3 params → 200400401403404429
POST
/incidents/{id}/notes
PagerDuty Create a note on an incident
createIncidentNote 4 params body → 200400401403404429
GET
/incidents/{id}/outlier_incident
PagerDuty Get Outlier Incident
getOutlierIncident 5 params → 200400403404429500
GET
/incidents/{id}/past_incidents
PagerDuty Get Past Incidents
getPastIncidents 5 params → 200400403404500
GET
/incidents/{id}/related_incidents
PagerDuty Get Related Incidents
getRelatedIncidents 4 params → 200400403404429500
POST
/incidents/{id}/responder_requests
PagerDuty Create a responder request for an incident
createIncidentResponderRequest 4 params body → 200400401403404429
POST
/incidents/{id}/snooze
PagerDuty Snooze an incident
createIncidentSnooze 4 params body → 201400401403404429
POST
/incidents/{id}/status_updates
PagerDuty Create a status update on an incident
createIncidentStatusUpdate 4 params body → 200400401403404429
GET
/incidents/{id}/status_updates/subscribers
PagerDuty List Notification Subscribers
getIncidentNotificationSubscribers 2 params → 200400401403422429
POST
/incidents/{id}/status_updates/subscribers
PagerDuty Add Notification Subscribers
createIncidentNotificationSubscribers 2 params body → 200400401403422
POST
/incidents/{id}/status_updates/unsubscribe
PagerDuty Remove Notification Subscriber
removeIncidentNotificationSubscribers 2 params body → 200401403404422

Schemas 75

The contract defines 75 schemas that model the data the API accepts and returns. The most detailed are CustomFieldsFieldValue (8 properties), Notification (8 properties), IncidentsRespondersReference (7 properties), NotificationSubscriptionWithContext (6 properties). Each schema is shown below with its type and property counts.

EscalationRule
object
4 properties 2 required
NotifyLogEntry
ResolveLogEntry
IncidentNote
object
5 properties 1 required
Impact
object
5 properties
Notification
object
8 properties
CustomFieldsFieldValue
object
8 properties 8 required
Context
object
4 properties 1 required
ReachTriggerLimitLogEntry
IncidentReference
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
NotificationSubscriber
object
A reference of a subscriber entity.
2 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
AlertCount
object
3 properties
ExhaustEscalationPathLogEntry
PriorityReference
ConferenceBridge
object
2 properties
IncidentUrgencyRule
User
TimeBasedAlertGroupingConfiguration
object
The configuration for Time Based Alert Grouping
1 property
LogEntry
UrgencyChangeLogEntry
Alert
UnacknowledgeLogEntry
CustomFieldsEditableFieldValue
UserReference
NotificationSubscriptionWithContext
object
An object describing the relationship of a NotificationSubscriber and a NotificationSubscribable with additional context on status of subscription attempt.
6 properties
AcknowledgeLogEntry
CursorPagination
object
2 properties 2 required
EscalationPolicy
Acknowledgement
object
2 properties 2 required
EscalationTargetReference
RepeatEscalationPathLogEntry
AgentReference
AssignLogEntry
TriggerLogEntry
ResponderRequest
object
5 properties
StatusUpdate
object
6 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
RelatedIncidentServiceDependencyBase
object
3 properties
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
ScheduledAction
object
3 properties 3 required
IncidentsRespondersReference
object
7 properties
RelatedIncidentMachineLearningRelationship
object
The data for a type of relationship where the Incident is related due to our machine learning algorithm.
2 properties
DelegateLogEntry
Incident
IncidentUrgencyType
object
2 properties
ContactMethodReference
NotificationSubscriberWithContext
object
A reference of a subscriber entity with additional subscription context.
4 properties
RelatedIncidentServiceDependencyRelationship
object
The data for a type of relationship where the Incident is related due to Business or Technical Service dependencies. Both dependentservices and supportingservi…
2 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-incidents-api-openapi.yml Raw ↑

Other APIs PagerDuty publishes across the network.

PagerDuty Events API
AE Profile APIs.io
PagerDuty Abilities API
AE Profile APIs.io
PagerDuty Add-Ons API
AE Profile APIs.io
PagerDuty Alert Grouping Settings API
AE Profile APIs.io
PagerDuty Analytics API
AE Profile APIs.io
PagerDuty Audit API
AE Profile APIs.io
PagerDuty Automation Actions API
AE Profile APIs.io
PagerDuty Business Services API
AE Profile APIs.io
PagerDuty Change Events API
AE Profile APIs.io
PagerDuty Change Tags API
AE Profile APIs.io
PagerDuty Custom Fields API
AE Profile APIs.io
PagerDuty Escalation Policies API
AE Profile APIs.io
#Incidents
← Back to P APIs
API Details
ID
pagerduty:pagerduty-incidents-api
Base URL
https://api.pagerduty.com
Docs
https://developer.pagerduty.com/api-reference/
Provider
PagerDuty
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=pagerduty-incidents-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/pagerduty-incidents-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of PagerDuty Incidents 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.