PagerDuty

Get aggregated incident metrics across the account. Filter by date range, urgency, service, or team. Returns MTTA, MTTR, incident counts.

Get aggregated metrics broken down by service. Filter by date range, urgency, service, or team. Returns per-service MTTA, MTTR, incident counts.

List escalation policies with optional filters. Escalation policies define who to notify and in what order. Supports pagination.

Get an escalation policy by ID. Returns full policy details including escalation rules and targets.

Create an escalation policy. Requires name and escalation_rules with targets (users/schedules) and delays. Use list_users or list_schedules to find target IDs.

Update an escalation policy. Change name, description, rules, or loop count.

Delete an escalation policy by ID. This is permanent. Ensure no services reference this policy first.

List incidents with optional filters for status, urgency, service, date range. Supports pagination via offset/limit.

Get a specific incident by ID. Returns full incident details including status, assignments, and priority.

Create a new incident. Requires title and service_id. Use list_services to find valid service IDs. Optionally set urgency, priority, and assignments.

Update an incident. Change status (acknowledge/resolve), urgency, priority, or reassign. Use list_priorities for valid priority IDs.

List notes on an incident. Notes are timestamped comments added by responders during incident lifecycle.

Add a note to an incident. Notes help document incident response activities and findings.

List alerts for an incident. Alerts are the underlying triggers that created or were grouped into the incident.

List log entries for an incident. Shows the timeline of actions taken during incident response.

List priority levels configured in PagerDuty. Priorities are used when creating or updating incidents.

List tags with optional name filter. Tags can be attached to users, teams, and escalation policies for organization.

Create a new tag. Tags help organize users, teams, and escalation policies.

List log entries across the account. Log entries record all actions in PagerDuty (triggers, acknowledgements, escalations, etc.).

List maintenance windows. Maintenance windows temporarily disable incident creation for specified services.

Get a maintenance window by ID. Returns full details including services and time range.

Create a maintenance window. Temporarily disables incident creation for specified services during the time range.

Update a maintenance window. Change time range, description, or services.

Delete a maintenance window by ID. This is permanent and cannot be undone.

List audit records across the account. Tracks changes to all PagerDuty resources for compliance and security review.

List who is currently on-call. Filter by schedule, escalation policy, user, or time range. Use to find current responders.

List on-call schedules with optional name filter. Schedules define who is on-call at any given time. Supports pagination.

Get a schedule by ID with rendered on-call entries. Optionally specify since/until for the rendered time range.

Create an on-call schedule. Requires name, time_zone, and schedule_layers. Each layer defines a rotation with users, start time, and turn length.

Update a schedule. Change name, description, time zone, or schedule layers.

Delete a schedule by ID. This is permanent. Ensure no escalation policies reference this schedule first.

List services with optional filters. Services represent applications or components that generate incidents. Supports pagination via offset/limit.

Get a specific service by ID. Returns full service details including escalation policy and alert settings.

Create a new service. Requires name and escalation_policy_id. Use list_escalation_policies to find valid IDs.

Update a service. Change name, description, escalation policy, or alert settings.

Delete a service by ID. This is permanent and cannot be undone. All associated incidents will remain.

List teams with optional name filter. Teams group users for incident assignment and escalation. Supports pagination.

Get a specific team by ID. Returns team details including parent team relationship.

Create a new team. Requires a name. Optionally set description and parent team for nesting.

Update a team. Change name, description, or parent team.

Delete a team by ID. This is permanent. Reassign users and escalation policies before deleting.

List users with optional filters by name, email, or team. Supports pagination via offset/limit.

Get a specific user by ID. Returns full user details including role, teams, and contact methods.

Create a new user. Requires name and email. Optionally set role, time zone, and job title.

Update a user. Change name, email, role, time zone, or other profile fields.

Delete a user by ID. This is permanent. The user must not be on-call or have pending incidents.

Validate PagerDuty credentials by testing API access. Used during credential setup to verify authentication is working correctly.