PagerDuty REST API

Alert history

• Additive

  Add ServiceNow enrichment integration API endpoints

  Jul 8, 2026, 9:01 PM

  A new "Enrichment Integrations" API group has been added to manage ServiceNow CMDB integrations with PagerDuty. This includes new endpoints for creating and managing ServiceNow integrations, tables, and credentials, plus new request/response schemas and path parameters. All features are in early access and purely additive — existing integrations are unaffected.

• Additive

  Add Enrichment Schemas API for event contextual data

  Jul 8, 2026, 8:00 PM

  PagerDuty has added a new "Enrichment Schemas" API section enabling queryable data tables to add context to incoming events through Event Enrichment. This includes new endpoints to create, list, update, and delete enrichment schemas and records, along with CSV upload capabilities. The feature is marked as Early Access and does not affect existing APIs.

• Additive

  Add calendar feed URLs and regeneration endpoint

  Jul 8, 2026, 3:00 PM

  Adds two new response fields http_cal_url and web_cal_url to user objects, a new optional include[]=calendar_urls query parameter for retrieving them, and a new POST /users/{id}/regenerate_private_url_key endpoint to rotate calendar feed credentials. These are purely additive changes that do not affect existing functionality.

• Additive

  Add Event Enrichments API endpoints

  Jul 6, 2026, 7:00 PM

  PagerDuty introduces a new Event Enrichments API for managing contextual data enrichment rules on events. This is marked as Early Access. New endpoints enable creating, reading, updating, deleting, and managing associations and rules for event enrichments across services and event orchestrations.

• Informational

  Update Analytics endpoint descriptions for data availability

  Jun 12, 2026, 11:00 AM

  Multiple Analytics API endpoint descriptions were updated to clarify data availability timelines. The phrase "Analytics data is updated periodically. It takes up to 24 hours before new incidents appear" was replaced with "Data availability reflects pipeline processing cycles and is generally within 24 hours under normal conditions" across 8 endpoints. These are documentation-only changes that do not alter API behavior or contract.

• Informational

  Clarified recurrence rule documentation for schedule events

  Jun 11, 2026, 11:00 PM

  Documentation for the shifts_per_member and recurrence fields in schedule event schemas has been expanded to clarify constraints and limitations in the web UI editor. These changes document existing API behavior and UI limitations but do not alter API functionality or requirements.

• Additive

  Add IP allow list audit records endpoint

  Jun 8, 2026, 6:00 PM

  Adds a new endpoint GET /ip_allow_lists/{id}/audit/records to retrieve audit records for IP allow lists. This is an Early Access feature that extends the existing Audit API capability to IP allow lists and does not affect existing functionality.

• Additive

  Add optional query params and response field to schedule endpoints

  Jun 4, 2026, 6:00 PM

  Two schedule list endpoints now accept optional query parameters team_ids, query, and offset_total. The v3 schedule list response also adds a new html_url field to schedule objects. These are purely additive changes that do not break existing integrations.

• Additive

  Add Recommendations API for Event Orchestrations

  Jun 1, 2026, 7:00 PM

  PagerDuty added a new Recommendations API section with four new endpoints to manage AI-generated rule suggestions for Event Orchestrations: list recommended rules, accept rules, dismiss rules with feedback, and delete accepted rules. This is purely additive functionality with new OAuth scopes recommendations.read and recommendations.write.

• Additive

  Add IP Allow Lists API (Early Access)

  May 26, 2026, 5:00 PM

  PagerDuty added a new IP Allow Lists API group with three endpoints to manage account-level IP allow lists. This is marked as Early Access and requires the X-EARLY-ACCESS: ip-allow-lists header; it's fully additive and cannot break existing integrations.

• Breaking

  Schedules_v3 Early Access header requirement removed (GA promotion)

  May 18, 2026, 3:00 PM

  The X-EARLY-ACCESS: flexible-schedules-early-access required header parameter has been removed from all Schedules_v3 endpoints, and the "Early Access" warning notices have been stripped from all endpoint descriptions. This means the API is no longer in early access — clients that were conditionally sending this header no longer need to, but more importantly, clients that were not sending it (because the API was gated) can now call these endpoints freely. However, if any server-side enforcement still exists in the opposite direction (rejecting the old header), existing integrations that send it would break; treat this as a potentially breaking change for existing early-access integrations.

• Additive

  Add escalation_rule_assignment_strategies to enum

  May 15, 2026, 6:15 PM

  A new enum value escalation_rule_assignment_strategies has been added to an enum field. This is purely additive and does not break existing integrations that use the previous enum values (services, teams, targets).