{"files":{"SKILL.md":"---\nname: pagerduty-api\ndescription: \"PagerDuty API skill. Use when working with PagerDuty for {entity_type}, abilities, addons. Covers 420 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# PagerDuty API\nAPI version: 2.0.0\n\n## Auth\nApiKey Authorization in header\n\n## Base URL\nhttps://api.pagerduty.com\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /abilities -- list abilities\n3. POST /{entity_type}/{id}/change_tags -- create first change_tag\n\n## Endpoints\n420 endpoints across 40 groups. See references/api-spec.lap for full details.\n\n### {entity_type}\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /{entity_type}/{id}/change_tags | Assign tags |\n| GET | /{entity_type}/{id}/tags | Get tags for entities |\n\n### Abilities\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /abilities | List abilities |\n| GET | /abilities/{id} | Test an ability |\n\n### Addons\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /addons | List installed Add-ons |\n| POST | /addons | Install an Add-on |\n| GET | /addons/{id} | Get an Add-on |\n| DELETE | /addons/{id} | Delete an Add-on |\n| PUT | /addons/{id} | Update an Add-on |\n\n### Alert_grouping_settings\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /alert_grouping_settings | List alert grouping settings |\n| POST | /alert_grouping_settings | Create an Alert Grouping Setting |\n| GET | /alert_grouping_settings/{id} | Get an Alert Grouping Setting |\n| DELETE | /alert_grouping_settings/{id} | Delete an Alert Grouping Setting |\n| PUT | /alert_grouping_settings/{id} | Update an Alert Grouping Setting |\n\n### Analytics\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /analytics/metrics/incidents/all | Get aggregated incident data |\n| POST | /analytics/metrics/incidents/escalation_policies | Get aggregated escalation policy data |\n| POST | /analytics/metrics/incidents/escalation_policies/all | Get aggregated metrics for all escalation policies |\n| POST | /analytics/metrics/incidents/services | Get aggregated service data |\n| POST | /analytics/metrics/incidents/services/all | Get aggregated metrics for all services |\n| POST | /analytics/metrics/incidents/teams | Get aggregated team data |\n| POST | /analytics/metrics/incidents/teams/all | Get aggregated metrics for all teams |\n| POST | /analytics/metrics/pd_advance_usage/features | Get aggregated PD Advance usage data |\n| POST | /analytics/metrics/responders/all | Get aggregated metrics for all responders |\n| POST | /analytics/metrics/responders/teams | Get responder data aggregated by team |\n| POST | /analytics/metrics/users/all | Get aggregated metrics for all users |\n| POST | /analytics/raw/incidents | Get raw data - multiple incidents |\n| GET | /analytics/raw/incidents/{id} | Get raw data - single incident |\n| GET | /analytics/raw/incidents/{id}/responses | Get raw responses from a single incident |\n| POST | /analytics/raw/responders/{responder_id}/incidents | Get raw incidents for a single responder_id |\n| POST | /analytics/raw/users | Get raw user analytics data |\n\n### Audit\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /audit/records | List audit records |\n\n### Automation_actions\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /automation_actions/actions | Create an Automation Action |\n| GET | /automation_actions/actions | List Automation Actions |\n| GET | /automation_actions/actions/{id} | Get an Automation Action |\n| DELETE | /automation_actions/actions/{id} | Delete an Automation Action |\n| PUT | /automation_actions/actions/{id} | Update an Automation Action |\n| POST | /automation_actions/actions/{id}/invocations | Create an Invocation |\n| GET | /automation_actions/actions/{id}/services | Get all service references associated with an Automation Action |\n| POST | /automation_actions/actions/{id}/services | Associate an Automation Action with a service |\n| GET | /automation_actions/actions/{id}/services/{service_id} | Get the details of an Automation Action / service relation |\n| DELETE | /automation_actions/actions/{id}/services/{service_id} | Disassociate an Automation Action from a service |\n| POST | /automation_actions/actions/{id}/teams | Associate an Automation Action with a team |\n| GET | /automation_actions/actions/{id}/teams | Get all team references associated with an Automation Action |\n| DELETE | /automation_actions/actions/{id}/teams/{team_id} | Disassociate an Automation Action from a team |\n| GET | /automation_actions/actions/{id}/teams/{team_id} | Get the details of an Automation Action / team relation |\n| GET | /automation_actions/invocations | List Invocations |\n| GET | /automation_actions/invocations/{id} | Get an Invocation |\n| POST | /automation_actions/runners | Create an Automation Action runner. |\n| GET | /automation_actions/runners | List Automation Action runners |\n| GET | /automation_actions/runners/{id} | Get an Automation Action runner |\n| PUT | /automation_actions/runners/{id} | Update an Automation Action runner |\n| DELETE | /automation_actions/runners/{id} | Delete an Automation Action runner |\n| POST | /automation_actions/runners/{id}/teams | Associate a runner with a team |\n| GET | /automation_actions/runners/{id}/teams | Get all team references associated with a runner |\n| DELETE | /automation_actions/runners/{id}/teams/{team_id} | Disassociate a runner from a team |\n| GET | /automation_actions/runners/{id}/teams/{team_id} | Get the details of a runner / team relation |\n\n### Business_services\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /business_services | List Business Services |\n| POST | /business_services | Create a Business Service |\n| GET | /business_services/{id} | Get a Business Service |\n| DELETE | /business_services/{id} | Delete a Business Service |\n| PUT | /business_services/{id} | Update a Business Service |\n| POST | /business_services/{id}/account_subscription | Create Business Service Account Subscription |\n| DELETE | /business_services/{id}/account_subscription | Delete Business Service Account Subscription |\n| GET | /business_services/{id}/subscribers | List Business Service Subscribers |\n| POST | /business_services/{id}/subscribers | Create Business Service Subscribers |\n| GET | /business_services/{id}/supporting_services/impacts | List the supporting Business Services for the given Business Service Id, sorted by impacted status. |\n| POST | /business_services/{id}/unsubscribe | Remove Business Service Subscribers |\n| GET | /business_services/impactors | List Impactors affecting Business Services |\n| GET | /business_services/impacts | List Business Services sorted by impacted status |\n| GET | /business_services/priority_thresholds | Get the global priority threshold for a Business Service to be considered impacted by an Incident |\n| DELETE | /business_services/priority_thresholds | Deletes the account-level priority threshold for Business Service impact |\n| PUT | /business_services/priority_thresholds | Set the Account-level priority threshold for Business Service impact. |\n\n### Change_events\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /change_events | List Change Events |\n| POST | /change_events | Create a Change Event |\n| GET | /change_events/{id} | Get a Change Event |\n| PUT | /change_events/{id} | Update a Change Event |\n\n### Escalation_policies\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /escalation_policies | List escalation policies |\n| POST | /escalation_policies | Create an escalation policy |\n| GET | /escalation_policies/{id} | Get an escalation policy |\n| DELETE | /escalation_policies/{id} | Delete an escalation policy |\n| PUT | /escalation_policies/{id} | Update an escalation policy |\n| GET | /escalation_policies/{id}/audit/records | List audit records for an escalation policy |\n\n### Event_orchestrations\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /event_orchestrations | List Event Orchestrations |\n| POST | /event_orchestrations | Create an Orchestration |\n| GET | /event_orchestrations/{id} | Get an Orchestration |\n| PUT | /event_orchestrations/{id} | Update an Orchestration |\n| DELETE | /event_orchestrations/{id} | Delete an Orchestration |\n| GET | /event_orchestrations/{id}/integrations | List Integrations for an Event Orchestration |\n| POST | /event_orchestrations/{id}/integrations | Create an Integration for an Event Orchestration |\n| GET | /event_orchestrations/{id}/integrations/{integration_id} | Get an Integration for an Event Orchestration |\n| PUT | /event_orchestrations/{id}/integrations/{integration_id} | Update an Integration for an Event Orchestration |\n| DELETE | /event_orchestrations/{id}/integrations/{integration_id} | Delete an Integration for an Event Orchestration |\n| POST | /event_orchestrations/{id}/integrations/migration | Migrate an Integration from one Event Orchestration to another |\n| GET | /event_orchestrations/{id}/global | Get the Global Orchestration for an Event Orchestration |\n| PUT | /event_orchestrations/{id}/global | Update the Global Orchestration for an Event Orchestration |\n| GET | /event_orchestrations/{id}/router | Get the Router for an Event Orchestration |\n| PUT | /event_orchestrations/{id}/router | Update the Router for an Event Orchestration |\n| GET | /event_orchestrations/{id}/unrouted | Get the Unrouted Orchestration for an Event Orchestration |\n| PUT | /event_orchestrations/{id}/unrouted | Update the Unrouted Orchestration for an Event Orchestration |\n| GET | /event_orchestrations/services/{service_id} | Get the Service Orchestration for a Service |\n| PUT | /event_orchestrations/services/{service_id} | Update the Service Orchestration for a Service |\n| GET | /event_orchestrations/services/{service_id}/active | Get the Service Orchestration active status for a Service |\n| PUT | /event_orchestrations/services/{service_id}/active | Update the Service Orchestration active status for a Service |\n| GET | /event_orchestrations/{id}/cache_variables | List Cache Variables for a Global Event Orchestration |\n| POST | /event_orchestrations/{id}/cache_variables | Create a Cache Variable for a Global Event Orchestration |\n| GET | /event_orchestrations/{id}/cache_variables/{cache_variable_id} | Get a Cache Variable for a Global Event Orchestration |\n| PUT | /event_orchestrations/{id}/cache_variables/{cache_variable_id} | Update a Cache Variable for a Global Event Orchestration |\n| DELETE | /event_orchestrations/{id}/cache_variables/{cache_variable_id} | Delete a Cache Variable for a Global Event Orchestration |\n| GET | /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data | Get Data for an External Data Cache Variable on a Global Event Orchestration |\n| PUT | /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data | Update Data for an External Data Cache Variable on a Global Event Orchestration |\n| DELETE | /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data | Delete Data for an External Data Cache Variable on a Global Event Orchestration |\n| GET | /event_orchestrations/services/{service_id}/cache_variables | List Cache Variables for a Service Event Orchestration |\n| POST | /event_orchestrations/services/{service_id}/cache_variables | Create a Cache Variable for a Service Event Orchestration |\n| GET | /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id} | Get a Cache Variable for a Service Event Orchestration |\n| PUT | /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id} | Update a Cache Variable for a Service Event Orchestration |\n| DELETE | /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id} | Delete a Cache Variable for a Service Event Orchestration |\n| GET | /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}/data | Get Data for an External Data Cache Variable on a Service Event Orchestration |\n| PUT | /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}/data | Update Data for an External Data Cache Variable on a Service Event Orchestration |\n| DELETE | /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}/data | Delete Data for an External Data Cache Variable on a Service Event Orchestration |\n| GET | /event_orchestrations/{id}/enablements | List Enablements for an Event Orchestration |\n| PUT | /event_orchestrations/{id}/enablements/{feature_name} | Update an Enablement for an Event Orchestration |\n\n### Extension_schemas\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /extension_schemas | List extension schemas |\n| GET | /extension_schemas/{id} | Get an extension vendor |\n\n### Extensions\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /extensions | List extensions |\n| POST | /extensions | Create an extension |\n| GET | /extensions/{id} | Get an extension |\n| DELETE | /extensions/{id} | Delete an extension |\n| PUT | /extensions/{id} | Update an extension |\n| POST | /extensions/{id}/enable | Enable an extension |\n\n### Incident_workflows\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /incident_workflows | List Incident Workflows |\n| POST | /incident_workflows | Create an Incident Workflow |\n| GET | /incident_workflows/{id} | Get an Incident Workflow |\n| DELETE | /incident_workflows/{id} | Delete an Incident Workflow |\n| PUT | /incident_workflows/{id} | Update an Incident Workflow |\n| POST | /incident_workflows/{id}/instances | Start an Incident Workflow Instance |\n| GET | /incident_workflows/actions | List Actions |\n| GET | /incident_workflows/actions/{id} | Get an Action |\n| GET | /incident_workflows/triggers | List Triggers |\n| POST | /incident_workflows/triggers | Create a Trigger |\n| GET | /incident_workflows/triggers/{id} | Get a Trigger |\n| PUT | /incident_workflows/triggers/{id} | Update a Trigger |\n| DELETE | /incident_workflows/triggers/{id} | Delete a Trigger |\n| POST | /incident_workflows/triggers/{id}/services | Associate a Trigger and Service |\n| DELETE | /incident_workflows/triggers/{trigger_id}/services/{service_id} | Dissociate a Trigger and Service |\n\n### Incidents\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /incidents | List incidents |\n| PUT | /incidents | Manage incidents |\n| POST | /incidents | Create an Incident |\n| GET | /incidents/{id} | Get an incident |\n| PUT | /incidents/{id} | Update an incident |\n| GET | /incidents/{id}/alerts | List alerts for an incident |\n| PUT | /incidents/{id}/alerts | Manage alerts |\n| GET | /incidents/{id}/alerts/{alert_id} | Get an alert |\n| PUT | /incidents/{id}/alerts/{alert_id} | Update an alert |\n| PUT | /incidents/{id}/business_services/{business_service_id}/impacts | Manually change an Incident's Impact on a Business Service. |\n| GET | /incidents/{id}/business_services/impacts | List Business Services impacted by the given Incident |\n| GET | /incidents/{id}/custom_fields/values | Get Custom Field Values |\n| PUT | /incidents/{id}/custom_fields/values | Update Custom Field Values |\n| GET | /incidents/{id}/log_entries | List log entries for an incident |\n| PUT | /incidents/{id}/merge | Merge incidents |\n| GET | /incidents/{id}/notes | List notes for an incident |\n| POST | /incidents/{id}/notes | Create a note on an incident |\n| PUT | /incidents/{id}/notes/{note_id} | Update a note on an incident |\n| DELETE | /incidents/{id}/notes/{note_id} | Delete a note on an incident |\n| GET | /incidents/{id}/outlier_incident | Get Outlier Incident |\n| GET | /incidents/{id}/past_incidents | Get Past Incidents |\n| GET | /incidents/{id}/related_change_events | List related Change Events for an Incident |\n| GET | /incidents/{id}/related_incidents | Get Related Incidents |\n| POST | /incidents/{id}/responder_requests | Create a responder request for an incident |\n| PUT | /incidents/{id}/responder_requests/cancel | Cancel responder requests for an incident |\n| POST | /incidents/{id}/snooze | Snooze an incident |\n| POST | /incidents/{id}/status_updates | Create a status update on an incident |\n| GET | /incidents/{id}/status_updates/subscribers | List Notification Subscribers |\n| POST | /incidents/{id}/status_updates/subscribers | Add Notification Subscribers |\n| POST | /incidents/{id}/status_updates/unsubscribe | Remove Notification Subscriber |\n| GET | /incidents/types | List incident types |\n| POST | /incidents/types | Create an Incident Type |\n| GET | /incidents/types/{type_id_or_name} | Get an Incident Type |\n| PUT | /incidents/types/{type_id_or_name} | Update an Incident Type |\n| GET | /incidents/types/{type_id_or_name}/custom_fields | List Incident Type Custom Fields |\n| POST | /incidents/types/{type_id_or_name}/custom_fields | Create a Custom Field for an Incident Type |\n| GET | /incidents/types/{type_id_or_name}/custom_fields/{field_id} | Get an Incident Type Custom Field |\n| PUT | /incidents/types/{type_id_or_name}/custom_fields/{field_id} | Update a Custom Field for an Incident Type |\n| DELETE | /incidents/types/{type_id_or_name}/custom_fields/{field_id} | Delete a Custom Field for an Incident Type |\n| GET | /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options | List Field Options on a Custom Field |\n| POST | /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options | Create a Field Option for a Custom Field |\n| GET | /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id} | Get a Field Option on a Custom Field |\n| PUT | /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id} | Update a Field Option for a Custom Field |\n| DELETE | /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id} | Delete a Field Option for a Custom Field |\n| POST | /incidents/custom_fields | Create a Field |\n| GET | /incidents/custom_fields | List Fields |\n| GET | /incidents/custom_fields/{field_id} | Get a Field |\n| PUT | /incidents/custom_fields/{field_id} | Update a Field |\n| DELETE | /incidents/custom_fields/{field_id} | Delete a Field |\n| POST | /incidents/custom_fields/{field_id}/field_options | Create a Field Option |\n| GET | /incidents/custom_fields/{field_id}/field_options | List Field Options |\n| PUT | /incidents/custom_fields/{field_id}/field_options/{field_option_id} | Update a Field Option |\n| DELETE | /incidents/custom_fields/{field_id}/field_options/{field_option_id} | Delete a Field Option |\n\n### License_allocations\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /license_allocations | List License Allocations |\n\n### Licenses\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /licenses | List Licenses |\n\n### Log_entries\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /log_entries | List log entries |\n| GET | /log_entries/{id} | Get a log entry |\n| PUT | /log_entries/{id}/channel | Update log entry channel information. |\n\n### Maintenance_windows\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /maintenance_windows | List maintenance windows |\n| POST | /maintenance_windows | Create a maintenance window |\n| GET | /maintenance_windows/{id} | Get a maintenance window |\n| DELETE | /maintenance_windows/{id} | Delete or end a maintenance window |\n| PUT | /maintenance_windows/{id} | Update a maintenance window |\n\n### Notifications\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /notifications | List notifications |\n\n### Oauth_delegations\n| Method | Path | Description |\n|--------|------|-------------|\n| DELETE | /oauth_delegations | Delete all OAuth delegations |\n| GET | /oauth_delegations/revocation_requests/status | Get OAuth delegations revocation requests status |\n\n### Oncalls\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /oncalls | List all of the on-calls |\n\n### Paused_incident_reports\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /paused_incident_reports/alerts | Get Paused Incident Reporting on Alerts |\n| GET | /paused_incident_reports/counts | Get Paused Incident Reporting counts |\n\n### Priorities\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /priorities | List priorities |\n\n### Rulesets\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /rulesets | List Rulesets |\n| POST | /rulesets | Create a Ruleset |\n| GET | /rulesets/{id} | Get a Ruleset |\n| PUT | /rulesets/{id} | Update a Ruleset |\n| DELETE | /rulesets/{id} | Delete a Ruleset |\n| GET | /rulesets/{id}/rules | List Event Rules |\n| POST | /rulesets/{id}/rules | Create an Event Rule |\n| GET | /rulesets/{id}/rules/{rule_id} | Get an Event Rule |\n| PUT | /rulesets/{id}/rules/{rule_id} | Update an Event Rule |\n| DELETE | /rulesets/{id}/rules/{rule_id} | Delete an Event Rule |\n\n### Schedules\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /schedules | List schedules |\n| POST | /schedules | Create a schedule |\n| GET | /schedules/{id} | Get a schedule |\n| DELETE | /schedules/{id} | Delete a schedule |\n| PUT | /schedules/{id} | Update a schedule |\n| GET | /schedules/{id}/audit/records | List audit records for a schedule |\n| GET | /schedules/{id}/overrides | List overrides |\n| POST | /schedules/{id}/overrides | Create one or more overrides |\n| DELETE | /schedules/{id}/overrides/{override_id} | Delete an override |\n| GET | /schedules/{id}/users | List users on call. |\n| POST | /schedules/preview | Preview a schedule |\n| GET | /v3/schedules | List schedules |\n| POST | /v3/schedules | Create a schedule |\n| GET | /v3/schedules/{id} | Get a schedule |\n| PUT | /v3/schedules/{id} | Update a schedule |\n| DELETE | /v3/schedules/{id} | Delete a schedule |\n| GET | /v3/schedules/{id}/custom_shifts | List custom shifts |\n| POST | /v3/schedules/{id}/custom_shifts | Create custom shifts |\n| GET | /v3/schedules/{id}/custom_shifts/{custom_shift_id} | Get a custom shift |\n| PUT | /v3/schedules/{id}/custom_shifts/{custom_shift_id} | Update a custom shift |\n| DELETE | /v3/schedules/{id}/custom_shifts/{custom_shift_id} | Delete a custom shift |\n| GET | /v3/schedules/{id}/overrides | List overrides |\n| POST | /v3/schedules/{id}/overrides | Create overrides |\n| GET | /v3/schedules/{id}/overrides/{override_id} | Get an override |\n| PUT | /v3/schedules/{id}/overrides/{override_id} | Update an override |\n| DELETE | /v3/schedules/{id}/overrides/{override_id} | Delete an override |\n| GET | /v3/schedules/{id}/rotations | List rotations |\n| POST | /v3/schedules/{id}/rotations | Create a rotation |\n| GET | /v3/schedules/{id}/rotations/{rotation_id} | Get a rotation |\n| DELETE | /v3/schedules/{id}/rotations/{rotation_id} | Delete a rotation |\n| GET | /v3/schedules/{id}/rotations/{rotation_id}/events | List events |\n| POST | /v3/schedules/{id}/rotations/{rotation_id}/events | Create an event |\n| GET | /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id} | Get an event |\n| PUT | /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id} | Update an event |\n| DELETE | /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id} | Delete an event |\n\n### Service_dependencies\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /service_dependencies/associate | Associate service dependencies |\n| GET | /service_dependencies/business_services/{id} | Get Business Service dependencies |\n| POST | /service_dependencies/disassociate | Disassociate service dependencies |\n| GET | /service_dependencies/technical_services/{id} | Get technical service dependencies |\n\n### Services\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /services | List services |\n| POST | /services | Create a service |\n| GET | /services/{id} | Get a service |\n| DELETE | /services/{id} | Delete a service |\n| PUT | /services/{id} | Update a service |\n| GET | /services/{id}/audit/records | List audit records for a service |\n| GET | /services/{id}/change_events | List Change Events for a service |\n| POST | /services/{id}/integrations | Create a new integration |\n| PUT | /services/{id}/integrations/{integration_id} | Update an existing integration |\n| GET | /services/{id}/integrations/{integration_id} | View an integration |\n| GET | /services/{id}/rules | List Service's Event Rules |\n| POST | /services/{id}/rules | Create an Event Rule on a Service |\n| POST | /services/{id}/rules/convert | Convert a Service's Event Rules into Event Orchestration Rules |\n| GET | /services/{id}/rules/{rule_id} | Get an Event Rule from a Service |\n| PUT | /services/{id}/rules/{rule_id} | Update an Event Rule on a Service |\n| DELETE | /services/{id}/rules/{rule_id} | Delete an Event Rule from a Service |\n| POST | /services/custom_fields | Create a Field |\n| GET | /services/custom_fields | List Fields |\n| GET | /services/custom_fields/{field_id} | Get a Field |\n| PUT | /services/custom_fields/{field_id} | Update a Field |\n| DELETE | /services/custom_fields/{field_id} | Delete a Field |\n| GET | /services/custom_fields/{field_id}/field_options | List Field Options |\n| POST | /services/custom_fields/{field_id}/field_options | Create a Field Option |\n| GET | /services/custom_fields/{field_id}/field_options/{field_option_id} | Get a Field Option |\n| PUT | /services/custom_fields/{field_id}/field_options/{field_option_id} | Update a Field Option |\n| DELETE | /services/custom_fields/{field_id}/field_options/{field_option_id} | Delete a Field Option |\n| GET | /services/{id}/custom_fields/values | Get Custom Field Values |\n| PUT | /services/{id}/custom_fields/values | Update Custom Field Values |\n| GET | /services/{id}/enablements | Get Enablements for a Service |\n| PUT | /services/{id}/enablements/{feature_name} | Update an Enablement for a Service |\n\n### Session_configurations\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /session_configurations | Get an account's session configurations |\n| PUT | /session_configurations | Configure an account's session configurations |\n| DELETE | /session_configurations | Delete an account's session configurations. |\n\n### Standards\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /standards | List Standards |\n| PUT | /standards/{id} | Update a standard |\n| GET | /standards/scores/{resource_type} | List resources' standards scores |\n| GET | /standards/scores/{resource_type}/{id} | List a resource's standards scores |\n\n### Status_dashboards\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /status_dashboards | List Status Dashboards |\n| GET | /status_dashboards/{id} | Get a single Status Dashboard by `id` |\n| GET | /status_dashboards/{id}/service_impacts | Get impacted Business Services for a Status Dashboard by `id`. |\n| GET | /status_dashboards/url_slugs/{url_slug} | Get a single Status Dashboard by `url_slug` |\n| GET | /status_dashboards/url_slugs/{url_slug}/service_impacts | Get impacted Business Services for a  Status Dashboard by `url_slug` |\n\n### Status_pages\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /status_pages | List Status Pages |\n| GET | /status_pages/{id}/impacts | List Status Page Impacts |\n| GET | /status_pages/{id}/impacts/{impact_id} | Get a Status Page Impact |\n| GET | /status_pages/{id}/services | List Status Page Services |\n| GET | /status_pages/{id}/services/{service_id} | Get a Status Page Service |\n| GET | /status_pages/{id}/severities | List Status Page Severities |\n| GET | /status_pages/{id}/severities/{severity_id} | Get a Status Page Severity |\n| GET | /status_pages/{id}/statuses | List Status Page Statuses |\n| GET | /status_pages/{id}/statuses/{status_id} | Get a Status Page Status |\n| GET | /status_pages/{id}/posts | List Status Page Posts |\n| POST | /status_pages/{id}/posts | Create a Status Page Post |\n| GET | /status_pages/{id}/posts/{post_id} | Get a Status Page Post |\n| PUT | /status_pages/{id}/posts/{post_id} | Update a Status Page Post |\n| DELETE | /status_pages/{id}/posts/{post_id} | Delete a Status Page Post |\n| GET | /status_pages/{id}/posts/{post_id}/post_updates | List Status Page Post Updates |\n| POST | /status_pages/{id}/posts/{post_id}/post_updates | Create a Status Page Post Update |\n| GET | /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id} | Get a Status Page Post Update |\n| PUT | /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id} | Update a Status Page Post Update |\n| DELETE | /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id} | Delete a Status Page Post Update |\n| GET | /status_pages/{id}/posts/{post_id}/postmortem | Get a Post Postmortem |\n| POST | /status_pages/{id}/posts/{post_id}/postmortem | Create a Post Postmortem |\n| PUT | /status_pages/{id}/posts/{post_id}/postmortem | Update a Post Postmortem |\n| DELETE | /status_pages/{id}/posts/{post_id}/postmortem | Delete a Post Postmortem |\n| GET | /status_pages/{id}/subscriptions | List Status Page Subscriptions |\n| POST | /status_pages/{id}/subscriptions | Create a Status Page Subscription |\n| GET | /status_pages/{id}/subscriptions/{subscription_id} | Get a Status Page Subscription |\n| DELETE | /status_pages/{id}/subscriptions/{subscription_id} | Delete a Status Page Subscription |\n\n### Sre_agent\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /sre_agent/memories | List SRE Agent memories |\n| PUT | /sre_agent/memories/{id} | Update an SRE Agent memory |\n| DELETE | /sre_agent/memories/{id} | Delete an SRE Agent memory |\n\n### Tags\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /tags | List tags |\n| POST | /tags | Create a tag |\n| GET | /tags/{id} | Get a tag |\n| DELETE | /tags/{id} | Delete a tag |\n| GET | /tags/{id}/{entity_type} | Get connected entities |\n\n### Teams\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /teams | Create a team |\n| GET | /teams | List teams |\n| GET | /teams/{id} | Get a team |\n| DELETE | /teams/{id} | Delete a team |\n| PUT | /teams/{id} | Update a team |\n| GET | /teams/{id}/audit/records | List audit records for a team |\n| DELETE | /teams/{id}/escalation_policies/{escalation_policy_id} | Remove an escalation policy from a team |\n| PUT | /teams/{id}/escalation_policies/{escalation_policy_id} | Add an escalation policy to a team |\n| GET | /teams/{id}/members | List members of a team |\n| GET | /teams/{id}/notification_subscriptions | List Team Notification Subscriptions |\n| POST | /teams/{id}/notification_subscriptions | Create Team Notification Subscriptions |\n| POST | /teams/{id}/notification_subscriptions/unsubscribe | Unsubscribe the given Team from Notifications on the matching Subscribable entities. |\n| DELETE | /teams/{id}/users/{user_id} | Remove a user from a team |\n| PUT | /teams/{id}/users/{user_id} | Add a user to a team |\n\n### Templates\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /templates | List templates |\n| POST | /templates | Create a template |\n| GET | /templates/{id} | Get a template |\n| PUT | /templates/{id} | Update a template |\n| DELETE | /templates/{id} | Delete a template |\n| POST | /templates/{id}/render | Render a template |\n| GET | /templates/fields | List template fields |\n\n### Users\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /users | List users |\n| POST | /users | Create a user |\n| GET | /users/{id} | Get a user |\n| DELETE | /users/{id} | Delete a user |\n| PUT | /users/{id} | Update a user |\n| GET | /users/{id}/audit/records | List audit records for a user |\n| GET | /users/{id}/contact_methods | List a user's contact methods |\n| POST | /users/{id}/contact_methods | Create a user contact method |\n| GET | /users/{id}/contact_methods/{contact_method_id} | Get a user's contact method |\n| DELETE | /users/{id}/contact_methods/{contact_method_id} | Delete a user's contact method |\n| PUT | /users/{id}/contact_methods/{contact_method_id} | Update a user's contact method |\n| GET | /users/{id}/oauth_delegations | List a user's delegations |\n| GET | /users/{id}/oauth_delegations/{delegation_id} | Get a user's delegation |\n| GET | /users/{id}/license | Get the License allocated to a User |\n| GET | /users/{id}/notification_rules | List a user's notification rules |\n| POST | /users/{id}/notification_rules | Create a user notification rule |\n| GET | /users/{id}/notification_rules/{notification_rule_id} | Get a user's notification rule |\n| DELETE | /users/{id}/notification_rules/{notification_rule_id} | Delete a user's notification rule |\n| PUT | /users/{id}/notification_rules/{notification_rule_id} | Update a user's notification rule |\n| GET | /users/{id}/notification_subscriptions | List Notification Subscriptions |\n| POST | /users/{id}/notification_subscriptions | Create Notification Subcriptions |\n| POST | /users/{id}/notification_subscriptions/unsubscribe | Remove Notification Subscriptions |\n| GET | /users/{id}/oncall_handoff_notification_rules | List a User's Handoff Notification Rules |\n| POST | /users/{id}/oncall_handoff_notification_rules | Create a User Handoff Notification Rule |\n| GET | /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id} | Get a user's handoff notification rule |\n| DELETE | /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id} | Delete a User's Handoff Notification rule |\n| PUT | /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id} | Update a User's Handoff Notification Rule |\n| GET | /users/{id}/sessions | List a user's active sessions |\n| DELETE | /users/{id}/sessions | Delete all user sessions |\n| GET | /users/{id}/sessions/{type}/{session_id} | Get a user's session |\n| DELETE | /users/{id}/sessions/{type}/{session_id} | Delete a user's session |\n| GET | /users/{id}/status_update_notification_rules | List a user's status update notification rules |\n| POST | /users/{id}/status_update_notification_rules | Create a user status update notification rule |\n| GET | /users/{id}/status_update_notification_rules/{status_update_notification_rule_id} | Get a user's status update notification rule |\n| DELETE | /users/{id}/status_update_notification_rules/{status_update_notification_rule_id} | Delete a user's status update notification rule |\n| PUT | /users/{id}/status_update_notification_rules/{status_update_notification_rule_id} | Update a user's status update notification rule |\n| GET | /users/me | Get the current user |\n\n### Vendors\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /vendors | List vendors |\n| GET | /vendors/{id} | Get a vendor |\n\n### Webhook_subscriptions\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /webhook_subscriptions | List webhook subscriptions |\n| POST | /webhook_subscriptions | Create a webhook subscription |\n| GET | /webhook_subscriptions/{id} | Get a webhook subscription |\n| PUT | /webhook_subscriptions/{id} | Update a webhook subscription |\n| DELETE | /webhook_subscriptions/{id} | Delete a webhook subscription |\n| POST | /webhook_subscriptions/{id}/enable | Enable a webhook subscription |\n| POST | /webhook_subscriptions/{id}/ping | Test a webhook subscription |\n| GET | /webhook_subscriptions/oauth_clients | List OAuth clients |\n| POST | /webhook_subscriptions/oauth_clients | Create an OAuth client |\n| GET | /webhook_subscriptions/oauth_clients/{id} | Get an OAuth client |\n| PUT | /webhook_subscriptions/oauth_clients/{id} | Update an OAuth client |\n| DELETE | /webhook_subscriptions/oauth_clients/{id} | Delete an OAuth client |\n\n### Workflows\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /workflows/integrations | List Workflow Integrations |\n| GET | /workflows/integrations/{id} | Get Workflow Integration |\n| GET | /workflows/integrations/connections | List all Workflow Integration Connections |\n| GET | /workflows/integrations/{integration_id}/connections | List Workflow Integration Connections |\n| POST | /workflows/integrations/{integration_id}/connections | Create Workflow Integration Connection |\n| GET | /workflows/integrations/{integration_id}/connections/{id} | Get Workflow Integration Connection |\n| PATCH | /workflows/integrations/{integration_id}/connections/{id} | Update Workflow Integration Connection |\n| DELETE | /workflows/integrations/{integration_id}/connections/{id} | Delete Workflow Integration Connection |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Create a change_tag?\" -> POST /{entity_type}/{id}/change_tags\n- \"List all tags?\" -> GET /{entity_type}/{id}/tags\n- \"List all abilities?\" -> GET /abilities\n- \"Get ability details?\" -> GET /abilities/{id}\n- \"List all addons?\" -> GET /addons\n- \"Create a addon?\" -> POST /addons\n- \"Get addon details?\" -> GET /addons/{id}\n- \"Delete a addon?\" -> DELETE /addons/{id}\n- \"Update a addon?\" -> PUT /addons/{id}\n- \"List all alert_grouping_settings?\" -> GET /alert_grouping_settings\n- \"Create a alert_grouping_setting?\" -> POST /alert_grouping_settings\n- \"Get alert_grouping_setting details?\" -> GET /alert_grouping_settings/{id}\n- \"Delete a alert_grouping_setting?\" -> DELETE /alert_grouping_settings/{id}\n- \"Update a alert_grouping_setting?\" -> PUT /alert_grouping_settings/{id}\n- \"Create a all?\" -> POST /analytics/metrics/incidents/all\n- \"Create a escalation_policy?\" -> POST /analytics/metrics/incidents/escalation_policies\n- \"Create a service?\" -> POST /analytics/metrics/incidents/services\n- \"Create a team?\" -> POST /analytics/metrics/incidents/teams\n- \"Create a feature?\" -> POST /analytics/metrics/pd_advance_usage/features\n- \"Create a incident?\" -> POST /analytics/raw/incidents\n- \"Get incident details?\" -> GET /analytics/raw/incidents/{id}\n- \"List all responses?\" -> GET /analytics/raw/incidents/{id}/responses\n- \"Create a user?\" -> POST /analytics/raw/users\n- \"List all records?\" -> GET /audit/records\n- \"Create a action?\" -> POST /automation_actions/actions\n- \"List all actions?\" -> GET /automation_actions/actions\n- \"Get action details?\" -> GET /automation_actions/actions/{id}\n- \"Delete a action?\" -> DELETE /automation_actions/actions/{id}\n- \"Update a action?\" -> PUT /automation_actions/actions/{id}\n- \"Create a invocation?\" -> POST /automation_actions/actions/{id}/invocations\n- \"List all services?\" -> GET /automation_actions/actions/{id}/services\n- \"Get service details?\" -> GET /automation_actions/actions/{id}/services/{service_id}\n- \"Delete a service?\" -> DELETE /automation_actions/actions/{id}/services/{service_id}\n- \"List all teams?\" -> GET /automation_actions/actions/{id}/teams\n- \"Delete a team?\" -> DELETE /automation_actions/actions/{id}/teams/{team_id}\n- \"Get team details?\" -> GET /automation_actions/actions/{id}/teams/{team_id}\n- \"List all invocations?\" -> GET /automation_actions/invocations\n- \"Get invocation details?\" -> GET /automation_actions/invocations/{id}\n- \"Create a runner?\" -> POST /automation_actions/runners\n- \"List all runners?\" -> GET /automation_actions/runners\n- \"Get runner details?\" -> GET /automation_actions/runners/{id}\n- \"Update a runner?\" -> PUT /automation_actions/runners/{id}\n- \"Delete a runner?\" -> DELETE /automation_actions/runners/{id}\n- \"List all business_services?\" -> GET /business_services\n- \"Create a business_service?\" -> POST /business_services\n- \"Get business_service details?\" -> GET /business_services/{id}\n- \"Delete a business_service?\" -> DELETE /business_services/{id}\n- \"Update a business_service?\" -> PUT /business_services/{id}\n- \"Create a account_subscription?\" -> POST /business_services/{id}/account_subscription\n- \"List all subscribers?\" -> GET /business_services/{id}/subscribers\n- \"Create a subscriber?\" -> POST /business_services/{id}/subscribers\n- \"List all impacts?\" -> GET /business_services/{id}/supporting_services/impacts\n- \"Create a unsubscribe?\" -> POST /business_services/{id}/unsubscribe\n- \"List all impactors?\" -> GET /business_services/impactors\n- \"List all priority_thresholds?\" -> GET /business_services/priority_thresholds\n- \"List all change_events?\" -> GET /change_events\n- \"Create a change_event?\" -> POST /change_events\n- \"Get change_event details?\" -> GET /change_events/{id}\n- \"Update a change_event?\" -> PUT /change_events/{id}\n- \"Search escalation_policies?\" -> GET /escalation_policies\n- \"Get escalation_policy details?\" -> GET /escalation_policies/{id}\n- \"Delete a escalation_policy?\" -> DELETE /escalation_policies/{id}\n- \"Update a escalation_policy?\" -> PUT /escalation_policies/{id}\n- \"List all event_orchestrations?\" -> GET /event_orchestrations\n- \"Create a event_orchestration?\" -> POST /event_orchestrations\n- \"Get event_orchestration details?\" -> GET /event_orchestrations/{id}\n- \"Update a event_orchestration?\" -> PUT /event_orchestrations/{id}\n- \"Delete a event_orchestration?\" -> DELETE /event_orchestrations/{id}\n- \"List all integrations?\" -> GET /event_orchestrations/{id}/integrations\n- \"Create a integration?\" -> POST /event_orchestrations/{id}/integrations\n- \"Get integration details?\" -> GET /event_orchestrations/{id}/integrations/{integration_id}\n- \"Update a integration?\" -> PUT /event_orchestrations/{id}/integrations/{integration_id}\n- \"Delete a integration?\" -> DELETE /event_orchestrations/{id}/integrations/{integration_id}\n- \"Create a migration?\" -> POST /event_orchestrations/{id}/integrations/migration\n- \"List all global?\" -> GET /event_orchestrations/{id}/global\n- \"List all router?\" -> GET /event_orchestrations/{id}/router\n- \"List all unrouted?\" -> GET /event_orchestrations/{id}/unrouted\n- \"Update a service?\" -> PUT /event_orchestrations/services/{service_id}\n- \"List all active?\" -> GET /event_orchestrations/services/{service_id}/active\n- \"List all cache_variables?\" -> GET /event_orchestrations/{id}/cache_variables\n- \"Create a cache_variable?\" -> POST /event_orchestrations/{id}/cache_variables\n- \"Get cache_variable details?\" -> GET /event_orchestrations/{id}/cache_variables/{cache_variable_id}\n- \"Update a cache_variable?\" -> PUT /event_orchestrations/{id}/cache_variables/{cache_variable_id}\n- \"Delete a cache_variable?\" -> DELETE /event_orchestrations/{id}/cache_variables/{cache_variable_id}\n- \"List all data?\" -> GET /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data\n- \"List all enablements?\" -> GET /event_orchestrations/{id}/enablements\n- \"Update a enablement?\" -> PUT /event_orchestrations/{id}/enablements/{feature_name}\n- \"List all extension_schemas?\" -> GET /extension_schemas\n- \"Get extension_schema details?\" -> GET /extension_schemas/{id}\n- \"Search extensions?\" -> GET /extensions\n- \"Create a extension?\" -> POST /extensions\n- \"Get extension details?\" -> GET /extensions/{id}\n- \"Delete a extension?\" -> DELETE /extensions/{id}\n- \"Update a extension?\" -> PUT /extensions/{id}\n- \"Create a enable?\" -> POST /extensions/{id}/enable\n- \"Search incident_workflows?\" -> GET /incident_workflows\n- \"Create a incident_workflow?\" -> POST /incident_workflows\n- \"Get incident_workflow details?\" -> GET /incident_workflows/{id}\n- \"Delete a incident_workflow?\" -> DELETE /incident_workflows/{id}\n- \"Update a incident_workflow?\" -> PUT /incident_workflows/{id}\n- \"Create a instance?\" -> POST /incident_workflows/{id}/instances\n- \"List all triggers?\" -> GET /incident_workflows/triggers\n- \"Create a trigger?\" -> POST /incident_workflows/triggers\n- \"Get trigger details?\" -> GET /incident_workflows/triggers/{id}\n- \"Update a trigger?\" -> PUT /incident_workflows/triggers/{id}\n- \"Delete a trigger?\" -> DELETE /incident_workflows/triggers/{id}\n- \"List all incidents?\" -> GET /incidents\n- \"Update a incident?\" -> PUT /incidents/{id}\n- \"List all alerts?\" -> GET /incidents/{id}/alerts\n- \"Get alert details?\" -> GET /incidents/{id}/alerts/{alert_id}\n- \"Update a alert?\" -> PUT /incidents/{id}/alerts/{alert_id}\n- \"List all values?\" -> GET /incidents/{id}/custom_fields/values\n- \"List all log_entries?\" -> GET /incidents/{id}/log_entries\n- \"List all notes?\" -> GET /incidents/{id}/notes\n- \"Create a note?\" -> POST /incidents/{id}/notes\n- \"Update a note?\" -> PUT /incidents/{id}/notes/{note_id}\n- \"Delete a note?\" -> DELETE /incidents/{id}/notes/{note_id}\n- \"List all outlier_incident?\" -> GET /incidents/{id}/outlier_incident\n- \"List all past_incidents?\" -> GET /incidents/{id}/past_incidents\n- \"List all related_change_events?\" -> GET /incidents/{id}/related_change_events\n- \"List all related_incidents?\" -> GET /incidents/{id}/related_incidents\n- \"Create a responder_request?\" -> POST /incidents/{id}/responder_requests\n- \"Create a snooze?\" -> POST /incidents/{id}/snooze\n- \"Create a status_update?\" -> POST /incidents/{id}/status_updates\n- \"List all types?\" -> GET /incidents/types\n- \"Create a type?\" -> POST /incidents/types\n- \"Get type details?\" -> GET /incidents/types/{type_id_or_name}\n- \"Update a type?\" -> PUT /incidents/types/{type_id_or_name}\n- \"List all custom_fields?\" -> GET /incidents/types/{type_id_or_name}/custom_fields\n- \"Create a custom_field?\" -> POST /incidents/types/{type_id_or_name}/custom_fields\n- \"Get custom_field details?\" -> GET /incidents/types/{type_id_or_name}/custom_fields/{field_id}\n- \"Update a custom_field?\" -> PUT /incidents/types/{type_id_or_name}/custom_fields/{field_id}\n- \"Delete a custom_field?\" -> DELETE /incidents/types/{type_id_or_name}/custom_fields/{field_id}\n- \"List all field_options?\" -> GET /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options\n- \"Create a field_option?\" -> POST /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options\n- \"Get field_option details?\" -> GET /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}\n- \"Update a field_option?\" -> PUT /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}\n- \"Delete a field_option?\" -> DELETE /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}\n- \"List all license_allocations?\" -> GET /license_allocations\n- \"List all licenses?\" -> GET /licenses\n- \"Get log_entry details?\" -> GET /log_entries/{id}\n- \"Search maintenance_windows?\" -> GET /maintenance_windows\n- \"Create a maintenance_window?\" -> POST /maintenance_windows\n- \"Get maintenance_window details?\" -> GET /maintenance_windows/{id}\n- \"Delete a maintenance_window?\" -> DELETE /maintenance_windows/{id}\n- \"Update a maintenance_window?\" -> PUT /maintenance_windows/{id}\n- \"List all notifications?\" -> GET /notifications\n- \"List all status?\" -> GET /oauth_delegations/revocation_requests/status\n- \"List all oncalls?\" -> GET /oncalls\n- \"List all counts?\" -> GET /paused_incident_reports/counts\n- \"List all priorities?\" -> GET /priorities\n- \"List all rulesets?\" -> GET /rulesets\n- \"Create a ruleset?\" -> POST /rulesets\n- \"Get ruleset details?\" -> GET /rulesets/{id}\n- \"Update a ruleset?\" -> PUT /rulesets/{id}\n- \"Delete a ruleset?\" -> DELETE /rulesets/{id}\n- \"List all rules?\" -> GET /rulesets/{id}/rules\n- \"Create a rule?\" -> POST /rulesets/{id}/rules\n- \"Get rule details?\" -> GET /rulesets/{id}/rules/{rule_id}\n- \"Update a rule?\" -> PUT /rulesets/{id}/rules/{rule_id}\n- \"Delete a rule?\" -> DELETE /rulesets/{id}/rules/{rule_id}\n- \"Search schedules?\" -> GET /schedules\n- \"Create a schedule?\" -> POST /schedules\n- \"Get schedule details?\" -> GET /schedules/{id}\n- \"Delete a schedule?\" -> DELETE /schedules/{id}\n- \"Update a schedule?\" -> PUT /schedules/{id}\n- \"List all overrides?\" -> GET /schedules/{id}/overrides\n- \"Create a override?\" -> POST /schedules/{id}/overrides\n- \"Delete a override?\" -> DELETE /schedules/{id}/overrides/{override_id}\n- \"List all users?\" -> GET /schedules/{id}/users\n- \"Create a preview?\" -> POST /schedules/preview\n- \"Create a associate?\" -> POST /service_dependencies/associate\n- \"Create a disassociate?\" -> POST /service_dependencies/disassociate\n- \"Get technical_service details?\" -> GET /service_dependencies/technical_services/{id}\n- \"Search services?\" -> GET /services\n- \"Create a convert?\" -> POST /services/{id}/rules/convert\n- \"List all session_configurations?\" -> GET /session_configurations\n- \"List all standards?\" -> GET /standards\n- \"Update a standard?\" -> PUT /standards/{id}\n- \"Get score details?\" -> GET /standards/scores/{resource_type}\n- \"List all status_dashboards?\" -> GET /status_dashboards\n- \"Get status_dashboard details?\" -> GET /status_dashboards/{id}\n- \"List all service_impacts?\" -> GET /status_dashboards/{id}/service_impacts\n- \"Get url_slug details?\" -> GET /status_dashboards/url_slugs/{url_slug}\n- \"List all status_pages?\" -> GET /status_pages\n- \"Get impact details?\" -> GET /status_pages/{id}/impacts/{impact_id}\n- \"List all severities?\" -> GET /status_pages/{id}/severities\n- \"Get severity details?\" -> GET /status_pages/{id}/severities/{severity_id}\n- \"List all statuses?\" -> GET /status_pages/{id}/statuses\n- \"Get statuse details?\" -> GET /status_pages/{id}/statuses/{status_id}\n- \"List all posts?\" -> GET /status_pages/{id}/posts\n- \"Create a post?\" -> POST /status_pages/{id}/posts\n- \"Get post details?\" -> GET /status_pages/{id}/posts/{post_id}\n- \"Update a post?\" -> PUT /status_pages/{id}/posts/{post_id}\n- \"Delete a post?\" -> DELETE /status_pages/{id}/posts/{post_id}\n- \"List all post_updates?\" -> GET /status_pages/{id}/posts/{post_id}/post_updates\n- \"Create a post_update?\" -> POST /status_pages/{id}/posts/{post_id}/post_updates\n- \"Get post_update details?\" -> GET /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}\n- \"Update a post_update?\" -> PUT /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}\n- \"Delete a post_update?\" -> DELETE /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}\n- \"List all postmortem?\" -> GET /status_pages/{id}/posts/{post_id}/postmortem\n- \"Create a postmortem?\" -> POST /status_pages/{id}/posts/{post_id}/postmortem\n- \"List all subscriptions?\" -> GET /status_pages/{id}/subscriptions\n- \"Create a subscription?\" -> POST /status_pages/{id}/subscriptions\n- \"Get subscription details?\" -> GET /status_pages/{id}/subscriptions/{subscription_id}\n- \"Delete a subscription?\" -> DELETE /status_pages/{id}/subscriptions/{subscription_id}\n- \"List all memories?\" -> GET /sre_agent/memories\n- \"Update a memory?\" -> PUT /sre_agent/memories/{id}\n- \"Delete a memory?\" -> DELETE /sre_agent/memories/{id}\n- \"Search tags?\" -> GET /tags\n- \"Create a tag?\" -> POST /tags\n- \"Get tag details?\" -> GET /tags/{id}\n- \"Delete a tag?\" -> DELETE /tags/{id}\n- \"Search teams?\" -> GET /teams\n- \"Update a team?\" -> PUT /teams/{id}\n- \"List all members?\" -> GET /teams/{id}/members\n- \"List all notification_subscriptions?\" -> GET /teams/{id}/notification_subscriptions\n- \"Create a notification_subscription?\" -> POST /teams/{id}/notification_subscriptions\n- \"Delete a user?\" -> DELETE /teams/{id}/users/{user_id}\n- \"Update a user?\" -> PUT /teams/{id}/users/{user_id}\n- \"Search templates?\" -> GET /templates\n- \"Create a template?\" -> POST /templates\n- \"Get template details?\" -> GET /templates/{id}\n- \"Update a template?\" -> PUT /templates/{id}\n- \"Delete a template?\" -> DELETE /templates/{id}\n- \"Create a render?\" -> POST /templates/{id}/render\n- \"List all fields?\" -> GET /templates/fields\n- \"Search users?\" -> GET /users\n- \"Get user details?\" -> GET /users/{id}\n- \"List all contact_methods?\" -> GET /users/{id}/contact_methods\n- \"Create a contact_method?\" -> POST /users/{id}/contact_methods\n- \"Get contact_method details?\" -> GET /users/{id}/contact_methods/{contact_method_id}\n- \"Delete a contact_method?\" -> DELETE /users/{id}/contact_methods/{contact_method_id}\n- \"Update a contact_method?\" -> PUT /users/{id}/contact_methods/{contact_method_id}\n- \"List all oauth_delegations?\" -> GET /users/{id}/oauth_delegations\n- \"Get oauth_delegation details?\" -> GET /users/{id}/oauth_delegations/{delegation_id}\n- \"List all license?\" -> GET /users/{id}/license\n- \"List all notification_rules?\" -> GET /users/{id}/notification_rules\n- \"Create a notification_rule?\" -> POST /users/{id}/notification_rules\n- \"Get notification_rule details?\" -> GET /users/{id}/notification_rules/{notification_rule_id}\n- \"Delete a notification_rule?\" -> DELETE /users/{id}/notification_rules/{notification_rule_id}\n- \"Update a notification_rule?\" -> PUT /users/{id}/notification_rules/{notification_rule_id}\n- \"List all oncall_handoff_notification_rules?\" -> GET /users/{id}/oncall_handoff_notification_rules\n- \"Create a oncall_handoff_notification_rule?\" -> POST /users/{id}/oncall_handoff_notification_rules\n- \"Get oncall_handoff_notification_rule details?\" -> GET /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id}\n- \"Delete a oncall_handoff_notification_rule?\" -> DELETE /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id}\n- \"Update a oncall_handoff_notification_rule?\" -> PUT /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id}\n- \"List all sessions?\" -> GET /users/{id}/sessions\n- \"Get session details?\" -> GET /users/{id}/sessions/{type}/{session_id}\n- \"Delete a session?\" -> DELETE /users/{id}/sessions/{type}/{session_id}\n- \"List all status_update_notification_rules?\" -> GET /users/{id}/status_update_notification_rules\n- \"Create a status_update_notification_rule?\" -> POST /users/{id}/status_update_notification_rules\n- \"Get status_update_notification_rule details?\" -> GET /users/{id}/status_update_notification_rules/{status_update_notification_rule_id}\n- \"Delete a status_update_notification_rule?\" -> DELETE /users/{id}/status_update_notification_rules/{status_update_notification_rule_id}\n- \"Update a status_update_notification_rule?\" -> PUT /users/{id}/status_update_notification_rules/{status_update_notification_rule_id}\n- \"List all me?\" -> GET /users/me\n- \"List all vendors?\" -> GET /vendors\n- \"List all schedules?\" -> GET /v3/schedules\n- \"List all custom_shifts?\" -> GET /v3/schedules/{id}/custom_shifts\n- \"Create a custom_shift?\" -> POST /v3/schedules/{id}/custom_shifts\n- \"Get custom_shift details?\" -> GET /v3/schedules/{id}/custom_shifts/{custom_shift_id}\n- \"Update a custom_shift?\" -> PUT /v3/schedules/{id}/custom_shifts/{custom_shift_id}\n- \"Delete a custom_shift?\" -> DELETE /v3/schedules/{id}/custom_shifts/{custom_shift_id}\n- \"Get override details?\" -> GET /v3/schedules/{id}/overrides/{override_id}\n- \"Update a override?\" -> PUT /v3/schedules/{id}/overrides/{override_id}\n- \"List all rotations?\" -> GET /v3/schedules/{id}/rotations\n- \"Create a rotation?\" -> POST /v3/schedules/{id}/rotations\n- \"Get rotation details?\" -> GET /v3/schedules/{id}/rotations/{rotation_id}\n- \"Delete a rotation?\" -> DELETE /v3/schedules/{id}/rotations/{rotation_id}\n- \"List all events?\" -> GET /v3/schedules/{id}/rotations/{rotation_id}/events\n- \"Create a event?\" -> POST /v3/schedules/{id}/rotations/{rotation_id}/events\n- \"Get event details?\" -> GET /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id}\n- \"Update a event?\" -> PUT /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id}\n- \"Delete a event?\" -> DELETE /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id}\n- \"Get vendor details?\" -> GET /vendors/{id}\n- \"List all webhook_subscriptions?\" -> GET /webhook_subscriptions\n- \"Create a webhook_subscription?\" -> POST /webhook_subscriptions\n- \"Get webhook_subscription details?\" -> GET /webhook_subscriptions/{id}\n- \"Update a webhook_subscription?\" -> PUT /webhook_subscriptions/{id}\n- \"Delete a webhook_subscription?\" -> DELETE /webhook_subscriptions/{id}\n- \"Create a ping?\" -> POST /webhook_subscriptions/{id}/ping\n- \"List all oauth_clients?\" -> GET /webhook_subscriptions/oauth_clients\n- \"Create a oauth_client?\" -> POST /webhook_subscriptions/oauth_clients\n- \"Get oauth_client details?\" -> GET /webhook_subscriptions/oauth_clients/{id}\n- \"Update a oauth_client?\" -> PUT /webhook_subscriptions/oauth_clients/{id}\n- \"Delete a oauth_client?\" -> DELETE /webhook_subscriptions/oauth_clients/{id}\n- \"List all connections?\" -> GET /workflows/integrations/connections\n- \"Create a connection?\" -> POST /workflows/integrations/{integration_id}/connections\n- \"Get connection details?\" -> GET /workflows/integrations/{integration_id}/connections/{id}\n- \"Partially update a connection?\" -> PATCH /workflows/integrations/{integration_id}/connections/{id}\n- \"Delete a connection?\" -> DELETE /workflows/integrations/{integration_id}/connections/{id}\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Paginated endpoints accept limit/offset or cursor parameters\n- Create/update endpoints return the modified resource on success\n- Error responses include status codes and descriptions in the spec\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api PagerDuty API\n@base https://api.pagerduty.com\n@version 2.0.0\n@auth ApiKey Authorization in header\n@endpoints 420\n@hint download_for_search\n@toc {entity_type}(2), abilities(2), addons(5), alert_grouping_settings(5), analytics(16), audit(1), automation_actions(25), business_services(16), change_events(4), escalation_policies(6), event_orchestrations(39), extension_schemas(2), extensions(6), incident_workflows(15), incidents(53), license_allocations(1), licenses(1), log_entries(3), maintenance_windows(5), notifications(1), oauth_delegations(2), oncalls(1), paused_incident_reports(2), priorities(1), rulesets(10), schedules(35), service_dependencies(4), services(30), session_configurations(3), standards(4), status_dashboards(5), status_pages(27), sre_agent(3), tags(5), teams(14), templates(7), users(37), vendors(2), webhook_subscriptions(12), workflows(8)\n\n@group {entity_type}\n@endpoint POST /{entity_type}/{id}/change_tags\n@desc Assign tags\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, entity_type: str(users/teams/escalation_policies) # Type of entity related with the tag, id: str # The ID of the resource.}\n@optional {add: [map{type!: str, label: str, id: str}] # Array of tags and/or tag references to add to the entity. For elements with type `tag_reference`, the tag with the corresponding `id` is added to the entity. For elements with type `tag`, if there is an existing tag with the given label that tag is added to the entity. If there is no existing tag with that label and the user has permission to create tags, a new tag is created with that label and assigned to the entity., remove: [map{type!: str, id!: str}] # Array of tag references to remove from the entity.}\n@returns(200) The tags were added and/or removed.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"add\":[{\"type\":\"tag\",\"label\":\"Batman\"},{\"type\":\"tag_reference\",\"id\":\"P5IYCNZ\"}],\"remove\":[{\"type\":\"tag_reference\",\"id\":\"POE7RY8\"},{\"type\":\"tag_reference\",\"id\":\"PG68P1M\"}]}\n\n@endpoint GET /{entity_type}/{id}/tags\n@desc Get tags for entities\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, entity_type: str(users/teams/escalation_policies) # Type of entity related with the tag, id: str # The ID of the resource.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) An array of tags.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group abilities\n@endpoint GET /abilities\n@desc List abilities\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) An array of ability names.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /abilities/{id}\n@desc Test an ability\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The account has the requested ability.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group addons\n@endpoint GET /addons\n@desc List installed Add-ons\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., include[]: str # Array of additional Models to include in response., service_ids[]: [str] # Filters the results, showing only Add-ons for the given services, filter: str(full_page_addon/incident_show_addon) # Filters the results, showing only Add-ons of the given type}\n@returns(200) A paginated array of installed Add-ons.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /addons\n@desc Install an Add-on\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, addon: any}\n@returns(201) {addon: any} # The Add-on that was installed.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"addon\":{\"type\":\"full_page_addon\",\"name\":\"Internal Status Page\",\"src\":\"https://intranet.example.com/status\"}}\n\n@endpoint GET /addons/{id}\n@desc Get an Add-on\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {addon: any} # The requested Add-on.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /addons/{id}\n@desc Delete an Add-on\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The Add-on was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /addons/{id}\n@desc Update an Add-on\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., addon: any}\n@returns(200) {addon: any} # The Add-on that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"addon\":{\"type\":\"full_page_addon\",\"name\":\"Internal Status Page\",\"src\":\"https://intranet.example.com/status\"}}\n\n@endgroup\n\n@group alert_grouping_settings\n@endpoint GET /alert_grouping_settings\n@desc List alert grouping settings\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {after: str # Cursor to retrieve next page; only present if next page exists., before: str # Cursor to retrieve previous page; only present if not on first page., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., limit: int # The number of results per page., service_ids[]: [str] # An array of service IDs. Only results related to these services will be returned.}\n@returns(200) An array of alert grouping settings.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.}\n\n@endpoint POST /alert_grouping_settings\n@desc Create an Alert Grouping Setting\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, alert_grouping_setting: map{id: str, name: str, description: str, type: str, config: any, services: [any], created_at: str(date-time), updated_at: str(date-time)} # Defines how alerts will be automatically grouped into incidents based on the configurations defined. Note that the Alert Grouping Setting features are available only on certain plans.}\n@returns(201) {alert_grouping_setting: map{id: str, name: str?, description: str?, type: str, config: any, services: [any], created_at: str(date-time), updated_at: str(date-time)}} # The new Alert Grouping Setting.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n@example_request {\"alert_grouping_setting\":{\"id\":\"PZC4OM1\",\"name\":\"Example of Alert Grouping Setting\",\"description\":\"This Alert Grouping Setting is an example\",\"type\":\"content_based\",\"config\":{\"time_window\":900,\"aggregate\":\"all\",\"fields\":[\"summary\",\"component\",\"custom_details.host\",\"custom_details.field1.field2\"]},\"services\":[{\"id\":\"P0KJZ0A\"},{\"id\":\"PA15YRT\"}]}}\n\n@endpoint GET /alert_grouping_settings/{id}\n@desc Get an Alert Grouping Setting\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {alert_grouping_setting: map{id: str, name: str?, description: str?, type: str, config: any, services: [any], created_at: str(date-time), updated_at: str(date-time)}} # The Alert Grouping Setting.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 404: The requested resource was not found.}\n\n@endpoint DELETE /alert_grouping_settings/{id}\n@desc Delete an Alert Grouping Setting\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The Alert Grouping Setting was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 404: The requested resource was not found.}\n\n@endpoint PUT /alert_grouping_settings/{id}\n@desc Update an Alert Grouping Setting\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., alert_grouping_setting: map{id: str, name: str, description: str, type: str, config: any, services: [any], created_at: str(date-time), updated_at: str(date-time)} # Defines how alerts will be automatically grouped into incidents based on the configurations defined. Note that the Alert Grouping Setting features are available only on certain plans.}\n@returns(200) {alert_grouping_setting: map{id: str, name: str?, description: str?, type: str, config: any, services: [any], created_at: str(date-time), updated_at: str(date-time)}} # The updated Alert Grouping Setting.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 404: The requested resource was not found.}\n@example_request {\"alert_grouping_setting\":{\"id\":\"PZC4OM1\",\"name\":\"Example of Alert Grouping Setting\",\"description\":\"This Alert Grouping Setting is an example\",\"type\":\"content_based\",\"config\":{\"time_window\":900,\"aggregate\":\"all\",\"fields\":[\"summary\",\"component\",\"custom_details.host\",\"custom_details.field1.field2\"]},\"services\":[{\"id\":\"P0KJZ0A\"},{\"id\":\"PA15YRT\"}]}}\n\n@endgroup\n\n@group analytics\n@endpoint POST /analytics/metrics/incidents/all\n@desc Get aggregated incident data\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2024-01-01T00:00:00-05:00\",\"created_at_end\":\"2024-01-31T00:00:00-05:00\",\"urgency\":\"high\",\"major\":true,\"team_ids\":[\"PGVXG6U\",\"PNVU4U4\"],\"service_ids\":[\"PQVUB8D\",\"PU2D9X3\"]},\"aggregate_unit\":\"day\",\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/incidents/escalation_policies\n@desc Get aggregated escalation policy data\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) Only returns data for escalation policies that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-10T00:00:00-07:00\",\"created_at_end\":\"2023-06-11T23:59:59-07:00\",\"urgency\":\"high\",\"major\":true,\"escalation_policy_ids\":[\"PDESCP1\",\"PDESCP2\"]},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/incidents/escalation_policies/all\n@desc Get aggregated metrics for all escalation policies\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) Only returns data for escalation policies that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-17T00:00:00-07:00\",\"created_at_end\":\"2023-07-01T23:59:59-07:00\",\"escalation_policy_ids\":[\"PDESCP1\",\"PDESCP2\"]},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/incidents/services\n@desc Get aggregated service data\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) Only returns data for services that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-10T00:00:00-07:00\",\"created_at_end\":\"2023-06-11T23:59:59-07:00\",\"urgency\":\"high\",\"major\":true,\"team_ids\":[\"P3XUQ75\"],\"service_ids\":[\"PPSCXAN\"]},\"aggregate_unit\":\"day\",\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/incidents/services/all\n@desc Get aggregated metrics for all services\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) Only returns data for services that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-17T00:00:00-07:00\",\"created_at_end\":\"2023-07-01T23:59:59-07:00\",\"service_ids\":[\"PQVUB8D\",\"PU2D9X3\"]},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/incidents/teams\n@desc Get aggregated team data\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) Only returns data for teams that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-10T00:00:00-07:00\",\"created_at_end\":\"2023-06-11T23:59:59-07:00\",\"urgency\":\"high\",\"major\":true,\"team_ids\":[\"P3XUQ75\"]},\"aggregate_unit\":\"day\",\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/incidents/teams/all\n@desc Get aggregated metrics for all teams\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str], pd_advance_used: bool} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by.  If no value is provided, the metrics will be aggregated for the entire period.}\n@returns(200) Only returns data for teams that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-10T00:00:00-07:00\",\"created_at_end\":\"2023-06-11T23:59:59-07:00\",\"urgency\":\"high\",\"major\":true,\"team_ids\":[\"P3XUQ75\"]},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/pd_advance_usage/features\n@desc Get aggregated PD Advance usage data\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, incident_created_at_start: str, incident_created_at_end: str, urgency: str, major: bool, min_ackowledgements: int, min_timeout_escalations: int, min_manual_escalations: int, team_ids: [str], service_ids: [str], escalation_policy_ids: [str], priority_ids: [str], priority_names: [str]} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results., time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"incident_created_at_start\":\"2024-01-01T00:00:00-05:00\",\"incident_created_at_end\":\"2024-01-31T00:00:00-05:00\",\"urgency\":\"high\",\"major\":true},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/responders/all\n@desc Get aggregated metrics for all responders\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{date_range_start: str, date_range_end: str, urgency: str, team_ids: [str], responder_ids: [str], priority_ids: [str], priority_names: [str]} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results, time_zone: str # The time zone to use for the results and grouping., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results.}\n@returns(200) Only returns data for responders that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"date_range_start\":\"2023-06-10T00:00:00-07:00\",\"date_range_end\":\"2023-06-11T23:59:59-07:00\",\"urgency\":\"high\",\"responder_ids\":[\"PDUSER1\",\"PDUSER2\"]},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/responders/teams\n@desc Get responder data aggregated by team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{date_range_start: str, date_range_end: str, urgency: str, team_ids: [str], responder_ids: [str], priority_ids: [str], priority_names: [str]} # Accepts a set of filters to apply to the Incidents before aggregating.  Any incidents that do not match the included filters will be omitted from the results, time_zone: str # The time zone to use for the results and grouping., order: str(asc/desc) # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str # The column that was used for ordering the results.}\n@returns(200) Only returns data for responders and teams that match the filters and have data.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"date_range_start\":\"2023-06-10T00:00:00-07:00\",\"date_range_end\":\"2023-06-11T23:59:59-07:00\",\"urgency\":\"high\",\"responder_ids\":[\"PDUSER1\",\"PDUSER2\"]},\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/metrics/users/all\n@desc Get aggregated metrics for all users\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str(date-time), created_at_end: str(date-time), team_ids: [str], user_ids: [str], role_ids: [str]}, time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc)=desc # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str=user_id # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by. If no value is provided, the metrics will be aggregated for the entire period., limit: int=1000 # The maximum number of results to return per page. The default (and maximum allowed value) is 1000., starting_after: str # A cursor used for pagination. Starting after cursor provides the next set of results in forward pagination order., ending_before: str # A cursor used for pagination. Ending before cursor provides the previous set of results in reverse pagination order.}\n@returns(200) {data: [map], filters: map{created_at_start: str(date-time), created_at_end: str(date-time), team_ids: [str]}, time_zone: str} # Returns user metrics aggregated across the account\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2024-08-07T00:00:00-07:00\",\"created_at_end\":\"2025-08-05T23:59:59-07:00\"},\"time_zone\":\"America/Chicago\"}\n\n@endpoint POST /analytics/raw/incidents\n@desc Get raw data - multiple incidents\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, updated_after: str, urgency: str, major: bool, team_ids: [str], service_ids: [str], priority_ids: [str], priority_names: [str], incident_type_ids: [str]} # Filters the result, only show incidents that match the conditions passed in the filter., starting_after: str # A cursor to indicate the reference point that the results should follow, ending_before: str # A cursor to indicate the reference point that the results should precede, order: str(asc/desc) # The order the results;  asc for ascending, desc for descending. Defaults to 'desc'., order_by: str(created_at/seconds_to_resolve) # The column to use for ordering the results. Defaults to 'created_at'., limit: int # Number of results to include in each batch. Limits between 1 to 1000 are accepted., time_zone: str # The time zone to use for the results.}\n@returns(200) {first: str, last: str, limit: int, more: bool, order: str, order_by: str, filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, team_ids: [str], service_ids: [str], priority_ids: [str], priority_names: [str], incident_type_ids: [str]}, time_zone: str, data: [map]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2024-01-01T00:00:00-05:00\",\"created_at_end\":\"2024-01-31T00:00:00-05:00\",\"updated_after\":\"2024-05-01T00:00:00-05:00\",\"urgency\":\"high\",\"major\":true,\"team_ids\":[\"PGVXG6U\",\"PNVU4U4\"],\"service_ids\":[\"PQVUB8D\",\"PU2D9X3\"],\"priority_names\":[\"P1\",\"P2\"],\"incident_type_ids\":[\"PIJ90N7\",\"PKL73Z2\"]},\"limit\":20,\"order\":\"desc\",\"order_by\":\"created_at\",\"time_zone\":\"Etc/UTC\"}\n\n@endpoint GET /analytics/raw/incidents/{id}\n@desc Get raw data - single incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {acknowledged_user_ids: [str], acknowledged_user_names: [str], acknowledgement_count: int, active_user_count: int, assigned_user_ids: [str], assigned_user_names: [str], assignment_count: int, auto_resolved: bool, business_hour_interruptions: int, created_at: str, updated_at: str, description: str, engaged_seconds: int, engaged_user_count: int, escalation_count: int, escalation_policy_id: str, escalation_policy_name: str, id: str, incident_number: int, incident_type_id: str, incident_type_name: str, joined_user_ids: [str], joined_user_names: [str], major: bool, manual_escalation_count: int, off_hour_interruptions: int, priority_id: str?, priority_name: str?, priority_order: int?, reassignment_count: int, resolved_at: str, resolved_by_user_id: str, resolved_by_user_name: str, seconds_to_engage: int, seconds_to_first_ack: int, seconds_to_mobilize: int, seconds_to_resolve: int, service_id: str, service_name: str, sleep_hour_interruptions: int, snoozed_seconds: int, status: str, team_id: str?, team_name: str?, timeout_escalation_count: int, total_interruptions: int, total_notifications: int, urgency: str, user_defined_effort_seconds: int?}\n@errors {404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /analytics/raw/incidents/{id}/responses\n@desc Get raw responses from a single incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # Number of results to include in each batch. Limits between 1 to 1000 are accepted., order: str(asc/desc) # The order in which to display the results; asc for ascending, desc for descending. Defaults to `desc`., order_by: str # The column to use for ordering the results., time_zone: str # The time zone to use for the results.}\n@returns(200) {incident_id: str, limit: int, order: str, order_by: str, time_zone: str, responses: [map]}\n@errors {404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"limit\":20,\"order\":\"desc\",\"order_by\":\"requested_at\",\"time_zone\":\"America/Los_Angeles\"}\n\n@endpoint POST /analytics/raw/responders/{responder_id}/incidents\n@desc Get raw incidents for a single responder_id\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, team_ids: [str], service_ids: [str], priority_ids: [str], priority_names: [str], incident_type_ids: [str]} # Filters the result, only show incidents that match the conditions passed in the filter., starting_after: str # A cursor to indicate the reference point that the results should follow, ending_before: str # A cursor to indicate the reference point that the results should precede, order: str(asc/desc) # The order in which to display the results; asc for ascending, desc for descending. Defaults to `desc`., order_by: str # The column to use for ordering the results. Defaults to `incident_created_at`., limit: int # Number of results to include in each batch. Limits between 1 to 1000 are accepted., time_zone: str # The time zone to use for the results.}\n@returns(200) {first: str, last: str, responder_id: str, limit: int, order: str, order_by: str, time_zone: str, filters: map{created_at_start: str, created_at_end: str, urgency: str, major: bool, team_ids: [str], service_ids: [str], priority_ids: [str], priority_names: [str], incident_type_ids: [str]}, data: [map]}\n@errors {404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2023-06-10T00:00:00-07:00\",\"created_at_end\":\"2023-06-11T23:59:59-07:00\",\"incident_type_ids\":[\"PIJ90N7\",\"PKL73Z2\"]},\"responder_id\":\"PDUSER1\",\"limit\":100,\"order\":\"asc\",\"order_by\":\"incident_created_at\",\"time_zone\":\"Etc/UTC\"}\n\n@endpoint POST /analytics/raw/users\n@desc Get raw user analytics data\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filters: map{created_at_start: str(date-time), created_at_end: str(date-time), team_ids: [str], user_ids: [str], role_ids: [str]}, time_zone: str # The time zone to use for the results and grouping. Must be in tzdata format. See list of accepted values [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)., order: str(asc/desc)=desc # The order in which the results were sorted; asc for ascending, desc for descending., order_by: str=user_id # The column that was used for ordering the results., aggregate_unit: str(day/week/month) # The time unit to aggregate metrics by. If no value is provided, the metrics will be aggregated for the entire period., limit: int=1000 # The maximum number of results to return per page. The default (and maximum allowed value) is 1000., starting_after: str # A cursor used for pagination. Starting after cursor provides the next set of results in forward pagination order., ending_before: str # A cursor used for pagination. Ending before cursor provides the previous set of results in reverse pagination order.}\n@returns(200) {first: str, last: str, limit: int, more: bool, order: str, order_by: str, filters: map{created_at_start: str, created_at_end: str, team_ids: [str], roles: [str]}, time_zone: str, data: [map]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"filters\":{\"created_at_start\":\"2025-01-01T00:00:00Z\",\"created_at_end\":\"2025-09-01T00:00:00Z\"},\"limit\":10}\n\n@endgroup\n\n@group audit\n@endpoint GET /audit/records\n@desc List audit records\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., since: str(date-time) # The start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours), until: str(date-time) # The end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`., root_resource_types[]: str(users/teams/schedules/escalation_policies/services) # Resource type filter for the root_resource., actor_type: str(user_reference/api_key_reference/app_reference) # Actor type filter., actor_id: str # Actor Id filter. Must be qualified by providing the `actor_type` param., method_type: str(browser/oauth/api_token/identity_provider/other) # Method type filter., method_truncated_token: str # Method truncated_token filter. Must be qualified by providing the `method_type` param., actions[]: str(create/update/delete) # Action filter}\n@returns(200) Records matching the query criteria.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group automation_actions\n@endpoint POST /automation_actions/actions\n@desc Create an Automation Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, action: any}\n@returns(201) {action: any} # Action information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"action\":{\"name\":\"Restart apache\",\"description\":\"Restarts apache on the us-west-2-shopping-cart host\",\"action_type\":\"script\",\"action_data_reference\":{\"script\":\"java --version\"},\"teams\":[{\"id\":\"PQ9K7I8\",\"type\":\"team_reference\"}],\"services\":[{\"id\":\"PRDRWUJ\",\"type\":\"service_reference\"}]}}\n\n@endpoint GET /automation_actions/actions\n@desc List Automation Actions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., name: str # Filters results to include the ones matching the name (case insensitive substring matching), runner_id: str # Filters results to include the ones linked to the specified runner. Specifying the value `any` filters results to include the ones linked to runners only, thus omitting the results not linked to runners., classification: str # Filters results to include the ones matching the specified classification (aka category), team_id: str # Filters results to include the ones associated with the specified team., service_id: str # Filters results to include the ones associated with the specified service, action_type: str(script/process_automation) # Filters results to include the ones matching the specified action type}\n@returns(200) An array of actions\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /automation_actions/actions/{id}\n@desc Get an Automation Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {action: any} # Action information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint DELETE /automation_actions/actions/{id}\n@desc Delete an Automation Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) Deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /automation_actions/actions/{id}\n@desc Update an Automation Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., action: any}\n@returns(200) {action: any} # Action information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /automation_actions/actions/{id}/invocations\n@desc Create an Invocation\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., invocation: map{metadata!: map}}\n@returns(201) {invocation: any} # Created invocation\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"invocation\":{\"metadata\":{\"incident_id\":\"Q2LAR4ADCXC8IB\"}}}\n\n@endpoint GET /automation_actions/actions/{id}/services\n@desc Get all service references associated with an Automation Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {services: [any]} # An array of service references\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /automation_actions/actions/{id}/services\n@desc Associate an Automation Action with a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., service: any}\n@returns(201) {service: any} # The action-service association was created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"service\":{\"id\":\"PRDRWUJ\",\"type\":\"service_reference\"}}\n\n@endpoint GET /automation_actions/actions/{id}/services/{service_id}\n@desc Get the details of an Automation Action / service relation\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., service_id: str # The service ID}\n@returns(200) {service: any} # Service reference\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint DELETE /automation_actions/actions/{id}/services/{service_id}\n@desc Disassociate an Automation Action from a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., service_id: str # The service ID}\n@returns(204) Ok.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /automation_actions/actions/{id}/teams\n@desc Associate an Automation Action with a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team: any}\n@returns(201) {team: any} # The action-team association was created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"team\":{\"id\":\"PQ9K7I8\",\"type\":\"team_reference\"}}\n\n@endpoint GET /automation_actions/actions/{id}/teams\n@desc Get all team references associated with an Automation Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {teams: [any]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint DELETE /automation_actions/actions/{id}/teams/{team_id}\n@desc Disassociate an Automation Action from a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team_id: str # The team ID}\n@returns(204) Ok.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /automation_actions/actions/{id}/teams/{team_id}\n@desc Get the details of an Automation Action / team relation\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team_id: str # The team ID}\n@returns(200) {team: any} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /automation_actions/invocations\n@desc List Invocations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {invocation_state: str(prepared/created/sent/queued/running/aborted/completed/error/unknown) # Invocation state, not_invocation_state: str # Invocation state inverse filter (matches invocations NOT in the specified state), incident_id: str # Incident ID, action_id: str # Action ID}\n@returns(200) Invocations matching the criteria\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /automation_actions/invocations/{id}\n@desc Get an Invocation\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {invocation: any} # Invocation information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /automation_actions/runners\n@desc Create an Automation Action runner.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, runner: any}\n@returns(201) {runner: any} # Runner information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"runner\":{\"name\":\"us-west-2 prod sidecar runner\",\"description\":\"us-west-2 prod sidecar runner provisioned by SRE\",\"runner_type\":\"sidecar\",\"teams\":[{\"id\":\"PQ9K7I8\",\"type\":\"team_reference\"}]}}\n\n@endpoint GET /automation_actions/runners\n@desc List Automation Action runners\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., name: str # Filters results to include the ones matching the name (case insensitive substring matching), include[]: [str] # Includes additional data elements into the response}\n@returns(200) Runners matching the criteria.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /automation_actions/runners/{id}\n@desc Get an Automation Action runner\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {runner: any} # Runner information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /automation_actions/runners/{id}\n@desc Update an Automation Action runner\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., runner: any}\n@returns(200) {runner: any} # Runner information\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"runner\":{\"name\":\"us-west-2 prod sidecar runner\",\"description\":\"us-west-2 prod sidecar runner provisioned by SRE\"}}\n\n@endpoint DELETE /automation_actions/runners/{id}\n@desc Delete an Automation Action runner\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) Deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /automation_actions/runners/{id}/teams\n@desc Associate a runner with a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team: any}\n@returns(201) {team: any} # The runner-team association that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"team\":{\"id\":\"PQ9K7I8\",\"type\":\"team_reference\"}}\n\n@endpoint GET /automation_actions/runners/{id}/teams\n@desc Get all team references associated with a runner\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {teams: [any]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint DELETE /automation_actions/runners/{id}/teams/{team_id}\n@desc Disassociate a runner from a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team_id: str # The team ID}\n@returns(204) Ok.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /automation_actions/runners/{id}/teams/{team_id}\n@desc Get the details of a runner / team relation\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team_id: str # The team ID}\n@returns(200) {team: any} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group business_services\n@endpoint GET /business_services\n@desc List Business Services\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) A paginated array of services.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint POST /business_services\n@desc Create a Business Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {business_service: map{name: str, description: str, point_of_contact: str, team: map} # The Business Service to be created}\n@returns(200) {business_service: any} # The Business Service that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"business_service\":{\"name\":\"Self-serve mobile checkout\",\"description\":\"Checkout service for our mobile clients\",\"point_of_contact\":\"PagerDuty Admin\",\"team\":{\"id\":\"P3ZQXDF\"}}}\n\n@endpoint GET /business_services/{id}\n@desc Get a Business Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {business_service: any} # The service business requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint DELETE /business_services/{id}\n@desc Delete a Business Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The Business Service was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /business_services/{id}\n@desc Update a Business Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {business_service: map{name: str, description: str, point_of_contact: str, team: map} # The Business Service to be created}\n@returns(200) {business_service: any} # The Business Service that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"business_service\":{\"name\":\"Self-serve mobile checkout\",\"description\":\"Checkout service for our mobile clients\",\"point_of_contact\":\"PagerDuty Admin\",\"team\":{\"id\":\"P3ZQXDF\"}}}\n\n@endpoint POST /business_services/{id}/account_subscription\n@desc Create Business Service Account Subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) {account_is_subscribed: bool} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 422: Unprocessable Entity. Some arguments failed validation checks.}\n\n@endpoint DELETE /business_services/{id}/account_subscription\n@desc Delete Business Service Account Subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(204) The account was unsubscribed successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 422: Unprocessable Entity. Some arguments failed validation checks.}\n\n@endpoint GET /business_services/{id}/subscribers\n@desc List Business Service Subscribers\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /business_services/{id}/subscribers\n@desc Create Business Service Subscribers\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribers: [map{subscriber_id: str, subscriber_type: str}]}\n@returns(200) {subscriptions: [map]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribers\":[{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"team\"},{\"subscriber_id\":\"PD1235\",\"subscriber_type\":\"team\"},{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"user\"}]}\n\n@endpoint GET /business_services/{id}/supporting_services/impacts\n@desc List the supporting Business Services for the given Business Service Id, sorted by impacted status.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {additional_fields[]: str(services.highest_impacting_priority/total_impacted_count): any # Provides access to additional fields such as highest priority per business service and total impacted count, ids[]: str # The IDs of the resources.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /business_services/{id}/unsubscribe\n@desc Remove Business Service Subscribers\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribers: [map{subscriber_id: str, subscriber_type: str}]}\n@returns(200) {deleted_count: num, unauthorized_count: num, non_existent_count: num} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribers\":[{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"team\"},{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"user\"}]}\n\n@endpoint GET /business_services/impactors\n@desc List Impactors affecting Business Services\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {ids[]: str: any # The IDs of the resources.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /business_services/impacts\n@desc List Business Services sorted by impacted status\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {additional_fields[]: str(services.highest_impacting_priority/total_impacted_count): any # Provides access to additional fields such as highest priority per business service and total impacted count, ids[]: str # The IDs of the resources.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /business_services/priority_thresholds\n@desc Get the global priority threshold for a Business Service to be considered impacted by an Incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@returns(200) {global_threshold: map?{id: str, order: int}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /business_services/priority_thresholds\n@desc Deletes the account-level priority threshold for Business Service impact\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@returns(204) The Priority Threshold for the account was successfully cleared.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /business_services/priority_thresholds\n@desc Set the Account-level priority threshold for Business Service impact.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., global_threshold: map{id!: str, order!: num}}\n@returns(200) {global_threshold: map{id: str, order: num}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error}\n@example_request {\"global_threshold\":{\"id\":\"PTLNKGF\",\"order\":256}}\n\n@endgroup\n\n@group change_events\n@endpoint GET /change_events\n@desc List Change Events\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., integration_ids[]: [str] # An array of integration IDs. Only results related to these integrations will be returned., since: str(date-time) # The start of the date range over which you want to search, as a UTC ISO 8601 datetime string. Will return an HTTP 400 for non-UTC datetimes., until: str(date-time) # The end of the date range over which you want to search, as a UTC ISO 8601 datetime string. Will return an HTTP 400 for non-UTC datetimes.}\n@returns(200) {change_events: [any]} # The array of Change Events returned by the query.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint POST /change_events\n@desc Create a Change Event\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(202) See [`Send Change Event`](https://developer.pagerduty.com/api-reference/b3A6Mjc0ODI2Ng-send-change-events-to-the-pager-duty-events-api) in the V2 Events API reference.\n\n@endpoint GET /change_events/{id}\n@desc Get a Change Event\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {change_event: any} # The Change Event requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /change_events/{id}\n@desc Update a Change Event\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., change_event: any}\n@returns(200) {change_event: any} # The Change Event that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"change_event\":{\"summary\":\"Build Success - Increase snapshot create timeout to 30 seconds\",\"type\":\"change_event\",\"custom_details\":{\"build_state\":\"passed\",\"build_number\":\"2\",\"run_time\":\"1236s\"}}}\n\n@endgroup\n\n@group escalation_policies\n@endpoint GET /escalation_policies\n@desc List escalation policies\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Filters the result, showing only the records whose name matches the query., user_ids[]: [str] # Filters the results, showing only escalation policies on which any of the users is a target., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., include[]: str(services/teams/targets) # Array of additional Models to include in response., sort_by: str(name/name:asc/name:desc)=name # Used to specify the field you wish to sort the results on.}\n@returns(200) A paginated array of escalation policy objects.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /escalation_policies\n@desc Create an escalation policy\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, escalation_policy: any}\n@optional {From: str(email) # The email address of a valid user associated with the account making the request. This is optional, and is only used for change tracking.}\n@returns(201) {escalation_policy: any} # The escalation policy that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"escalation_policy\":{\"type\":\"escalation_policy\",\"name\":\"Engineering Escalation Policy\",\"escalation_rules\":[{\"escalation_delay_in_minutes\":30,\"targets\":[{\"id\":\"PEYSGVF\",\"type\":\"user_reference\"}],\"escalation_rule_assignment_strategy\":{\"type\":\"round_robin\"}}],\"services\":[{\"id\":\"PIJ90N7\",\"type\":\"service_reference\"}],\"num_loops\":2,\"on_call_handoff_notifications\":\"if_has_services\",\"teams\":[{\"id\":\"PQ9K7I8\",\"type\":\"team_reference\"}],\"description\":\"Here is the ep for the engineering team.\"}}\n\n@endpoint GET /escalation_policies/{id}\n@desc Get an escalation policy\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str(services/teams/targets): any # Array of additional Models to include in response.}\n@returns(200) {escalation_policy: any} # The escalation policy object.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint DELETE /escalation_policies/{id}\n@desc Delete an escalation policy\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The escalation policy was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /escalation_policies/{id}\n@desc Update an escalation policy\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., escalation_policy: any}\n@returns(200) {escalation_policy: any} # The escalation policy that was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"escalation_policy\":{\"type\":\"escalation_policy\",\"name\":\"Engineering Escalation Policy\",\"escalation_rules\":[{\"escalation_delay_in_minutes\":30,\"targets\":[{\"id\":\"PEYSGVF\",\"type\":\"user_reference\"}],\"escalation_rule_assignment_strategy\":{\"type\":\"round_robin\"}}],\"services\":[{\"id\":\"PIJ90N7\",\"type\":\"service_reference\"}],\"num_loops\":2,\"on_call_handoff_notifications\":\"if_has_services\",\"teams\":[{\"id\":\"PQ9K7I8\",\"type\":\"team_reference\"}],\"description\":\"Here is the ep for the engineering team.\"}}\n\n@endpoint GET /escalation_policies/{id}/audit/records\n@desc List audit records for an escalation policy\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., since: str(date-time) # The start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours), until: str(date-time) # The end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`.}\n@returns(200) Records matching the query criteria.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group event_orchestrations\n@endpoint GET /event_orchestrations\n@desc List Event Orchestrations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., sort_by: str(name:asc/name:desc/routes:asc/routes:desc/created_at:asc/created_at:desc)=name:asc # Used to specify the field you wish to sort the results on.}\n@returns(200) A paginated array of Event Orchestration objects.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /event_orchestrations\n@desc Create an Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, orchestration: map{id: str, self: str(url), name: str, description: str, team: map, integrations: [map], routes: int, created_at: str(date-time), created_by: map, updated_at: str(date-time), updated_by: map, version: str}}\n@returns(201) {orchestration: map{id: str, self: str(url), name: str, description: str, team: map{id: str, type: str, self: str(url)}, integrations: [map], routes: int, created_at: str(date-time), created_by: map{id: str, type: str, self: str(url)}, updated_at: str(date-time), updated_by: map{id: str, type: str, self: str(url)}, version: str}} # The Orchestration that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"orchestration\":{\"name\":\"New Orchestration\",\"description\":\"This is a newly created orchestration\",\"team\":{\"id\":\"PXD0WR8\"}}}\n\n@endpoint GET /event_orchestrations/{id}\n@desc Get an Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) {orchestration: map{id: str, self: str(url), name: str, description: str, team: map{id: str, type: str, self: str(url)}, integrations: [map], routes: int, created_at: str(date-time), created_by: map{id: str, type: str, self: str(url)}, updated_at: str(date-time), updated_by: map{id: str, type: str, self: str(url)}, version: str}} # The Orchestration object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/{id}\n@desc Update an Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., orchestration: map{id: str, self: str(url), name: str, description: str, team: map, integrations: [map], routes: int, created_at: str(date-time), created_by: map, updated_at: str(date-time), updated_by: map, version: str}}\n@returns(200) {orchestration: map{id: str, self: str(url), name: str, description: str, team: map{id: str, type: str, self: str(url)}, integrations: [map], routes: int, created_at: str(date-time), created_by: map{id: str, type: str, self: str(url)}, updated_at: str(date-time), updated_by: map{id: str, type: str, self: str(url)}, version: str}} # The Orchestration that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"orchestration\":{\"name\":\"Go-Kart Orchestration\"}}\n\n@endpoint DELETE /event_orchestrations/{id}\n@desc Delete an Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(204) The Orchestration was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n\n@endpoint GET /event_orchestrations/{id}/integrations\n@desc List Integrations for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) {integrations: [map], total: int?} # The Integrations for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n\n@endpoint POST /event_orchestrations/{id}/integrations\n@desc Create an Integration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., integration: map{label!: str}}\n@returns(201) {integration: map{id: str, label: str, parameters: map{routing_key: str, type: str}}} # The Integration that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"integration\":{\"label\":\"Integration for Monitoring Tool X\"}}\n\n@endpoint GET /event_orchestrations/{id}/integrations/{integration_id}\n@desc Get an Integration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., integration_id: str # The ID of an Integration.}\n@returns(200) {integration: map{id: str, label: str, parameters: map{routing_key: str, type: str}}} # An Integration for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n\n@endpoint PUT /event_orchestrations/{id}/integrations/{integration_id}\n@desc Update an Integration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., integration_id: str # The ID of an Integration., integration: map{label!: str}}\n@returns(200) {integration: map{id: str, label: str, parameters: map{routing_key: str, type: str}}} # The Integration that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"integration\":{\"label\":\"New Name for my Integration\"}}\n\n@endpoint DELETE /event_orchestrations/{id}/integrations/{integration_id}\n@desc Delete an Integration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., integration_id: str # The ID of an Integration.}\n@returns(204) The Integration was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n\n@endpoint POST /event_orchestrations/{id}/integrations/migration\n@desc Migrate an Integration from one Event Orchestration to another\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., source_id: str # The ID of the Event Orchestration you'll be moving the Integration away from, source_type: str # The type of of the `source_id` object, integration_id: str # The ID of the Integration you'll be moving}\n@returns(200) {integrations: [map], total: int?} # The Integration that was migrated\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"source_type\":\"orchestration\",\"source_id\":\"b02e973d-9620-4e0a-9edc-00fedf7d4694\",\"integration_id\":\"11832872-88b6-4661-8972-db5712b69496\"}\n\n@endpoint GET /event_orchestrations/{id}/global\n@desc Get the Global Orchestration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) The Global Orchestration Rules object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/{id}/global\n@desc Update the Global Orchestration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) The Global Orchestration Rules object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"orchestration_path\":{\"sets\":[{\"id\":\"start\",\"rules\":[{\"label\":\"Always apply some consistent event transformations to all events\",\"id\":\"c91f72f3\",\"conditions\":[],\"actions\":{\"variables\":[{\"name\":\"hostname\",\"path\":\"event.component\",\"value\":\"hostname: (.*)\",\"type\":\"regex\"}],\"extractions\":[{\"template\":\"{{variables.hostname}}\",\"target\":\"event.custom_details.hostname\"},{\"source\":\"event.source\",\"regex\":\"www (.*) service\",\"target\":\"event.source\"}],\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#my-team-channel\"},{\"id\":\"PN1C4A2\",\"value\":\"{{event.timestamp}}\"}],\"route_to\":\"step-two\"}}]},{\"id\":\"step-two\",\"rules\":[{\"label\":\"All critical alerts should be treated as P1 incidents\",\"id\":\"7c54529d\",\"conditions\":[{\"expression\":\"event.severity matches 'critical'\"}],\"actions\":{\"priority\":\"P0IN2KQ\",\"suppress\":false,\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#p1-incident-response\"}]}},{\"label\":\"Drop all events from the very-noisy monitoring tool\",\"id\":\"1f6d9a33\",\"conditions\":[{\"expression\":\"event.source matches part 'very-noisy'\"}],\"actions\":{\"drop_event\":true}},{\"label\":\"Assign all database related incidents to the Database Team's escalation policy\",\"id\":\"4314d9ce\",\"conditions\":[{\"expression\":\"event.source matches 'prod-db'\"}],\"actions\":{\"escalation_policy\":\"PEYSGVF\"}},{\"label\":\"Never bother the on-call for info-level events outside of work hours\",\"id\":\"cd770384\",\"conditions\":[{\"expression\":\"event.severity matches 'info' and not (now in Mon,Tue,Wed,Thu,Fri 09:00:00 to 17:00:00 America/Los_Angeles)\"}],\"actions\":{\"suppress\":true}}]}],\"catch_all\":{\"actions\":{\"suppress\":true},\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#general-incident-notifications\"}]}}}\n\n@endpoint GET /event_orchestrations/{id}/router\n@desc Get the Router for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) The Orchestration Router object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/{id}/router\n@desc Update the Router for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) The Orchestration Router object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"orchestration_path\":{\"sets\":[{\"id\":\"start\",\"rules\":[{\"label\":\"Dynamically route events\",\"id\":\"763110d0\",\"actions\":{\"dynamic_route_to\":{\"source\":\"event.custom_details.pd_service\",\"regex\":\".*\",\"lookup_by\":\"service_name\"}}},{\"label\":\"Events relating to our relational database\",\"id\":\"1c26698b\",\"conditions\":[{\"expression\":\"event.summary matches part 'database'\"},{\"expression\":\"event.source matches regex 'db[0-9]+-server'\"}],\"actions\":{\"route_to\":\"PB31XBA\"}},{\"label\":\"Events relating to our www app server\",\"id\":\"d9801904\",\"conditions\":[{\"expression\":\"event.summary matches part 'www'\"}],\"actions\":{\"route_to\":\"PC2D9ML\"}},{\"label\":\"Events relating to our delivery pipeline\",\"id\":\"ed624931\",\"conditions\":[{\"expression\":\"trigger_count over 1 minute > 3\"}],\"actions\":{\"route_to\":\"PQSJBMA\"}}]}]}}\n\n@endpoint GET /event_orchestrations/{id}/unrouted\n@desc Get the Unrouted Orchestration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) The Unrouted Orchestration object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/{id}/unrouted\n@desc Update the Unrouted Orchestration for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) The Unrouted Orchestration object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"orchestration_path\":{\"sets\":[{\"id\":\"start\",\"rules\":[{\"label\":\"Update the summary of un-matched Critical alerts so they're easier to spot\",\"id\":\"38880ffb\",\"conditions\":[{\"expression\":\"event.severity matches 'critical'\"}],\"actions\":{\"extractions\":[{\"target\":\"event.summary\",\"template\":\"[Critical Unrouted] {{event.summary}}\"}]}},{\"label\":\"Reduce the severity of all other unrouted events\",\"id\":\"3896801e\",\"conditions\":[],\"actions\":{\"severity\":\"info\"}}]}],\"catch_all\":{\"actions\":{\"suppress\":true}}}}\n\n@endpoint GET /event_orchestrations/services/{service_id}\n@desc Get the Service Orchestration for a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID}\n@optional {include[]: str: any # Array of additional Models to include in response.}\n@returns(200) The Service Orchestration object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/services/{service_id}\n@desc Update the Service Orchestration for a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID}\n@returns(200) The Service Orchestration object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"orchestration_path\":{\"sets\":[{\"id\":\"start\",\"rules\":[{\"label\":\"Always apply some consistent event transformations to all events\",\"id\":\"c91f72f3\",\"conditions\":[],\"actions\":{\"variables\":[{\"name\":\"hostname\",\"path\":\"event.component\",\"value\":\"hostname: (.*)\",\"type\":\"regex\"}],\"extractions\":[{\"template\":\"{{variables.hostname}}\",\"target\":\"event.custom_details.hostname\"},{\"source\":\"event.source\",\"regex\":\"www (.*) service\",\"target\":\"event.source\"}],\"pagerduty_automation_actions\":[{\"action_id\":\"01CSB5SMOKCKVRI5GN0LJG7SMB\",\"trigger_types\":[\"alert_triggered\"]}],\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#my-team-channel\"},{\"id\":\"PN1C4A2\",\"value\":\"{{event.timestamp}}\"}],\"route_to\":\"step-two\"}}]},{\"id\":\"step-two\",\"rules\":[{\"label\":\"All critical alerts should be treated as P1 incidents\",\"id\":\"7c54529d\",\"conditions\":[{\"expression\":\"event.severity matches 'critical'\"}],\"actions\":{\"annotate\":\"Please use our P1 runbook: https://docs.test/p1-runbook\",\"priority\":\"P0IN2KQ\",\"suppress\":false,\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#p1-incident-response\"}]}},{\"label\":\"If there's something wrong on the canary let the team know about it in our deployments Slack channel\",\"id\":\"1f6d9a33\",\"conditions\":[{\"expression\":\"event.custom_details.hostname matches part 'canary'\"}],\"actions\":{\"automation_actions\":[{\"name\":\"Canary Slack Notification\",\"url\":\"https://our-slack-listerner.test/send-notification\",\"auto_send\":true,\"headers\":[{\"key\":\"X-Notification-Source\",\"value\":\"PagerDuty Incident Webhook\"}],\"parameters\":[{\"key\":\"channel\",\"value\":\"#my-team-channel\"},{\"key\":\"message\",\"value\":\"Something is wrong with the canary deployment\"}],\"trigger_types\":[\"alert_triggered\"]}],\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#my-team-channel\"}]}},{\"label\":\"Pause the alert and trigger a reboot action if flaky server receives an error\",\"id\":\"c0163dbe\",\"conditions\":[{\"expression\":\"event.custom_details.hostname matches part 'staging'\"}],\"actions\":{\"suspend\":300,\"pagerduty_automation_actions\":[{\"action_id\":\"01CSBCGJXMG7ABIJZKPD8P9RCL\",\"trigger_types\":[\"alert_suspended\"]}]}},{\"label\":\"Never bother the on-call for info-level events outside of work hours\",\"id\":\"cd770384\",\"conditions\":[{\"expression\":\"event.severity matches 'info' and not (now in Mon,Tue,Wed,Thu,Fri 09:00:00 to 17:00:00 America/Los_Angeles)\"}],\"actions\":{\"suppress\":true}}]}],\"catch_all\":{\"actions\":{\"suppress\":true},\"incident_custom_field_updates\":[{\"id\":\"PEXCK89\",\"value\":\"#general-incident-notifications\"}]}}}\n\n@endpoint GET /event_orchestrations/services/{service_id}/active\n@desc Get the Service Orchestration active status for a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID}\n@returns(200) {active: bool} # An object with the active status.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/services/{service_id}/active\n@desc Update the Service Orchestration active status for a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID}\n@returns(200) {active: bool} # An object with the active status.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"active\":false}\n\n@endpoint GET /event_orchestrations/{id}/cache_variables\n@desc List Cache Variables for a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) {cache_variables: [any]} # The Cache Variables for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /event_orchestrations/{id}/cache_variables\n@desc Create a Cache Variable for a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable: any}\n@returns(200) {cache_variable: any} # The created Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n@example_request {\"cache_variable\":{\"name\":\"example_1\",\"conditions\":[{\"expression\":\"not event.custom_details.errors exists\"}],\"configuration\":{\"type\":\"recent_value\",\"source\":\"event.summary\",\"regex\":\".*\"}}}\n\n@endpoint GET /event_orchestrations/{id}/cache_variables/{cache_variable_id}\n@desc Get a Cache Variable for a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable_id: str # The ID of a Cache Variable.}\n@returns(200) {cache_variable: any} # The fetched Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/{id}/cache_variables/{cache_variable_id}\n@desc Update a Cache Variable for a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable_id: str # The ID of a Cache Variable., cache_variable: any}\n@returns(200) {cache_variable: any} # The updated Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n@example_request {\"cache_variable\":{\"name\":\"example_1\",\"conditions\":[{\"expression\":\"event.summary matches 'exception'\"},{\"expression\":\"event.summary matches 'error'\"}]}}\n\n@endpoint DELETE /event_orchestrations/{id}/cache_variables/{cache_variable_id}\n@desc Delete a Cache Variable for a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable_id: str # The ID of a Cache Variable.}\n@returns(204) The Cache Variable was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data\n@desc Get Data for an External Data Cache Variable on a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable_id: str # The ID of a Cache Variable.}\n@returns(200) The data on an `external_data` type Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data\n@desc Update Data for an External Data Cache Variable on a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable_id: str # The ID of a Cache Variable.}\n@returns(200) The data on an `external_data` type Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n@example_request {\"cache_variable_data\":\"Updated - Hello World!\"}\n\n@endpoint DELETE /event_orchestrations/{id}/cache_variables/{cache_variable_id}/data\n@desc Delete Data for an External Data Cache Variable on a Global Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., cache_variable_id: str # The ID of a Cache Variable.}\n@returns(204) The Data was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /event_orchestrations/services/{service_id}/cache_variables\n@desc List Cache Variables for a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID}\n@returns(200) {cache_variables: [any]} # The Cache Variables for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /event_orchestrations/services/{service_id}/cache_variables\n@desc Create a Cache Variable for a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable: any}\n@returns(200) {cache_variable: any} # The created Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n@example_request {\"cache_variable\":{\"name\":\"example_1\",\"conditions\":[{\"expression\":\"not event.custom_details.errors exists\"}],\"configuration\":{\"type\":\"recent_value\",\"source\":\"event.summary\",\"regex\":\".*\"}}}\n\n@endpoint GET /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}\n@desc Get a Cache Variable for a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable_id: str # The ID of a Cache Variable.}\n@returns(200) {cache_variable: any} # The fetched Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}\n@desc Update a Cache Variable for a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable_id: str # The ID of a Cache Variable., cache_variable: any}\n@returns(200) {cache_variable: any} # The updated Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n@example_request {\"cache_variable\":{\"name\":\"example_1\",\"conditions\":[{\"expression\":\"event.summary matches 'exception'\"},{\"expression\":\"event.summary matches 'error'\"}]}}\n\n@endpoint DELETE /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}\n@desc Delete a Cache Variable for a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable_id: str # The ID of a Cache Variable.}\n@returns(204) The Cache Variable was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}/data\n@desc Get Data for an External Data Cache Variable on a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable_id: str # The ID of a Cache Variable.}\n@returns(200) The data on an `external_data` type Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}/data\n@desc Update Data for an External Data Cache Variable on a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable_id: str # The ID of a Cache Variable.}\n@returns(200) The data on an `external_data` type Cache Variable for this Event Orchestration.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.}\n@example_request {\"cache_variable_data\":\"Updated - Hello World!\"}\n\n@endpoint DELETE /event_orchestrations/services/{service_id}/cache_variables/{cache_variable_id}/data\n@desc Delete Data for an External Data Cache Variable on a Service Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service_id: str # The service ID, cache_variable_id: str # The ID of a Cache Variable.}\n@returns(204) The Data was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /event_orchestrations/{id}/enablements\n@desc List Enablements for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration.}\n@returns(200) {enablements: [map]} # The list of feature enablement settings for the Event Orchestation.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /event_orchestrations/{id}/enablements/{feature_name}\n@desc Update an Enablement for an Event Orchestration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of an Event Orchestration., feature_name: str # The feature enablement identifier, typically the name of the product addon. Currently only `aiops` is supported., enablement: map{feature: str, enabled!: bool, updated_at: str(date-time), warnings: [map]}}\n@returns(200) {enablement: map{feature: str, enabled: bool, updated_at: str(date-time), warnings: [map]}} # The feature enablement setting was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"enablement\":{\"enabled\":true}}\n\n@endgroup\n\n@group extension_schemas\n@endpoint GET /extension_schemas\n@desc List extension schemas\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) A paginated array of extension schemas.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /extension_schemas/{id}\n@desc Get an extension vendor\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {extension_schema: map{icon_url: str(url), logo_url: str(url), label: str, key: str, description: str, guide_url: str(url), send_types: [str], url: str}} # The extension vendor requested\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group extensions\n@endpoint GET /extensions\n@desc List extensions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Filters the result, showing only the records whose name matches the query., extension_object_id: str # The id of the extension object you want to filter by., extension_schema_id: str # Filter the extensions by extension vendor id., include[]: str(extension_objects/extension_schemas) # Array of additional details to include.}\n@returns(200) A paginated array of extensions.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint POST /extensions\n@desc Create an extension\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, extension: any}\n@returns(201) {extension: any} # The extension that was created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n@example_request {\"extension\":{\"endpoint_url\":\"https://example.com/receive_a_pagerduty_webhook\",\"name\":\"My Webhook\",\"extension_schema\":{\"id\":\"PJFWPEP\",\"type\":\"extension_schema_reference\"},\"extension_objects\":[{\"id\":\"PIJ90N7\",\"type\":\"service_reference\"}]}}\n\n@endpoint GET /extensions/{id}\n@desc Get an extension\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str(extension_schemas/extension_objects/temporarily_disabled): any # Array of additional details to include.}\n@returns(200) {extension: any} # The extension that was requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint DELETE /extensions/{id}\n@desc Delete an extension\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The extension was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /extensions/{id}\n@desc Update an extension\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., extension: any}\n@returns(200) {extension: any} # The extension that was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"extension\":{\"endpoint_url\":\"https://example.com/receive_a_pagerduty_webhook\",\"name\":\"My Webhook\",\"extension_schema\":{\"id\":\"PJFWPEP\",\"type\":\"extension_schema_reference\"},\"extension_objects\":[{\"id\":\"PIJ90N7\",\"type\":\"service_reference\"}]}}\n\n@endpoint POST /extensions/{id}/enable\n@desc Enable an extension\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {extension: any} # The extension that was successfully enabled.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endgroup\n\n@group incident_workflows\n@endpoint GET /incident_workflows\n@desc List Incident Workflows\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Filters the result, showing only the records whose name matches the query., include[]: str(steps/team) # Array of additional details to include.}\n@returns(200) A paginated array of Incident Workflows.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /incident_workflows\n@desc Create an Incident Workflow\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, incident_workflow: any}\n@returns(201) {incident_workflow: any} # The new Incident Workflow\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"incident_workflow\":{\"name\":\"Example Incident Workflow\",\"description\":\"This Incident Workflow is an example\",\"steps\":[{\"name\":\"Send Status Update\",\"action_configuration\":{\"action_id\":\"pagerduty.com:incident-workflows:send-status-update:1\",\"inputs\":[{\"name\":\"Message\",\"value\":\"Example status message sent on {{current_date}}\"}]}}]}}\n\n@endpoint GET /incident_workflows/{id}\n@desc Get an Incident Workflow\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(201) {incident_workflow: any} # The Incident Workflow\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /incident_workflows/{id}\n@desc Delete an Incident Workflow\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) The Incident Workflow was deleted successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incident_workflows/{id}\n@desc Update an Incident Workflow\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., incident_workflow: any}\n@returns(200) {incident_workflow: any} # The changed Incident Workflow\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"incident_workflow\":{\"name\":\"Example Incident Workflow\",\"description\":\"This Incident Workflow is an example\",\"steps\":[{\"name\":\"Send Status Update\",\"action_configuration\":{\"action_id\":\"pagerduty.com:incident-workflows:send-status-update:1\",\"inputs\":[{\"name\":\"Message\",\"value\":\"Example status message sent on {{current_date}}\"}]}}]}}\n\n@endpoint POST /incident_workflows/{id}/instances\n@desc Start an Incident Workflow Instance\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., incident_workflow_instance: map{id: str, incident: map}}\n@returns(201) {incident_workflow_instance: map{id: str, type: str, incident: any}} # The Incident Workflow Instance\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"incident_workflow_instance\":{\"id\":\"P3SNKQS\",\"type\":\"incident_workflow_instance\",\"incident\":{\"id\":\"Q1R2DLCB21K7NP\",\"type\":\"incident_reference\"}}}\n\n@endpoint GET /incident_workflows/actions\n@desc List Actions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., keyword: str # If provided, only show actions tagged with the specified keyword}\n@returns(200) A paginated array of Incident Workflow Actions\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /incident_workflows/actions/{id}\n@desc Get an Action\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {action: any} # An Incident Workflow Action\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /incident_workflows/triggers\n@desc List Triggers\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {workflow_id: str # If provided, only show triggers configured to start the given workflow. Useful for listing all services associated with the given workflow, incident_id: str # If provided, only show triggers configured on the service of the given incident. Useful for finding manual triggers that are configured on the service for a specific incident. Cannot be specified if `service_id` is provided., service_id: str # If provided, only show triggers configured for incidents in the given service. Useful for listing all workflows associated with the given service. Cannot be specified if `incident_id` is provided., trigger_type: str(manual/conditional/incident_type) # If provided, only show triggers of the given type. For example “manual” to search for manual triggers, workflow_name_contains: str # If provided, only show triggers configured to start workflows whose name contain the provided value., is_disabled: bool # If provided, filters between disabled and enabled Triggers. This query parameter is deprecated, and will be removed in a future version of this API., sort_by: str(workflow_id/workflow_id asc/workflow_id desc/workflow_name/workflow_name asc/workflow_name desc) # If provided, returns triggers sorted by the specified property., limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set.}\n@returns(200) A paginated array of Incident Workflow Triggers\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /incident_workflows/triggers\n@desc Create a Trigger\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, trigger: any}\n@returns(201) {trigger: any} # The newly created Incident Workflow Trigger\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"trigger\":{\"trigger_type\":\"conditional\",\"workflow\":{\"id\":\"PSFEVL7\"},\"services\":[{\"id\":\"PIJ90N7\"}],\"is_subscribed_to_all_services\":false,\"condition\":\"incident.priority matches 'P1'\"}}\n\n@endpoint GET /incident_workflows/triggers/{id}\n@desc Get a Trigger\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {trigger: any} # The Incident Workflows Trigger\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incident_workflows/triggers/{id}\n@desc Update a Trigger\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., trigger: any}\n@returns(200) {trigger: any} # The updated Incident Workflow Trigger\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"trigger\":{\"services\":[{\"id\":\"PIJ90N7\"}],\"is_subscribed_to_all_services\":false,\"condition\":\"incident.priority matches 'P1'\"}}\n\n@endpoint DELETE /incident_workflows/triggers/{id}\n@desc Delete a Trigger\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The Incident Workflow Trigger was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /incident_workflows/triggers/{id}/services\n@desc Associate a Trigger and Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., service: map{id: str}}\n@returns(201) {trigger: any} # The updated Incident Workflow Trigger\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"service\":{\"id\":\"PIJ90N7\"}}\n\n@endpoint DELETE /incident_workflows/triggers/{trigger_id}/services/{service_id}\n@desc Dissociate a Trigger and Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, trigger_id: str # Identifier for the Trigger, service_id: str # Identifier for the Service}\n@returns(201) {trigger: any} # The updated Incident Workflow Trigger\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group incidents\n@endpoint GET /incidents\n@desc List incidents\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page. Maximum of 100., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., date_range: str # When set to all, the since and until parameters and defaults are ignored., incident_key: str # Incident de-duplication key. Incidents with child alerts do not have an incident key; querying by incident key will return incidents whose alerts have alert_key matching the given incident key., service_ids[]: [str] # Returns only the incidents associated with the passed service(s). This expects one or more service IDs., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., user_ids[]: [str] # Returns only the incidents currently assigned to the passed user(s). This expects one or more user IDs. Note: When using the assigned_to_user filter, you will only receive incidents with statuses of triggered or acknowledged. This is because resolved incidents are not assigned to any user., urgencies[]: str(high/low) # Array of the urgencies of the incidents to be returned. Defaults to all urgencies. Account must have the `urgencies` ability to do this., time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., statuses[]: str(triggered/acknowledged/resolved) # Return only incidents with the given statuses. To query multiple statuses, pass `statuses[]` more than once, for example: `https://api.pagerduty.com/incidents?statuses[]=triggered&statuses[]=acknowledged`. (More status codes may be introduced in the future.), sort_by: [str] # Used to specify both the field you wish to sort the results on (incident_number/created_at/resolved_at/urgency), as well as the direction (asc/desc) of the results. The sort_by field and direction should be separated by a colon. A maximum of two fields can be included, separated by a comma. Sort direction defaults to ascending. The account must have the `urgencies` ability to sort by the urgency., include[]: str(acknowledgers/agents/assignees/conference_bridge/escalation_policies/first_trigger_log_entries/priorities/services/teams/users) # Array of additional details to include., since: str # The start of the date range over which you want to search. Maximum range is 6 months and default is 1 month., until: str # The end of the date range over which you want to search. Maximum range is 6 months and default is 1 month.}\n@returns(200) A paginated array of incidents.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incidents\n@desc Manage incidents\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, From: str(email) # The email address of a valid user associated with the account making the request., incidents: [any] # An array of incidents, including the parameters to update.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) All of the updates succeeded.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 413: Caller provided a request that is too large to process., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"incidents\":[{\"id\":\"PT4KHLK\",\"type\":\"incident_reference\",\"status\":\"acknowledged\"},{\"id\":\"PQMF62U\",\"type\":\"incident_reference\",\"priority\":{\"id\":\"P53ZZH5\",\"type\":\"priority_reference\"}},{\"id\":\"PPVZH9X\",\"type\":\"incident_reference\",\"status\":\"resolved\"},{\"id\":\"P8JOGX7\",\"type\":\"incident_reference\",\"assignments\":[{\"assignee\":{\"id\":\"PXPGF42\",\"type\":\"user_reference\"}}]},{\"id\":\"PYJ9K7I\",\"type\":\"incident_reference\",\"incident_type\":{\"name\":\"major_incident\"}}]}\n\n@endpoint POST /incidents\n@desc Create an Incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, From: str(email) # The email address of a valid user associated with the account making the request., incident: map{type!: str, title!: str, service!: any, priority: any, urgency: str, body: map, incident_key: str, assignments: [any], incident_type: map, escalation_policy: any, conference_bridge: map} # Details of the incident to be created.}\n@returns(201) {incident: any} # The incident object created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"incident\":{\"type\":\"incident\",\"title\":\"The server is on fire.\",\"service\":{\"id\":\"PWIXJZS\",\"type\":\"service_reference\"},\"priority\":{\"id\":\"P53ZZH5\",\"type\":\"priority_reference\"},\"urgency\":\"high\",\"incident_key\":\"baf7cf21b1da41b4b0221008339ff357\",\"body\":{\"type\":\"incident_body\",\"details\":\"A disk is getting full on this machine. You should investigate what is causing the disk to fill, and ensure that there is an automated process in place for ensuring data is rotated (eg. logs should have logrotate around them). If data is expected to stay on this disk forever, you should start planning to scale up to a larger disk.\"},\"incident_type\":{\"name\":\"major_incident\"},\"escalation_policy\":{\"id\":\"PT20YPA\",\"type\":\"escalation_policy_reference\"}}}\n\n@endpoint GET /incidents/{id}\n@desc Get an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str(acknowledgers/agents/assignees/conference_bridge/custom_fields/escalation_policies/first_trigger_log_entries/priorities/services/teams/users): any # Array of additional details to include.}\n@returns(200) {incident: any} # The incident requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incidents/{id}\n@desc Update an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., incident: map{type!: str, status: str, priority: any, resolution: str, title: str, escalation_level: int, assignments: [any], incident_type: map, escalation_policy: any, urgency: str, conference_bridge: map, service: map} # The parameters of the incident to update.}\n@returns(200) The incident was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"incident\":{\"type\":\"incident_reference\",\"status\":\"acknowledged\"}}\n\n@endpoint GET /incidents/{id}/alerts\n@desc List alerts for an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., alert_key: str # Alert de-duplication key., statuses[]: str(triggered/resolved) # Return only alerts with the given statuses. (More status codes may be introduced in the future.), sort_by: str(created_at/resolved_at/created_at:asc/created_at:desc/resolved_at:asc/resolved_at:desc) # Used to specify both the field you wish to sort the results on (created_at/resolved_at), as well as the direction (asc/desc) of the results. The sort_by field and direction should be separated by a colon. A maximum of two fields can be included, separated by a comma. Sort direction defaults to ascending., include[]: str(services/first_trigger_log_entries/incidents) # Array of additional details to include.}\n@returns(200) A paginated array of the incident's alerts.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incidents/{id}/alerts\n@desc Manage alerts\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., alerts: [map{status: str, incident: map}] # An array of alerts, including the parameters to update for each alert.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) All of the updates succeeded.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 413: Caller provided a request that is too large to process., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"alerts\":[{\"id\":\"PPVZH9X\",\"type\":\"alert\",\"status\":\"resolved\"},{\"id\":\"P8JOGX7\",\"type\":\"alert\",\"incident\":{\"id\":\"PPVZH9X\",\"type\":\"incident_reference\"}}]}\n\n@endpoint GET /incidents/{id}/alerts/{alert_id}\n@desc Get an alert\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., alert_id: str # The id of the alert to retrieve.}\n@returns(200) {alert: any} # The alert requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incidents/{id}/alerts/{alert_id}\n@desc Update an alert\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., alert_id: str # The id of the alert to retrieve., From: str(email) # The email address of a valid user associated with the account making the request., alert: map{status: str, incident: map}}\n@returns(200) {alert: any} # The alert that was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"alert\":{\"type\":\"alert\",\"status\":\"resolved\",\"incident\":{\"id\":\"PEYSGVF\",\"type\":\"incident_reference\"}}}\n\n@endpoint PUT /incidents/{id}/business_services/{business_service_id}/impacts\n@desc Manually change an Incident's Impact on a Business Service.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., business_service_id: str # The business service ID., relation: str(impacted/not_impacted)}\n@returns(200) {relation: str} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /incidents/{id}/business_services/impacts\n@desc List Business Services impacted by the given Incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /incidents/{id}/custom_fields/values\n@desc Get Custom Field Values\n@required {id: str # The ID of the resource.}\n@returns(200) {custom_fields: [map]} # The list of custom field values.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /incidents/{id}/custom_fields/values\n@desc Update Custom Field Values\n@required {id: str # The ID of the resource., custom_fields: [any]}\n@returns(201) {custom_fields: [map]} # Custom field values were updated.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"custom_fields\":[{\"name\":\"environment\",\"value\":\"production\"}]}\n\n@endpoint GET /incidents/{id}/log_entries\n@desc List log entries for an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search., is_overview: bool=false # If `true`, will return a subset of log entries that show only the most important changes to the incident., include[]: str(incidents/services/channels/teams) # Array of additional Models to include in response.}\n@returns(200) A paginated array of the incident's log entries.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /incidents/{id}/merge\n@desc Merge incidents\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., source_incidents: [any] # The source incidents that will be merged into the target incident and resolved.}\n@returns(200) {incident: any} # The target incident, which now contains all the alerts from the source incident.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"source_incidents\":[{\"id\":\"P8JOGX7\",\"type\":\"incident_reference\"},{\"id\":\"PPVZH9X\",\"type\":\"incident_reference\"}]}\n\n@endpoint GET /incidents/{id}/notes\n@desc List notes for an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {notes: [map]} # An array of notes.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /incidents/{id}/notes\n@desc Create a note on an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., note: map{content!: str}}\n@returns(200) {note: map{id: str, user: any, channel: map{summary: str, id: str, type: str, self: str(url), html_url: str(url)}, content: str, created_at: str(date-time), updated_at: str(date-time)}} # The new note.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"note\":{\"content\":\"Firefighters are on the scene.\"}}\n\n@endpoint PUT /incidents/{id}/notes/{note_id}\n@desc Update a note on an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., note_id: str # The id of the note., From: str(email) # The email address of a valid user associated with the account making the request., note: map{content!: str}}\n@returns(200) {note: map{id: str, user: any, channel: map{summary: str, id: str, type: str, self: str(url), html_url: str(url)}, content: str, created_at: str(date-time), updated_at: str(date-time)}} # The updated note.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"note\":{\"content\":\"Firefighters are on the scene. Update 1.\"}}\n\n@endpoint DELETE /incidents/{id}/notes/{note_id}\n@desc Delete a note on an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., note_id: str # The id of the note.}\n@returns(204) Note deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /incidents/{id}/outlier_incident\n@desc Get Outlier Incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {since: str(date-time) # The start of the date range over which you want to search., additional_details[]: str # Array of additional attributes to any of the returned incidents for related incidents.}\n@returns(200) {outlier_incident: map{incident: any, incident_template: map{id: str, cluster_id: str, mined_text: str}}} # Outlier Incident information calculated over the same Service as the given Incident.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /incidents/{id}/past_incidents\n@desc Get Past Incidents\n@optional {limit: int=5 # The number of results to be returned in the response., total: bool=false # By default the `total` field in the response body is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated with the total number of Past Incidents.}\n@returns(200) {past_incidents: [map], total: num, limit: num} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /incidents/{id}/related_change_events\n@desc List related Change Events for an Incident\n@required {id: str # The ID of the resource., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page.}\n@returns(200) {change_events: [any]} # The array of Change Events returned by the query.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /incidents/{id}/related_incidents\n@desc Get Related Incidents\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {additional_details[]: str: any # Array of additional attributes to any of the returned incidents for related incidents.}\n@returns(200) {related_incidents: [any]} # A list of Related Incidents and their relationships.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /incidents/{id}/responder_requests\n@desc Create a responder request for an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., requester_id: str # The user id of the requester., message: str # The message sent with the responder request., responder_request_targets: any # The array of targets the responder request is sent to.}\n@returns(200) {responder_request: map{id: str, incident: any, requester: any, requested_at: str, message: str, responder_request_targets: [map]}} # The new responder request for the given incident.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"requester_id\":\"PL1JMK5\",\"message\":\"Please help with issue - join bridge at +1(234)-567-8910\",\"responder_request_targets\":[{\"responder_request_target\":{\"id\":\"PJ25ZYX\",\"type\":\"user_reference\"}}]}\n\n@endpoint PUT /incidents/{id}/responder_requests/cancel\n@desc Cancel responder requests for an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., requester_id: str # The user id of the requester., responder_request_targets: [map{type!: str, id!: str}] # The array of targets to cancel.}\n@returns(200) {responder_request_targets: [map]} # The result of cancelling responder requests for the given incident.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"requester_id\":\"PL1JMK5\",\"responder_request_targets\":[{\"type\":\"user_reference\",\"id\":\"PJ25ZYX\"},{\"type\":\"escalation_policy_reference\",\"id\":\"PEP12AB\"}]}\n\n@endpoint POST /incidents/{id}/snooze\n@desc Snooze an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., duration: int # The number of seconds to snooze the incident for. After this number of seconds has elapsed, the incident will return to the \"triggered\" state.}\n@returns(201) {incident: any} # The incident that was successfully snoozed.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"duration\":3600}\n\n@endpoint POST /incidents/{id}/status_updates\n@desc Create a status update on an incident\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., message: str # The message to be posted as a status update.}\n@optional {subject: str # The subject to be sent for the custom html email status update. Required if sending custom html email., html_message: str # The html content to be sent for the custom html email status update. Required if sending custom html email.}\n@returns(200) {status_update: map{id: str, message: str, created_at: str, sender: any, subject: str, html_message: str}} # The new status update for the specified incident.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"message\":\"The server fire is spreading.\",\"subject\":\"Server Fire Update\",\"html_message\":\"<h1>Server is still on fire</h1>\"}\n\n@endpoint GET /incidents/{id}/status_updates/subscribers\n@desc List Notification Subscribers\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /incidents/{id}/status_updates/subscribers\n@desc Add Notification Subscribers\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribers: [map{subscriber_id: str, subscriber_type: str}]}\n@returns(200) {subscriptions: [map]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribers\":[{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"team\"},{\"subscriber_id\":\"PD1235\",\"subscriber_type\":\"team\"},{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"user\"}]}\n\n@endpoint POST /incidents/{id}/status_updates/unsubscribe\n@desc Remove Notification Subscriber\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribers: [map{subscriber_id: str, subscriber_type: str}]}\n@returns(200) {deleted_count: num, unauthorized_count: num, non_existent_count: num} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribers\":[{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"team\"},{\"subscriber_id\":\"PD1234\",\"subscriber_type\":\"user\"}]}\n\n@endpoint GET /incidents/types\n@desc List incident types\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {filter: str(enabled/disabled/all)=enabled # Filters the list of incident types based on their `enabled` state.}\n@returns(200) An array of all types for the account. The default incident type will automatically return on this list.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /incidents/types\n@desc Create an Incident Type\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, incident_type: map{name!: str, display_name!: str, parent_type!: str, enabled: bool, description: str} # Details of the incident type to be created.}\n@returns(201) {incident_type: map{enabled: bool, id: str, name: str, parent: map{id: str, type: str}, type: str, description: str, created_at: str(date-time), updated_at: str(date-time), display_name: str}} # The incident type object created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"incident_type\":{\"name\":\"fraud_incident\",\"display_name\":\"Fraud Incident\",\"parent_type\":\"incident_default\"}}\n\n@endpoint GET /incidents/types/{type_id_or_name}\n@desc Get an Incident Type\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type.}\n@returns(200) {incident_type: map{enabled: bool, id: str, name: str, parent: map{id: str, type: str}, type: str, description: str, created_at: str(date-time), updated_at: str(date-time), display_name: str}} # The incident type requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /incidents/types/{type_id_or_name}\n@desc Update an Incident Type\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., incident_type: map{display_name: str, enabled: bool, description: str} # Details of the incident type to be created.}\n@returns(200) {incident_type: map{enabled: bool, id: str, name: str, parent: map{id: str, type: str}, type: str, description: str, created_at: str(date-time), updated_at: str(date-time), display_name: str}} # The incident type object updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"incident_type\":{\"display_name\":\"Major Incident\"}}\n\n@endpoint GET /incidents/types/{type_id_or_name}/custom_fields\n@desc List Incident Type Custom Fields\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type.}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {fields: [map]} # The custom fields for the incident type requested. Passing in include[]=field_options will return the field options for the custom field.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /incidents/types/{type_id_or_name}/custom_fields\n@desc Create a Custom Field for an Incident Type\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field: map{name!: str, display_name!: str, data_type!: str, field_type!: str, description: str, enabled: bool, default_value: str, field_options: [any]} # Details of the custom field to be created.}\n@returns(201) {field: map{enabled: bool, id: str, name: str, type: str, self: str(url)?, description: str?, field_type: str, data_type: str, updated_at: str(date-time), created_at: str(date-time), display_name: str, default_value: any?, incident_type: str, summary: str?, field_options: [map]}} # The custom field object created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field\":{\"name\":\"custom_field_1\",\"display_name\":\"Custom Field 1\",\"data_type\":\"string\",\"field_type\":\"single_value\"}}\n\n@endpoint GET /incidents/types/{type_id_or_name}/custom_fields/{field_id}\n@desc Get an Incident Type Custom Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_id: str # The ID of the field.}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {field: map{enabled: bool, id: str, name: str, type: str, self: str(url)?, description: str?, field_type: str, data_type: str, updated_at: str(date-time), created_at: str(date-time), display_name: str, default_value: any?, incident_type: str, summary: str?, field_options: [map]}} # The incident type custom field requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /incidents/types/{type_id_or_name}/custom_fields/{field_id}\n@desc Update a Custom Field for an Incident Type\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_id: str # The ID of the field., field: map{display_name: str, enabled: bool, default_value: str, description: str, field_options: [any]} # Details of the custom field to be updated.}\n@returns(200) {field: map{enabled: bool, id: str, name: str, type: str, self: str(url)?, description: str?, field_type: str, data_type: str, updated_at: str(date-time), created_at: str(date-time), display_name: str, default_value: any?, incident_type: str, summary: str?, field_options: [map]}} # The updated custom field object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field\":{\"display_name\":\"Custom Field 1\"}}\n\n@endpoint DELETE /incidents/types/{type_id_or_name}/custom_fields/{field_id}\n@desc Delete a Custom Field for an Incident Type\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_id: str # The ID of the field.}\n@returns(204) The field was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options\n@desc List Field Options on a Custom Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_id: str # The ID of the field.}\n@returns(200) {field_options: [any]} # The field option for the custom field requested.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options\n@desc Create a Field Option for a Custom Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_id: str # The ID of the field., field_option: map{data!: map} # Details of the field option to be created.}\n@returns(201) {field_option: map{data: any, id: str, type: str, updated_at: str(date-time), created_at: str(date-time)}} # The field option for the custom field created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field_option\":{\"data\":{\"data_type\":\"string\",\"value\":\"option_1\"}}}\n\n@endpoint GET /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Get a Field Option on a Custom Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_option_id: str # The ID of the field option., field_id: str # The ID of the field.}\n@returns(200) {field_option: map{data: any, id: str, type: str, updated_at: str(date-time), created_at: str(date-time)}} # The field option of the custom field requested.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Update a Field Option for a Custom Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_option_id: str # The ID of the field option., field_id: str # The ID of the field., field_option: map{data!: map} # Details of the field option on a custom field to be updated.}\n@returns(200) {field_option: map{data: any, id: str, type: str, updated_at: str(date-time), created_at: str(date-time)}} # The field option for the custom field updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field_option\":{\"data\":{\"data_type\":\"string\",\"value\":\"option_1\"}}}\n\n@endpoint DELETE /incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Delete a Field Option for a Custom Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type_id_or_name: str # The ID or name of the Incident Type., field_option_id: str # The ID of the field option., field_id: str # The ID of the field.}\n@returns(204) The field option was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /incidents/custom_fields\n@desc Create a Field\n@required {field: any}\n@returns(201) {field: any} # The field object created, along with the Field Options if provided.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field\":{\"data_type\":\"string\",\"name\":\"environment\",\"display_name\":\"Environment\",\"description\":\"The environment that the issue occurred in\",\"field_type\":\"single_value_fixed\",\"default_value\":\"production\",\"field_options\":[{\"data\":{\"data_type\":\"string\",\"value\":\"production\"}},{\"data\":{\"data_type\":\"string\",\"value\":\"staging\"}}]}}\n\n@endpoint GET /incidents/custom_fields\n@desc List Fields\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) A list of fields.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /incidents/custom_fields/{field_id}\n@desc Get a Field\n@required {field_id: str # The ID of the field.}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {field: any} # The field requested.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /incidents/custom_fields/{field_id}\n@desc Update a Field\n@required {field_id: str # The ID of the field., field: map{display_name: str, description: str, default_value: any, enabled: bool}}\n@returns(200) {field: any} # The field object updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field\":{\"display_name\":\"New Display Name!\",\"description\":\"New description!\"}}\n\n@endpoint DELETE /incidents/custom_fields/{field_id}\n@desc Delete a Field\n@required {field_id: str # The ID of the field.}\n@returns(204) The field was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /incidents/custom_fields/{field_id}/field_options\n@desc Create a Field Option\n@required {field_id: str # The ID of the field., field_option: any}\n@returns(201) {field_option: any} # The field option created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field_option\":{\"data\":{\"data_type\":\"string\",\"value\":\"production\"}}}\n\n@endpoint GET /incidents/custom_fields/{field_id}/field_options\n@desc List Field Options\n@required {field_id: str # The ID of the field.}\n@returns(200) {field_options: [any]} # A list of field options.\n@errors {404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /incidents/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Update a Field Option\n@required {field_id: str # The ID of the field., field_option_id: str # The ID of the field option., field_option: map{data: any, id!: str, type!: str, updated_at!: str(date-time), created_at!: str(date-time)}}\n@returns(200) {field_option: any} # The field option object updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field_option\":{\"data\":{\"data_type\":\"string\",\"value\":\"prod\"}}}\n\n@endpoint DELETE /incidents/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Delete a Field Option\n@required {field_id: str # The ID of the field., field_option_id: str # The ID of the field option.}\n@returns(204) The field option was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group license_allocations\n@endpoint GET /license_allocations\n@desc List License Allocations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results.}\n@returns(200) License allocations to Users within your Account\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endgroup\n\n@group licenses\n@endpoint GET /licenses\n@desc List Licenses\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {licenses: [any]} # Licenses associated with your Account\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endgroup\n\n@group log_entries\n@endpoint GET /log_entries\n@desc List log entries\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search., is_overview: bool=false # If `true`, will return a subset of log entries that show only the most important changes to the incident., include[]: str(incidents/services/channels/teams) # Array of additional Models to include in response., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter.}\n@returns(200) A paginated array of log entries.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /log_entries/{id}\n@desc Get a log entry\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., include[]: str(incidents/services/channels/teams) # Array of additional Models to include in response.}\n@returns(200) {log_entry: any} # A single log entry.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /log_entries/{id}/channel\n@desc Update log entry channel information.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., From: str(email) # The email address of a valid user associated with the account making the request., channel: map{details!: str, type!: str} # The parameters to update.}\n@returns(202) The channel information modification was accepted.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"channel\":{\"type\":\"web_trigger\",\"details\":\"New channel details\"}}\n\n@endgroup\n\n@group maintenance_windows\n@endpoint GET /maintenance_windows\n@desc List maintenance windows\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {query: str # Filters the result, showing only the records whose name matches the query., limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., service_ids[]: [str] # An array of service IDs. Only results related to these services will be returned., include[]: str(teams/services/users) # Array of additional Models to include in response., filter: str(past/future/ongoing/open/all) # Only return maintenance windows in a given state.}\n@returns(200) A paginated array of maintenance windows.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /maintenance_windows\n@desc Create a maintenance window\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, From: str(email) # The email address of a valid user associated with the account making the request., maintenance_window: any}\n@returns(201) {maintenance_window: any} # The maintenance window that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"maintenance_window\":{\"type\":\"maintenance_window\",\"start_time\":\"2015-11-09T20:00:00-05:00\",\"end_time\":\"2015-11-09T22:00:00-05:00\",\"description\":\"Immanentizing the eschaton\",\"services\":[{\"id\":\"PIJ90N7\",\"type\":\"service_reference\"}]}}\n\n@endpoint GET /maintenance_windows/{id}\n@desc Get a maintenance window\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str(teams/services/users): any # Array of additional Models to include in response.}\n@returns(200) {maintenance_window: any} # The maintenance window that was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /maintenance_windows/{id}\n@desc Delete or end a maintenance window\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The maintenance window was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The maintenance window can't be deleted because it has already ended., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /maintenance_windows/{id}\n@desc Update a maintenance window\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., maintenance_window: any}\n@returns(200) {maintenance_window: any} # The maintenance window that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"maintenance_window\":{\"type\":\"maintenance_window\",\"start_time\":\"2015-11-09T20:00:00-05:00\",\"end_time\":\"2015-11-09T22:00:00-05:00\",\"description\":\"Immanentizing the eschaton\",\"services\":[{\"id\":\"PIJ90N7\",\"type\":\"service_reference\"}]}}\n\n@endgroup\n\n@group notifications\n@endpoint GET /notifications\n@desc List notifications\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, since: str(date-time) # The start of the date range over which you want to search. The time element is optional., until: str(date-time) # The end of the date range over which you want to search. This should be in the same format as since. The size of the date range must be less than 3 months.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., filter: str(sms_notification/email_notification/phone_notification/push_notification) # Return notification of this type only., include[]: str # Array of additional details to include.}\n@returns(200) A paginated array of notifications.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group oauth_delegations\n@endpoint DELETE /oauth_delegations\n@desc Delete all OAuth delegations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, user_id: str # The ID of the user for whom this request is applicable., type: str(mobile/web) # The type of OAuth delegations this request should target. Allowed values are 'mobile' (to sign users out of the mobile app) and 'web' (to sign users out of the web app). You can pass one or more types in, separated by commas (e.g., `type=web,mobile`).}\n@returns(200) {status: str} # The request to delete delegations has been processed.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /oauth_delegations/revocation_requests/status\n@desc Get OAuth delegations revocation requests status\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {requested_at_end: str(date-time) # The end of the date range over which you want to search. If not specified, this will default to current time.}\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group oncalls\n@endpoint GET /oncalls\n@desc List all of the on-calls\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., include[]: str(escalation_policies/users/schedules) # Array of additional details to include., user_ids[]: [str] # Filters the results, showing only on-calls for the specified user IDs., escalation_policy_ids[]: [str] # Filters the results, showing only on-calls for the specified escalation policy IDs., schedule_ids[]: [str] # Filters the results, showing only on-calls for the specified schedule IDs. If `null` is provided in the array, it includes permanent on-calls due to direct user escalation targets., since: str(date-time) # The start of the time range over which you want to search. If an on-call period overlaps with the range, it will be included in the result. Defaults to current time. On-call shifts are limited to 90 days in the future., until: str(date-time) # The end of the time range over which you want to search. If an on-call period overlaps with the range, it will be included in the result. Defaults to current time. On-call shifts are limited to 90 days in the future, and the `until` time cannot be before the `since` time., earliest: bool # This will filter on-calls such that only the earliest on-call for each combination of escalation policy, escalation level, and user is returned. This is useful for determining when the \"next\" on-calls are for a given set of filters.}\n@returns(200) A paginated array of on-call objects.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group paused_incident_reports\n@endpoint GET /paused_incident_reports/alerts\n@desc Get Paused Incident Reporting on Alerts\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search., service_id: str # Specifies a filter to limit the scope of reporting to a particular service, suspended_by: any(auto_pause/rules) # Specifies a filter to scope the response to either alerts suspended by Auto Pause or Event Rules.}\n@returns(200) {paused_incident_reporting_alerts: map{since: str, until: str, triggered_after_pause_alerts: [any], resolved_after_pause_alerts: [any]}} # Paused Incident Reporting on Alerts for the Account or scoped to a Service.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /paused_incident_reports/counts\n@desc Get Paused Incident Reporting counts\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search., service_id: str # Specifies a filter to limit the scope of reporting to a particular service, suspended_by: any(auto_pause/rules) # Specifies a filter to scope the response to either alerts suspended by Auto Pause or Event Rules.}\n@returns(200) {paused_incident_reporting_counts: map{since: str, until: str, paused_count: num, triggered_after_pause_count: num, resolved_after_pause_count: num}} # Paused Incident Reporting counts for the Account or scoped to a Service.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group priorities\n@endpoint GET /priorities\n@desc List priorities\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) A paginated array of priorities.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group rulesets\n@endpoint GET /rulesets\n@desc List Rulesets\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) A paginated array of Ruleset objects.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /rulesets\n@desc Create a Ruleset\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, ruleset: any}\n@returns(201) {ruleset: map{id: str, self: str(url), type: str, name: str, routing_keys: [str], created_at: str(date-time), creator: map{id: str, type: str, self: str(url)}, updated_at: str(date-time), updater: map{id: str, type: str, self: str(url)}, team: map{id: str, type: str, self: str(url)}}} # The Ruleset that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"ruleset\":{\"name\":\"MySQL Clusters\",\"team\":{\"id\":\"PWL7QXS\",\"type\":\"team_reference\"}}}\n\n@endpoint GET /rulesets/{id}\n@desc Get a Ruleset\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {ruleset: map{id: str, self: str(url), type: str, name: str, routing_keys: [str], created_at: str(date-time), creator: map{id: str, type: str, self: str(url)}, updated_at: str(date-time), updater: map{id: str, type: str, self: str(url)}, team: map{id: str, type: str, self: str(url)}}} # The Ruleset object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /rulesets/{id}\n@desc Update a Ruleset\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., ruleset: map{id: str, self: str(url), type: str, name: str, routing_keys: [str], created_at: str(date-time), creator: map, updated_at: str(date-time), updater: map, team: map}}\n@returns(200) {ruleset: map{id: str, self: str(url), type: str, name: str, routing_keys: [str], created_at: str(date-time), creator: map{id: str, type: str, self: str(url)}, updated_at: str(date-time), updater: map{id: str, type: str, self: str(url)}, team: map{id: str, type: str, self: str(url)}}} # The Ruleset that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"ruleset\":{\"name\":\"MySQL Clusters\"}}\n\n@endpoint DELETE /rulesets/{id}\n@desc Delete a Ruleset\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The Ruleset was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n\n@endpoint GET /rulesets/{id}/rules\n@desc List Event Rules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) A paginated array of Event Rule objects.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /rulesets/{id}/rules\n@desc Create an Event Rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule: any}\n@returns(201) {rule: any} # The Event Rule that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 409: The request conflicts with the current state of the server.}\n@example_request {\"rule\":{\"id\":\"14e56445-ebab-4dd0-ba9d-fc28a41b7e7b\",\"position\":0,\"disabled\":false,\"catch_all\":false,\"conditions\":{\"operator\":\"and\",\"subconditions\":[{\"operator\":\"contains\",\"parameters\":{\"value\":\"mysql\",\"path\":\"details.host\"}}]},\"time_frame\":{\"active_between\":{\"start_time\":1577880000000,\"end_time\":1580558400000}},\"actions\":{\"annotate\":{\"value\":\"This incident was created by a Global Event Rule\"},\"route\":{\"value\":\"PI2KBWI\"},\"priority\":{\"value\":\"PCMUB6F\"},\"severity\":{\"value\":\"warning\"},\"extractions\":[{\"target\":\"dedup_key\",\"source\":\"details.error_summary\",\"regex\":\"Host (.*) is experiencing errors\"}]}}}\n\n@endpoint GET /rulesets/{id}/rules/{rule_id}\n@desc Get an Event Rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule_id: str # The id of the Event Rule to retrieve.}\n@returns(200) {rule: any} # The Event Rule object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /rulesets/{id}/rules/{rule_id}\n@desc Update an Event Rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule_id: str # The id of the Event Rule to retrieve., rule_id: str # The id of the Event Rule to update.}\n@optional {rule: any}\n@returns(200) {rule: any} # The Event Rule that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"rule_id\":\"7123bdd1-74e8-4aa7-aa38-4a9ebe123456\",\"rule\":{\"actions\":{\"suppress\":{\"value\":true}}}}\n\n@endpoint DELETE /rulesets/{id}/rules/{rule_id}\n@desc Delete an Event Rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule_id: str # The id of the Event Rule to retrieve.}\n@returns(204) The Event Rule was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n\n@endgroup\n\n@group schedules\n@endpoint GET /schedules\n@desc List schedules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Filters the result, showing only the records whose name matches the query., include[]: str(schedule_layers/overrides_subschedule/final_schedule) # Array of additional details to include., time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the current user's time zone and then the account's time zone., include_next_oncall_for_user: str # Specify an `user_id`, and the schedule list API will return information about this user's next on-call., since: str(date-time) # The start of the date range over which you want to show schedule entries. Defaults to 2 weeks before until if an until is given. Optional parameter. When provided with include[] for schedule types, populates the rendered_schedule_entries fields in the response., until: str(date-time) # The end of the date range over which you want to show schedule entries. Defaults to 2 weeks after since if a since is given. Optional parameter. When provided with include[] for schedule types, populates the rendered_schedule_entries fields in the response.}\n@returns(200) A paginated array of schedule objects.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /schedules\n@desc Create a schedule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, schedule: any}\n@optional {overflow: bool=false # Any on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter `overflow=true` is passed. This parameter defaults to false. For instance, if your schedule is a rotation that changes daily at midnight UTC, and your date range is from `2011-06-01T10:00:00Z` to `2011-06-01T14:00:00Z`:   - If you don't pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T10:00:00Z` and end of `2011-06-01T14:00:00Z`. - If you do pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T00:00:00Z` and end of `2011-06-02T00:00:00Z`.}\n@returns(201) {schedule: any} # The schedule object created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"schedule\":{\"name\":\"Daily Engineering Rotation\",\"type\":\"schedule\",\"time_zone\":\"America/New_York\",\"description\":\"Rotation schedule for engineering\",\"schedule_layers\":[{\"name\":\"Night Shift\",\"start\":\"2015-11-06T20:00:00-05:00\",\"rotation_virtual_start\":\"2015-11-06T20:00:00-05:00\",\"rotation_turn_length_seconds\":86400,\"users\":[{\"user\":{\"id\":\"PXPGF42\",\"type\":\"user_reference\"}}],\"restrictions\":[{\"type\":\"daily_restriction\",\"start_time_of_day\":\"08:00:00\",\"duration_seconds\":32400}]}]}}\n\n@endpoint GET /schedules/{id}\n@desc Get a schedule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the schedule's time zone., since: str(date-time) # The start of the date range over which you want to show schedule entries. Defaults to 2 weeks before until if an until is given. Optional parameter. When provided with include[] for schedule types, populates the rendered_schedule_entries fields in the response., until: str(date-time) # The end of the date range over which you want to show schedule entries. Defaults to 2 weeks after since if a since is given. Optional parameter. When provided with include[] for schedule types, populates the rendered_schedule_entries fields in the response., overflow: bool=false # Any on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter `overflow=true` is passed. This parameter defaults to false. For instance, if your schedule is a rotation that changes daily at midnight UTC, and your date range is from `2011-06-01T10:00:00Z` to `2011-06-01T14:00:00Z`:   - If you don't pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T10:00:00Z` and end of `2011-06-01T14:00:00Z`. - If you do pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T00:00:00Z` and end of `2011-06-02T00:00:00Z`., include_next_oncall_for_user: str # Specify an `user_id`, and the schedule list API will return information about this user's next on-call.}\n@returns(200) {schedule: any} # The schedule object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /schedules/{id}\n@desc Delete a schedule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The schedule was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /schedules/{id}\n@desc Update a schedule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., schedule: any}\n@optional {overflow: bool=false # Any on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter `overflow=true` is passed. This parameter defaults to false. For instance, if your schedule is a rotation that changes daily at midnight UTC, and your date range is from `2011-06-01T10:00:00Z` to `2011-06-01T14:00:00Z`:   - If you don't pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T10:00:00Z` and end of `2011-06-01T14:00:00Z`. - If you do pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T00:00:00Z` and end of `2011-06-02T00:00:00Z`.}\n@returns(200) {schedule: any} # The updated schedule.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"schedule\":{\"name\":\"Daily Engineering Rotation\",\"type\":\"schedule\",\"time_zone\":\"America/New_York\",\"description\":\"Rotation schedule for engineering\",\"schedule_layers\":[{\"name\":\"Night Shift\",\"start\":\"2015-11-06T20:00:00-05:00\",\"end\":\"2016-11-06T20:00:00-05:00\",\"rotation_virtual_start\":\"2015-11-06T20:00:00-05:00\",\"rotation_turn_length_seconds\":86400,\"users\":[{\"user\":{\"id\":\"PXPGF42\",\"type\":\"user_reference\"}}],\"restrictions\":[{\"type\":\"daily_restriction\",\"start_time_of_day\":\"08:00:00\",\"duration_seconds\":32400}]}]}}\n\n@endpoint GET /schedules/{id}/audit/records\n@desc List audit records for a schedule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., since: str(date-time) # The start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours), until: str(date-time) # The end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`.}\n@returns(200) Records matching the query criteria.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /schedules/{id}/overrides\n@desc List overrides\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search.}\n@optional {editable: bool # When this parameter is present, only editable overrides will be returned. The result will only include the id of the override if this parameter is present. Only future overrides are editable., overflow: bool # Any on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter overflow=true is passed. This parameter defaults to false.}\n@returns(201) {overrides: [any]} # The collection of override objects returned by the query.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /schedules/{id}/overrides\n@desc Create one or more overrides\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {overrides: [any]}\n@returns(201) A list of overrides requested and a status code indicating whether they were created or rejected\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"overrides\":[{\"start\":\"2012-07-01T00:00:00-04:00\",\"end\":\"2012-07-02T00:00:00-04:00\",\"user\":{\"id\":\"PEYSGVA\",\"type\":\"user_reference\"},\"time_zone\":\"UTC\"},{\"start\":\"2012-07-03T00:00:00-04:00\",\"end\":\"2012-07-04T00:00:00-04:00\",\"user\":{\"id\":\"PEYSGVF\",\"type\":\"user_reference\"},\"time_zone\":\"UTC\"}]}\n\n@endpoint DELETE /schedules/{id}/overrides/{override_id}\n@desc Delete an override\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., override_id: str # The override ID on the schedule.}\n@returns(200) The override was truncated.\n@returns(204) The override was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /schedules/{id}/users\n@desc List users on call.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search.}\n@returns(200) {users: [any]} # The users on the given schedule.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /schedules/preview\n@desc Preview a schedule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, schedule: any}\n@optional {since: str(date-time) # The start of the date range over which you want to search., until: str(date-time) # The end of the date range over which you want to search., overflow: bool=false # Any on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter `overflow=true` is passed. This parameter defaults to false. For instance, if your schedule is a rotation that changes daily at midnight UTC, and your date range is from `2011-06-01T10:00:00Z` to `2011-06-01T14:00:00Z`:   - If you don't pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T10:00:00Z` and end of `2011-06-01T14:00:00Z`. - If you do pass the `overflow=true` parameter, you will get one schedule entry returned with a start of `2011-06-01T00:00:00Z` and end of `2011-06-02T00:00:00Z`.}\n@returns(200) {schedule: any} # What the schedule will look like if posted.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"schedule\":{\"name\":\"Daily Engineering Rotation\",\"type\":\"schedule\",\"time_zone\":\"America/New_York\",\"description\":\"Rotation schedule for engineering\",\"schedule_layers\":[{\"name\":\"Night Shift\",\"start\":\"2015-11-06T20:00:00-05:00\",\"end\":\"2016-11-06T20:00:00-05:00\",\"rotation_virtual_start\":\"2015-11-06T20:00:00-05:00\",\"rotation_turn_length_seconds\":86400,\"users\":[{\"user\":{\"id\":\"PXPGF42\",\"type\":\"user_reference\"}}],\"restrictions\":[{\"type\":\"daily_restriction\",\"start_time_of_day\":\"08:00:00\",\"duration_seconds\":32400}]}]}}\n\n@endgroup\n\n@group service_dependencies\n@endpoint POST /service_dependencies/associate\n@desc Associate service dependencies\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {relationships: [map{supporting_service: map, dependent_service: map}] # List of all service dependencies to be created.}\n@returns(200) {relationships: [map]} # An array of service relationships that were successfully associated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"relationships\":[{\"supporting_service\":{\"id\":\"P7AD56\",\"type\":\"service\"},\"dependent_service\":{\"id\":\"P99DJ6\",\"type\":\"business_service\"}},{\"supporting_service\":{\"id\":\"DT93K1\",\"type\":\"business_service\"},\"dependent_service\":{\"id\":\"RS34D9\",\"type\":\"service\"}}]}\n\n@endpoint GET /service_dependencies/business_services/{id}\n@desc Get Business Service dependencies\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {relationships: [map]} # An array of service relationships.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /service_dependencies/disassociate\n@desc Disassociate service dependencies\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {relationships: [map{supporting_service: map, dependent_service: map}] # List of all service dependencies to be deleted.}\n@returns(200) {relationships: [map]} # An array of service relationships that were successfully disassociated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"relationships\":[{\"supporting_service\":{\"id\":\"P7AD56\",\"type\":\"service\"},\"dependent_service\":{\"id\":\"P99DJ6\",\"type\":\"business_service\"}},{\"supporting_service\":{\"id\":\"DT93K1\",\"type\":\"business_service\"},\"dependent_service\":{\"id\":\"RS34D9\",\"type\":\"service\"}}]}\n\n@endpoint GET /service_dependencies/technical_services/{id}\n@desc Get technical service dependencies\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {relationships: [map]} # An array of service relationships.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endgroup\n\n@group services\n@endpoint GET /services\n@desc List services\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {query: str # Filters the result, showing only the records whose name matches the query., limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., time_zone: str(tzinfo) # Time zone in which results will be rendered. This will default to the account time zone., sort_by: str(name/name:asc/name:desc)=name # Used to specify the field you wish to sort the results on., include[]: str(escalation_policies/teams/integrations/auto_pause_notifications_parameters) # Array of additional details to include., name: str # Filters the results, showing only services with the specified name.}\n@returns(200) A paginated array of services.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint POST /services\n@desc Create a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, service: any}\n@returns(201) {service: any} # The service that was created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n@example_request {\"service\":{\"type\":\"service\",\"name\":\"My Web App\",\"description\":\"My cool web application that does things.\",\"auto_resolve_timeout\":14400,\"acknowledgement_timeout\":600,\"status\":\"active\",\"escalation_policy\":{\"id\":\"PWIP6CQ\",\"type\":\"escalation_policy_reference\"},\"incident_urgency_rule\":{\"type\":\"use_support_hours\",\"during_support_hours\":{\"type\":\"constant\",\"urgency\":\"high\"},\"outside_support_hours\":{\"type\":\"constant\",\"urgency\":\"low\"}},\"support_hours\":{\"type\":\"fixed_time_per_day\",\"time_zone\":\"America/Lima\",\"start_time\":\"09:00:00\",\"end_time\":\"17:00:00\",\"days_of_week\":[1,2,3,4,5]},\"scheduled_actions\":[{\"type\":\"urgency_change\",\"at\":{\"type\":\"named_time\",\"name\":\"support_hours_start\"},\"to_urgency\":\"high\"}],\"alert_creation\":\"create_alerts_and_incidents\",\"alert_grouping_parameters\":{\"type\":\"time\",\"config\":{\"timeout\":2}},\"auto_pause_notifications_parameters\":{\"enabled\":true,\"timeout\":300}}}\n\n@endpoint GET /services/{id}\n@desc Get a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str(escalation_policies/teams/auto_pause_notifications_parameters/integrations): any # Array of additional details to include.}\n@returns(200) {service: any} # The service requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint DELETE /services/{id}\n@desc Delete a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The service was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint PUT /services/{id}\n@desc Update a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., service: any}\n@returns(200) {service: any} # The service that was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"service\":{\"type\":\"service\",\"name\":\"My Web App\",\"description\":\"My cool web application that does things.\",\"auto_resolve_timeout\":14400,\"acknowledgement_timeout\":600,\"status\":\"active\",\"escalation_policy\":{\"id\":\"PWIP6CQ\",\"type\":\"escalation_policy_reference\"},\"incident_urgency_rule\":{\"type\":\"use_support_hours\",\"during_support_hours\":{\"type\":\"constant\",\"urgency\":\"high\"},\"outside_support_hours\":{\"type\":\"constant\",\"urgency\":\"low\"}},\"support_hours\":{\"type\":\"fixed_time_per_day\",\"time_zone\":\"America/Lima\",\"start_time\":\"09:00:00\",\"end_time\":\"17:00:00\",\"days_of_week\":[1,2,3,4,5]},\"scheduled_actions\":[{\"type\":\"urgency_change\",\"at\":{\"type\":\"named_time\",\"name\":\"support_hours_start\"},\"to_urgency\":\"high\"}],\"alert_creation\":\"create_alerts_and_incidents\",\"alert_grouping_parameters\":{\"type\":\"time\",\"config\":{\"timeout\":2}},\"auto_pause_notifications_parameters\":{\"enabled\":true,\"timeout\":300}}}\n\n@endpoint GET /services/{id}/audit/records\n@desc List audit records for a service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., since: str(date-time) # The start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours), until: str(date-time) # The end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`.}\n@returns(200) Records matching the query criteria.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /services/{id}/change_events\n@desc List Change Events for a service\n@required {id: str # The ID of the resource., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {since: str(date-time) # The start of the date range over which you want to search, as a UTC ISO 8601 datetime string. Will return an HTTP 400 for non-UTC datetimes., until: str(date-time) # The end of the date range over which you want to search, as a UTC ISO 8601 datetime string. Will return an HTTP 400 for non-UTC datetimes., limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., integration_ids[]: [str] # An array of integration IDs. Only results related to these integrations will be returned.}\n@returns(200) {change_events: [any]} # The array of Change Events returned by the query.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /services/{id}/integrations\n@desc Create a new integration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., integration: any}\n@returns(201) {integration: any} # The integration that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"integration\":{\"type\":\"generic_email_inbound_integration\",\"name\":\"Email\",\"service\":{\"id\":\"PQL78HM\",\"type\":\"service_reference\"},\"integration_email\":\"my-email-based-integration@subdomain.pagerduty.com\",\"vendor\":{\"type\":\"vendor_reference\",\"id\":\"PZD94QK\"}}}\n\n@endpoint PUT /services/{id}/integrations/{integration_id}\n@desc Update an existing integration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., integration_id: str # The integration ID on the service., integration: any}\n@returns(200) {integration: any} # The integration that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"integration\":{\"type\":\"generic_email_inbound_integration\",\"name\":\"Email\",\"service\":{\"id\":\"PQL78HM\",\"type\":\"service_reference\",\"summary\":\"My Email-Based Integration\",\"self\":\"https://api.pagerduty.com/services/PQL78HM\",\"html_url\":\"https://subdomain.pagerduty.com/service-directory/PQL78HM\"},\"integration_email\":\"my-email-based-integration@subdomain.pagerduty.com\",\"vendor\":{\"type\":\"vendor_reference\",\"id\":\"PZD94QK\"}}}\n\n@endpoint GET /services/{id}/integrations/{integration_id}\n@desc View an integration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., integration_id: str # The integration ID on the service.}\n@optional {include[]: str(services/vendors): any # Array of additional details to include.}\n@returns(200) {integration: any} # The integration that was requested.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /services/{id}/rules\n@desc List Service's Event Rules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., include[]: str # Array of additional Models to include in response.}\n@returns(200) A paginated array of Event Rule objects.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /services/{id}/rules\n@desc Create an Event Rule on a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule: any}\n@returns(201) {rule: any} # The Event Rule that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 409: The request conflicts with the current state of the server.}\n@example_request {\"rule\":{\"id\":\"14e56445-ebab-4dd0-ba9d-fc28a41b7e7b\",\"position\":0,\"disabled\":false,\"conditions\":{\"operator\":\"and\",\"subconditions\":[{\"operator\":\"contains\",\"parameters\":{\"value\":\"mysql\",\"path\":\"class\"}}]},\"time_frame\":{\"active_between\":{\"start_time\":1577880000000,\"end_time\":1580558400000}},\"actions\":{\"annotate\":{\"value\":\"This incident was modified by an Event Rule\"},\"priority\":{\"value\":\"PCMUB6F\"},\"severity\":{\"value\":\"warning\"},\"extractions\":[{\"target\":\"dedup_key\",\"source\":\"custom_details.error_summary\",\"regex\":\"Host (.*) is experiencing errors\"}]}}}\n\n@endpoint POST /services/{id}/rules/convert\n@desc Convert a Service's Event Rules into Event Orchestration Rules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {convert_status: str, converted_to: str(url)} # The Event Orchestration Rules were successfully created\n@errors {400: Could not create equivalent Event Orchestration Rules based on the Service's current Event Rules, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n\n@endpoint GET /services/{id}/rules/{rule_id}\n@desc Get an Event Rule from a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule_id: str # The id of the Event Rule to retrieve.}\n@returns(200) {rule: any} # The Event Rule object.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /services/{id}/rules/{rule_id}\n@desc Update an Event Rule on a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule_id: str # The id of the Event Rule to retrieve., rule_id: str # The id of the Event Rule to update on the Service.}\n@optional {rule: any}\n@returns(200) {rule: any} # The Event Rule that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n@example_request {\"rule_id\":\"7123bdd1-74e8-4aa7-aa38-4a9ebe123456\",\"rule\":{\"actions\":{\"suppress\":{\"value\":true}}}}\n\n@endpoint DELETE /services/{id}/rules/{rule_id}\n@desc Delete an Event Rule from a Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., rule_id: str # The id of the Event Rule to retrieve.}\n@returns(204) The Event Rule was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 405: The request was received and recognized by the server, but its HTTP method was rejected for the requested resource., 409: The request conflicts with the current state of the server.}\n\n@endpoint POST /services/custom_fields\n@desc Create a Field\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, field: map{data_type!: str, description: str, display_name!: str, enabled: bool, field_options: [map], field_type!: str, name!: str} # Details of the custom field to be created.}\n@returns(201) {field: map{created_at: str(date-time), data_type: str, description: str?, display_name: str, enabled: bool, field_options: [map], field_type: str, id: str, name: str, self: str(url)?, summary: str?, type: str, updated_at: str(date-time)}} # The field object created, along with the Field Options if provided.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field\":{\"data_type\":\"string\",\"description\":\"The environment that the service operates in\",\"display_name\":\"Environment\",\"enabled\":true,\"field_options\":[{\"data\":{\"data_type\":\"string\",\"value\":\"production\"}},{\"data\":{\"data_type\":\"string\",\"value\":\"staging\"}},{\"data\":{\"data_type\":\"string\",\"value\":\"development\"}}],\"field_type\":\"single_value_fixed\",\"name\":\"environment\"}}\n\n@endpoint GET /services/custom_fields\n@desc List Fields\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {fields: [map]} # A list of fields.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /services/custom_fields/{field_id}\n@desc Get a Field\n@required {field_id: str # The ID of the field., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {field: map{created_at: str(date-time), data_type: str, description: str?, display_name: str, enabled: bool, field_options: [map], field_type: str, id: str, name: str, self: str(url)?, summary: str?, type: str, updated_at: str(date-time)}} # The field requested.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /services/custom_fields/{field_id}\n@desc Update a Field\n@required {field_id: str # The ID of the field., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, field: map{description: str, display_name: str, enabled: bool, field_options: [any]} # Details of the custom field to be updated.}\n@returns(200) {field: map{created_at: str(date-time), data_type: str, description: str?, display_name: str, enabled: bool, field_options: [map], field_type: str, id: str, name: str, self: str(url)?, summary: str?, type: str, updated_at: str(date-time)}} # The field object updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field\":{\"description\":\"The production environment where this service is deployed\",\"display_name\":\"Production Environment\",\"enabled\":true}}\n\n@endpoint DELETE /services/custom_fields/{field_id}\n@desc Delete a Field\n@required {field_id: str # The ID of the field., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(204) The field was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /services/custom_fields/{field_id}/field_options\n@desc List Field Options\n@required {field_id: str # The ID of the field., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {field_options: [map]} # List of field options.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /services/custom_fields/{field_id}/field_options\n@desc Create a Field Option\n@required {field_id: str # The ID of the field., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, field_option: map{data!: map} # An option for a custom field. Can only be applied to fields with a `field_type` of `single_value_fixed` or `multi_value_fixed`.}\n@returns(201) {field_option: map{created_at: str(date-time), data: map{data_type: str, value: str}, id: str, type: str, updated_at: str(date-time)}} # The field option created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field_option\":{\"data\":{\"data_type\":\"string\",\"value\":\"production\"}}}\n\n@endpoint GET /services/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Get a Field Option\n@required {field_id: str # The ID of the field., field_option_id: str # The ID of the field option., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {field_option: map{created_at: str(date-time), data: map{data_type: str, value: str}, id: str, type: str, updated_at: str(date-time)}} # The requested field option.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /services/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Update a Field Option\n@required {field_id: str # The ID of the field., field_option_id: str # The ID of the field option., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, field_option: map{data!: map} # An option for a custom field. Can only be applied to fields with a `field_type` of `single_value_fixed` or `multi_value_fixed`.}\n@returns(200) {field_option: map{created_at: str(date-time), data: map{data_type: str, value: str}, id: str, type: str, updated_at: str(date-time)}} # The field option updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"field_option\":{\"data\":{\"data_type\":\"string\",\"value\":\"prod\"}}}\n\n@endpoint DELETE /services/custom_fields/{field_id}/field_options/{field_option_id}\n@desc Delete a Field Option\n@required {field_id: str # The ID of the field., field_option_id: str # The ID of the field option., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(204) The field option was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /services/{id}/custom_fields/values\n@desc Get Custom Field Values\n@required {id: str # The ID of the resource., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {custom_fields: [map]} # The list of custom field values.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /services/{id}/custom_fields/values\n@desc Update Custom Field Values\n@required {id: str # The ID of the resource., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, custom_fields: [any]}\n@returns(201) {custom_fields: [map]} # The custom field values were updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"custom_fields\":[{\"id\":\"PT4KHEE\",\"value\":\"production\"}]}\n\n@endpoint GET /services/{id}/enablements\n@desc Get Enablements for a Service\n@required {id: str # The ID of the resource., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {enablements: [map]} # The list of feature enablement settings for the service.\n@errors {403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /services/{id}/enablements/{feature_name}\n@desc Update an Enablement for a Service\n@required {id: str # The ID of the resource., feature_name: str # The feature enablement identifier, typically the name of the product addon. Currently only `aiops` is supported., Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, enablement: map{feature: str, enabled!: bool, updated_at: str(date-time), warnings: [map]}}\n@returns(200) {enablement: map{feature: str, enabled: bool, updated_at: str(date-time), warnings: [map]}} # The feature enablement setting was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"enablement\":{\"enabled\":true}}\n\n@endgroup\n\n@group session_configurations\n@endpoint GET /session_configurations\n@desc Get an account's session configurations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {type: str(mobile/web) # Session configuration type. If omitted, returns both mobile and web configurations.}\n@returns(200) {session_configurations: [map]} # Session Configurations retrieved successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /session_configurations\n@desc Configure an account's session configurations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type: str(mobile/web) # Session configuration type. This can be either 'mobile' or 'web', or a comma-separated list of both., session_configuration: map{absolute_session_ttl!: int, idle_session_ttl!: int}}\n@returns(200) {session_configurations: [map]} # Session Configurations updated successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /session_configurations\n@desc Delete an account's session configurations.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, type: str(mobile/web) # Session configuration type. This can be either 'mobile' or 'web', or a comma-separated list of both.}\n@returns(204) Session Configurations deleted successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group standards\n@endpoint GET /standards\n@desc List Standards\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {active: bool, resource_type: str}\n@returns(200) OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /standards/{id}\n@desc Update a standard\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # Id of the standard}\n@returns(200) {active: bool, description: str, id: str, name: str, type: str, resource_type: str, exclusions: [map], inclusions: [map]} # OK\n@errors {400: Unprocessable Entity. Some arguments failed validation checks., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"active\":false}\n\n@endpoint GET /standards/scores/{resource_type}\n@desc List resources' standards scores\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., ids: [str] # Ids of resources to apply the standards. Maximum of 100 items, resource_type: str}\n@returns(200) OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /standards/scores/{resource_type}/{id}\n@desc List a resource's standards scores\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # Id of the resource to apply the standards., resource_type: str}\n@returns(200) {resource_id: str, resource_type: str, score: map{passing: int, total: int}, standards: [map]} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group status_dashboards\n@endpoint GET /status_dashboards\n@desc List Status Dashboards\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@returns(200) OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_dashboards/{id}\n@desc Get a single Status Dashboard by `id`\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) {status_dashboard: map{id: str, url_slug: str, name: str}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_dashboards/{id}/service_impacts\n@desc Get impacted Business Services for a Status Dashboard by `id`.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {additional_fields[]: str(services.highest_impacting_priority/total_impacted_count): any # Provides access to additional fields such as highest priority per business service and total impacted count}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_dashboards/url_slugs/{url_slug}\n@desc Get a single Status Dashboard by `url_slug`\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., url_slug: str # The `url_slug` for a status dashboard}\n@returns(200) {status_dashboard: map{id: str, url_slug: str, name: str}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_dashboards/url_slugs/{url_slug}/service_impacts\n@desc Get impacted Business Services for a  Status Dashboard by `url_slug`\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., url_slug: str # The `url_slug` for a status dashboard}\n@optional {additional_fields[]: str(services.highest_impacting_priority/total_impacted_count): any # Provides access to additional fields such as highest priority per business service and total impacted count}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group status_pages\n@endpoint GET /status_pages\n@desc List Status Pages\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {status_page_type: str(public/private) # The type of the Status Page.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/impacts\n@desc List Status Page Impacts\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {post_type: str(incident/maintenance) # Filter by Post type.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/impacts/{impact_id}\n@desc Get a Status Page Impact\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., impact_id: str # The ID of the Status Page Impact.}\n@returns(200) {impact: map{id: str, self: str, description: str, post_type: str, status_page: map{id: str, type: str}, type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/services\n@desc List Status Page Services\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/services/{service_id}\n@desc Get a Status Page Service\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., service_id: str # The ID of the Status Page service.}\n@returns(200) {service: map{id: str, self: str, name: str, status_page: map{id: str, type: str}, business_service: any, type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/severities\n@desc List Status Page Severities\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {post_type: str(incident/maintenance) # Filter by Post type.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/severities/{severity_id}\n@desc Get a Status Page Severity\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., severity_id: str # The ID of the Status Page severity.}\n@returns(200) {severity: map{id: str, self: str, description: str, post_type: str, status_page: map{id: str, type: str}, type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/statuses\n@desc List Status Page Statuses\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {post_type: str(incident/maintenance) # Filter by Post type.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/statuses/{status_id}\n@desc Get a Status Page Status\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., status_id: str # The ID of the Status Page status.}\n@returns(200) {status: map{id: str, self: str, description: str, post_type: str, status_page: map{id: str, type: str}, type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/posts\n@desc List Status Page Posts\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {post_type: str(incident/maintenance) # Filter by Post type., reviewed_status: str(approved/not_reviewed) # Filter by the reviewed status of the Post to retrieve., status[]: [str] # Filter by an array of Status identifiers.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /status_pages/{id}/posts\n@desc Create a Status Page Post\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post: map{type!: str, title!: str, post_type!: str, starts_at!: str(date-time), ends_at!: str(date-time), updates!: [map], status_page!: map} # Request schema for creating/updating a given Status Page Post resource.}\n@returns(201) {post: map{id: str, self: str, type: str, post_type: str, status_page: map{id: str, type: str}, linked_resource: map{id: str, type: str}, postmortem: map{id: str, type: str}, title: str, starts_at: str(date-time)?, ends_at: str(date-time)?, updates: [map]}} # Created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"post\":{\"ends_at\":\"2023-12-12T11:00:00.000Z\",\"post_type\":\"maintenance\",\"starts_at\":\"2023-12-12T11:00:00.000Z\",\"status_page\":{\"id\":\"PR5LMML\",\"type\":\"status_page\"},\"title\":\"maintenance window for database upgrade\",\"type\":\"status_page_post\",\"updates\":[{\"impacted_services\":[{\"impact\":{\"id\":\"PY5OM08\",\"type\":\"status_page_impact\"},\"service\":{\"id\":\"PYHMEI3\",\"type\":\"status_page_service\"}}],\"message\":\"<p>Message</p>\",\"update_frequency_ms\":null,\"notify_subscribers\":false,\"severity\":{\"id\":\"PY5OM08\",\"type\":\"status_page_severity\"},\"status\":{\"id\":\"P0400H4\",\"type\":\"status_page_status\"},\"type\":\"status_page_post_update\"}]}}\n\n@endpoint GET /status_pages/{id}/posts/{post_id}\n@desc Get a Status Page Post\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post.}\n@optional {include[]: [str]: any # Array of additional Models to include in response.}\n@returns(200) {post: map{id: str, self: str, type: str, post_type: str, status_page: map{id: str, type: str}, linked_resource: map{id: str, type: str}, postmortem: map{id: str, type: str}, title: str, starts_at: str(date-time)?, ends_at: str(date-time)?, updates: [map]}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /status_pages/{id}/posts/{post_id}\n@desc Update a Status Page Post\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post., post: map{type!: str, title!: str, post_type!: str, starts_at!: str(date-time), ends_at!: str(date-time), status_page!: map} # Request schema for creating a given Status Page Post resource.}\n@returns(200) {post: map{id: str, self: str, type: str, post_type: str, status_page: map{id: str, type: str}, linked_resource: map{id: str, type: str}, postmortem: map{id: str, type: str}, title: str, starts_at: str(date-time)?, ends_at: str(date-time)?, updates: [map]}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"post\":{\"ends_at\":\"2023-12-12T11:00:00.000Z\",\"post_type\":\"maintenance\",\"starts_at\":\"2023-12-12T11:00:00.000Z\",\"status_page\":{\"id\":\"PR5LMML\",\"type\":\"status_page\"},\"title\":\"maintenance window for database upgrade\",\"type\":\"status_page_post\"}}\n\n@endpoint DELETE /status_pages/{id}/posts/{post_id}\n@desc Delete a Status Page Post\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post.}\n@returns(204) No Content\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/posts/{post_id}/post_updates\n@desc List Status Page Post Updates\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post.}\n@optional {reviewed_status: str(approved/not_reviewed) # Filter by the reviewed status of the Post Update to retrieve.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /status_pages/{id}/posts/{post_id}/post_updates\n@desc Create a Status Page Post Update\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post., post_update: map{self: str, post!: map, message!: str, status!: map, severity!: map, impacted_services!: [map], update_frequency_ms!: int, notify_subscribers!: bool, reported_at: str(date-time), type!: str} # Attributes for Post Update creation/update}\n@returns(201) {post_update: map{id: str, self: str, post: map{id: str, type: str}, message: str, reviewed_status: str, status: map{id: str, type: str}, severity: map{id: str, type: str}, impacted_services: [map], update_frequency_ms: int?, notify_subscribers: bool, reported_at: str(date-time)?, type: str}} # Created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"post_update\":{\"impacted_services\":[{\"impact\":{\"id\":\"PY5OM08\",\"type\":\"status_page_impact\"},\"service\":{\"id\":\"PYHMEI3\",\"type\":\"status_page_service\"}}],\"message\":\"<p>Message</p>\",\"notify_subscribers\":false,\"post\":{\"id\":\"P6F2CJ3\",\"type\":\"status_page_post\"},\"severity\":{\"id\":\"PY5OM08\",\"type\":\"status_page_severity\"},\"status\":{\"id\":\"P0400H4\",\"type\":\"status_page_status\"},\"type\":\"status_page_post_update\"}}\n\n@endpoint GET /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}\n@desc Get a Status Page Post Update\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post., post_update_id: str # The ID of the Status Page Post Update.}\n@returns(200) {post_update: map{id: str, self: str, post: map{id: str, type: str}, message: str, reviewed_status: str, status: map{id: str, type: str}, severity: map{id: str, type: str}, impacted_services: [map], update_frequency_ms: int?, notify_subscribers: bool, reported_at: str(date-time)?, type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}\n@desc Update a Status Page Post Update\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post., post_update_id: str # The ID of the Status Page Post Update., post_update: map{self: str, post!: map, message!: str, status!: map, severity!: map, impacted_services!: [map], update_frequency_ms!: int, notify_subscribers!: bool, reported_at: str(date-time), type!: str} # Attributes for Post Update creation/update}\n@returns(200) {post_update: map{id: str, self: str, post: map{id: str, type: str}, message: str, reviewed_status: str, status: map{id: str, type: str}, severity: map{id: str, type: str}, impacted_services: [map], update_frequency_ms: int?, notify_subscribers: bool, reported_at: str(date-time)?, type: str}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"post_update\":{\"impacted_services\":[{\"impact\":{\"id\":\"PY5OM08\",\"type\":\"status_page_impact\"},\"service\":{\"id\":\"PYHMEI3\",\"type\":\"status_page_service\"}}],\"message\":\"<p>Message</p>\",\"notify_subscribers\":false,\"post\":{\"id\":\"P6F2CJ3\",\"type\":\"status_page_post\"},\"severity\":{\"id\":\"PY5OM08\",\"type\":\"status_page_severity\"},\"status\":{\"id\":\"P0400H4\",\"type\":\"status_page_status\"},\"type\":\"status_page_post_update\"}}\n\n@endpoint DELETE /status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}\n@desc Delete a Status Page Post Update\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post., post_update_id: str # The ID of the Status Page Post Update.}\n@returns(204) No Content\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/posts/{post_id}/postmortem\n@desc Get a Post Postmortem\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post.}\n@returns(200) {postmortem: map{id: str, self: str, post: map{id: str, type: str}, message: str, notify_subscribers: bool, reported_at: str(date-time), type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /status_pages/{id}/posts/{post_id}/postmortem\n@desc Create a Post Postmortem\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post.}\n@optional {postmortem: map{type!: str, post!: map, message!: str, notify_subscribers!: bool} # Request to create/update a given Postmortem resource.}\n@returns(201) {postmortem: map{id: str, self: str, post: map{id: str, type: str}, message: str, notify_subscribers: bool, reported_at: str(date-time), type: str}} # Created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"postmortem\":{\"message\":\"<p>Something wrong happened and this is a postmortem.<p>\",\"notify_subscribers\":true,\"post\":{\"id\":\"P6F2CJ3\",\"self\":\"https://api.pagerduty.com/status_pages/PR5LMML/posts/P6F2CJ3\",\"type\":\"status_page_post\"},\"type\":\"status_page_post_postmortem\"}}\n\n@endpoint PUT /status_pages/{id}/posts/{post_id}/postmortem\n@desc Update a Post Postmortem\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post., postmortem: map{type!: str, post!: map, message!: str, notify_subscribers!: bool} # Request to create/update a given Postmortem resource.}\n@returns(200) {postmortem: map{id: str, self: str, post: map{id: str, type: str}, message: str, notify_subscribers: bool, reported_at: str(date-time), type: str}} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"postmortem\":{\"message\":\"<p>Something wrong happened and this is a postmortem.<p>\",\"notify_subscribers\":true,\"post\":{\"id\":\"P6F2CJ3\",\"self\":\"https://api.pagerduty.com/status_pages/PR5LMML/posts/P6F2CJ3\",\"type\":\"status_page_post\"},\"type\":\"status_page_post_postmortem\"}}\n\n@endpoint DELETE /status_pages/{id}/posts/{post_id}/postmortem\n@desc Delete a Post Postmortem\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., post_id: str # The ID of the Status Page Post.}\n@returns(204) No Content\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /status_pages/{id}/subscriptions\n@desc List Status Page Subscriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@optional {status: str(active/pending) # Filter by Subscription status., channel: str(webhook/email/slack) # Filter by Subscription channel.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /status_pages/{id}/subscriptions\n@desc Create a Status Page Subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscription: map{channel!: str, contact!: str, status_page!: map, subscribable_object!: map, type!: str} # Request schema for creating a StatusPageSubscription.}\n@returns(201) {subscription: map{channel: str, contact: str, id: str, self: str, status: str, status_page: map{id: str, type: str}, subscribable_object: map{id: str, type: str}, type: str}} # Created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"subscription\":{\"channel\":\"email\",\"contact\":\"joe@email.example\",\"status_page\":{\"id\":\"PIJ90N7\",\"type\":\"status_page\"},\"subscribable_object\":{\"id\":\"PSX4LJI\",\"type\":\"status_page_service\"},\"type\":\"status_page_subscription\"}}\n\n@endpoint GET /status_pages/{id}/subscriptions/{subscription_id}\n@desc Get a Status Page Subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscription_id: str # The ID of the Status Page subscription.}\n@returns(200) {subscription: map{channel: str, contact: str, id: str, self: str, status: str, status_page: map{id: str, type: str}, subscribable_object: map{id: str, type: str}, type: str}} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /status_pages/{id}/subscriptions/{subscription_id}\n@desc Delete a Status Page Subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscription_id: str # The ID of the Status Page subscription.}\n@returns(204) No Content\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group sre_agent\n@endpoint GET /sre_agent/memories\n@desc List SRE Agent memories\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int=20 - incident_summary # The number of results to return per page., service_id: str # Filter memories by service ID, incident_id: str # Filter memories by incident ID, type: str(runbook/service_profile/incident_playbook) # Filter memories by type}\n@returns(200) An array of SRE Agent memories.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /sre_agent/memories/{id}\n@desc Update an SRE Agent memory\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., memory: map{content!: str}}\n@returns(200) {memory: map{id: str, content: str, attributes: map{account_id: str, service_id: str, incident_id: str, type: str}, created_at: str(date-time), updated_at: str(date-time)}} # The SRE Agent memory that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"memory\":{\"content\":\"Updated memory content - The database connection pool was increased to 100 connections to resolve performance issues during peak load.\"}}\n\n@endpoint DELETE /sre_agent/memories/{id}\n@desc Delete an SRE Agent memory\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The SRE Agent memory was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group tags\n@endpoint GET /tags\n@desc List tags\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Filters the result, showing only the tags whose label matches the query.}\n@returns(200) An array of tags names.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /tags\n@desc Create a tag\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, tag: any}\n@returns(201) {tag: any} # The tag that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"tag\":{\"type\":\"tag\",\"label\":\"Batman\"}}\n\n@endpoint GET /tags/{id}\n@desc Get a tag\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {tag: any} # The tag requested.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /tags/{id}\n@desc Delete a tag\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The tag was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /tags/{id}/{entity_type}\n@desc Get connected entities\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., entity_type: str(users/teams/escalation_policies) # Type of entity related with the tag}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) An array of connected entities.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group teams\n@endpoint POST /teams\n@desc Create a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, team: any}\n@returns(201) {team: any} # The team that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"team\":{\"type\":\"team\",\"name\":\"Engineering\",\"description\":\"The engineering team\"}}\n\n@endpoint GET /teams\n@desc List teams\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Filters the result, showing only the records whose name matches the query.}\n@returns(200) A paginated array of teams.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /teams/{id}\n@desc Get a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str: any # Array of additional Models to include in response.}\n@returns(200) {team: any} # The team requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /teams/{id}\n@desc Delete a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {reassignment_team: str # Team to reassign unresolved incident to. If an unresolved incident exists on both the reassignment team and the team being deleted, a duplicate will not be made. If not supplied, unresolved incidents will be made account-level.}\n@returns(204) The team was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /teams/{id}\n@desc Update a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., team: any}\n@returns(200) {team: any} # The team that was updated.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"team\":{\"type\":\"team\",\"name\":\"Engineering\",\"description\":\"The engineering team\"}}\n\n@endpoint GET /teams/{id}/audit/records\n@desc List audit records for a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., since: str(date-time) # The start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours), until: str(date-time) # The end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`.}\n@returns(200) Records matching the query criteria.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint DELETE /teams/{id}/escalation_policies/{escalation_policy_id}\n@desc Remove an escalation policy from a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., escalation_policy_id: str # The escalation policy ID on the team.}\n@returns(204) The escalation policy was removed from the team.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /teams/{id}/escalation_policies/{escalation_policy_id}\n@desc Add an escalation policy to a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., escalation_policy_id: str # The escalation policy ID on the team.}\n@returns(204) The escalation policy was added to the team.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /teams/{id}/members\n@desc List members of a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., include[]: str # Array of additional Models to include in response.}\n@returns(200) A paginated array of users within the requested team.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /teams/{id}/notification_subscriptions\n@desc List Team Notification Subscriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /teams/{id}/notification_subscriptions\n@desc Create Team Notification Subscriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribables: [map{subscribable_id: str, subscribable_type: str}]}\n@returns(200) {subscriptions: [map]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribables\":[{\"subscribable_type\":\"incident\",\"subscribable_id\":\"PD1234\"},{\"subscribable_type\":\"business_service\",\"subscribable_id\":\"PD1234\"},{\"subscribable_type\":\"business_service\",\"subscribable_id\":\"PD1235\"}]}\n\n@endpoint POST /teams/{id}/notification_subscriptions/unsubscribe\n@desc Unsubscribe the given Team from Notifications on the matching Subscribable entities.\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribables: [map{subscribable_id: str, subscribable_type: str}]}\n@returns(200) {deleted_count: num, unauthorized_count: num, non_existent_count: num} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribables\":[{\"subscribable_type\":\"incident\",\"subscribable_id\":\"PD1234\"},{\"subscribable_type\":\"business_service\",\"subscribable_id\":\"PD1234\"}]}\n\n@endpoint DELETE /teams/{id}/users/{user_id}\n@desc Remove a user from a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., user_id: str # The user ID on the team.}\n@returns(204) The user was removed to the team.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /teams/{id}/users/{user_id}\n@desc Add a user to a team\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., user_id: str # The user ID on the team.}\n@optional {role: str(observer/responder/manager) # The role of the user on the team.}\n@returns(204) The user was added to the team.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"role\":\"observer\"}\n\n@endgroup\n\n@group templates\n@endpoint GET /templates\n@desc List templates\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., query: str # Template name or description to search, template_type: str=status_update # Filters templates by type., sort_by: str(name/name:asc/name:desc/created_at/created_at:asc/created_at:desc)=created_at:asc # Used to specify both the field you wish to sort the results on (name/created_at), as well as the direction (asc/desc) of the results. The sort_by field and direction should be separated by a colon. Sort direction defaults to ascending.}\n@returns(200) A paginated array of templates.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /templates\n@desc Create a template\n@required {template: map{template_type: str, name: str, description: str, templated_fields: map}}\n@returns(201) {template: any} # Template successfully created\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"template\":{\"description\":\"Sample template description\",\"templated_fields\":{\"email_body\":\"<div> sample </div>\",\"email_subject\":\"Sample email Subject\",\"message\":\"Sample SMS message\"},\"name\":\"Sample Template\",\"template_type\":\"status_update\"}}\n\n@endpoint GET /templates/{id}\n@desc Get a template\n@required {id: str # The ID of the resource.}\n@returns(200) {template: any} # Successful operation\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /templates/{id}\n@desc Update a template\n@required {id: str # The ID of the resource., template: map{template_type: str, name: str, description: str, templated_fields: map}}\n@returns(200) {template: any} # Successful operation\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"template\":{\"description\":\"Sample template description\",\"templated_fields\":{\"email_body\":\"<div> sample </div>\",\"email_subject\":\"Sample email Subject\",\"message\":\"Sample SMS message\"},\"name\":\"Sample Template\",\"template_type\":\"status_update\"}}\n\n@endpoint DELETE /templates/{id}\n@desc Delete a template\n@required {id: str # The ID of the resource.}\n@returns(204) Successful operation\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /templates/{id}/render\n@desc Render a template\n@required {id: str # The ID of the resource.}\n@returns(200) {templated_fields: map{email_subject: str, email_body: str, message: str}, warnings: map{email_subject: [str], email_body: [str], message: [str]}, errors: [str]} # Successful operation\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"incident_id\":\"QT4KHLK034QWE34\",\"status_update\":{\"message\":\"Status update message\"}}\n\n@endpoint GET /templates/fields\n@desc List template fields\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {fields: [map]} # An array of template fields.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group users\n@endpoint GET /users\n@desc List users\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {query: str # Filters the result, showing only the records whose name matches the query., team_ids[]: [str] # An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter., limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., include[]: str(contact_methods/notification_rules/teams/subdomains) # Array of additional Models to include in response.}\n@returns(200) A paginated array of users.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /users\n@desc Create a user\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, From: str(email) # The email address of a valid user associated with the account making the request., user: any}\n@returns(201) {user: any} # The user that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"user\":{\"type\":\"user\",\"name\":\"Earline Greenholt\",\"email\":\"125.greenholt.earline@graham.name\",\"time_zone\":\"America/Lima\",\"color\":\"green\",\"role\":\"admin\",\"job_title\":\"Director of Engineering\",\"avatar_url\":\"https://secure.gravatar.com/avatar/1d1a39d4635208d5664082a6c654a73f.png?d=mm&r=PG\",\"description\":\"I'm the boss\",\"license\":{\"id\":\"PTDVERC\",\"type\":\"license_reference\"}}}\n\n@endpoint GET /users/{id}\n@desc Get a user\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str(contact_methods/notification_rules/teams/subdomains): any # Array of additional Models to include in response.}\n@returns(200) {user: any} # The user requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}\n@desc Delete a user\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The user was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /users/{id}\n@desc Update a user\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., user: any}\n@returns(200) {user: any} # The user that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"user\":{\"type\":\"user\",\"name\":\"Earline Greenholt\",\"email\":\"125.greenholt.earline@graham.name\",\"time_zone\":\"America/Lima\",\"color\":\"green\",\"role\":\"admin\",\"job_title\":\"Director of Engineering\",\"avatar_url\":\"https://secure.gravatar.com/avatar/1d1a39d4635208d5664082a6c654a73f.png?d=mm&r=PG\",\"description\":\"I'm the boss\",\"license\":{\"id\":\"PTDVERC\",\"type\":\"license_reference\"}}}\n\n@endpoint GET /users/{id}/audit/records\n@desc List audit records for a user\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., since: str(date-time) # The start of the date range over which you want to search. If not specified, defaults to `now() - 24 hours` (past 24 hours), until: str(date-time) # The end of the date range over which you want to search. If not specified, defaults to `now()`. May not be more than 31 days after `since`.}\n@returns(200) Records matching the query criteria.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /users/{id}/contact_methods\n@desc List a user's contact methods\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {contact_methods: [any]} # A list of contact methods.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /users/{id}/contact_methods\n@desc Create a user contact method\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., contact_method: any}\n@returns(201) {contact_method: any} # The contact method that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method\",\"summary\":\"Work\",\"self\":\"https://api.pagerduty.com/users/PXPGF42/contact_method/PXPGF42\",\"label\":\"Work\",\"address\":\"grady.haylie.126@hickle.net\",\"send_short_email\":false}}\n\n@endpoint GET /users/{id}/contact_methods/{contact_method_id}\n@desc Get a user's contact method\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., contact_method_id: str # The contact method ID on the user.}\n@returns(200) {contact_method: any} # The user's contact method requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}/contact_methods/{contact_method_id}\n@desc Delete a user's contact method\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., contact_method_id: str # The contact method ID on the user.}\n@returns(204) The contact method was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /users/{id}/contact_methods/{contact_method_id}\n@desc Update a user's contact method\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., contact_method_id: str # The contact method ID on the user., contact_method: any}\n@returns(200) {contact_method: any} # The user's contact method that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method\",\"summary\":\"Work\",\"self\":\"https://api.pagerduty.com/users/PXPGF42/contact_method/PXPGF42\",\"label\":\"Work\",\"address\":\"grady.haylie.126@hickle.net\",\"send_short_email\":false}}\n\n@endpoint GET /users/{id}/oauth_delegations\n@desc List a user's delegations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {delegation_type: str(mobile/web/integration) # The type of OAuth delegations to filter on. Allowed values are 'mobile', 'web', and 'integration'. You can pass one or more types in, separated by commas (e.g., `type=web,mobile`)., status: str(issued/revoked) # The status of the delegations to return. Allowed values are 'issued' and 'revoked'. You can pass one or more statuses in, separated by commas (e.g., `status=issued,revoked`)., limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set.}\n@returns(200) {oauth_delegations: [map], limit: int, more: bool, next_cursor: str} # Delegations retrieved sucessfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /users/{id}/oauth_delegations/{delegation_id}\n@desc Get a user's delegation\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., delegation_id: str # The ID of the delegation.}\n@returns(200) {id: str, status: str, client_id: str, delegation_type: str, scope: str, created_at: str(date-time), expires_at: str(date-time), self: str(uri)} # Delegation retrieved successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /users/{id}/license\n@desc Get the License allocated to a User\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {license: any} # The License allocated to the User\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /users/{id}/notification_rules\n@desc List a user's notification rules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str: any # Array of additional details to include., urgency: str(high/low/all) # The incident urgency for which the notification rules are applied. If not specified, defaults to `high`.}\n@returns(200) {notification_rules: [any]} # A list of notification rules.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /users/{id}/notification_rules\n@desc Create a user notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., notification_rule: any}\n@returns(201) {notification_rule: any} # The notification rule that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"notification_rule\":{\"type\":\"assignment_notification_rule\",\"start_delay_in_minutes\":0,\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method_reference\"},\"urgency\":\"high\"}}\n\n@endpoint GET /users/{id}/notification_rules/{notification_rule_id}\n@desc Get a user's notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., notification_rule_id: str # The notification rule ID on the user.}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {notification_rule: any} # The user's notification rule requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}/notification_rules/{notification_rule_id}\n@desc Delete a user's notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., notification_rule_id: str # The notification rule ID on the user.}\n@returns(204) The notification rule was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /users/{id}/notification_rules/{notification_rule_id}\n@desc Update a user's notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., notification_rule_id: str # The notification rule ID on the user., notification_rule: any}\n@returns(200) {notification_rule: any} # The user's notification rule that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"notification_rule\":{\"type\":\"assignment_notification_rule\",\"start_delay_in_minutes\":0,\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method_reference\"},\"urgency\":\"high\"}}\n\n@endpoint GET /users/{id}/notification_subscriptions\n@desc List Notification Subscriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /users/{id}/notification_subscriptions\n@desc Create Notification Subcriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribables: [map{subscribable_id: str, subscribable_type: str}]}\n@returns(200) {subscriptions: [map]} # OK\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribables\":[{\"subscribable_type\":\"incident\",\"subscribable_id\":\"PD1234\"},{\"subscribable_type\":\"business_service\",\"subscribable_id\":\"PD1234\"},{\"subscribable_type\":\"business_service\",\"subscribable_id\":\"PD1235\"}]}\n\n@endpoint POST /users/{id}/notification_subscriptions/unsubscribe\n@desc Remove Notification Subscriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource., subscribables: [map{subscribable_id: str, subscribable_type: str}]}\n@returns(200) {deleted_count: num, unauthorized_count: num, non_existent_count: num} # OK\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 422: Unprocessable Entity. Some arguments failed validation checks.}\n@example_request {\"subscribables\":[{\"subscribable_type\":\"incident\",\"subscribable_id\":\"PD1234\"},{\"subscribable_type\":\"business_service\",\"subscribable_id\":\"PD1234\"}]}\n\n@endpoint GET /users/{id}/oncall_handoff_notification_rules\n@desc List a User's Handoff Notification Rules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {oncall_handoff_notification_rules: [map]} # A list of Handoff Notification Rules.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /users/{id}/oncall_handoff_notification_rules\n@desc Create a User Handoff Notification Rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., oncall_handoff_notification_rule: map{id!: str, notify_advance_in_minutes: int, handoff_type!: str, contact_method!: any} # A rule for contacting the user for Handoff Notifications.}\n@returns(201) {oncall_handoff_notification_rule: map{id: str, notify_advance_in_minutes: int, handoff_type: str, contact_method: any}} # The Handoff Notification Rule that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"oncall_handoff_notification_rule\":{\"id\":\"PXPGF43\",\"handoff_type\":\"both\",\"notify_advance_in_minutes\":180,\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method_reference\"}}}\n\n@endpoint GET /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id}\n@desc Get a user's handoff notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., oncall_handoff_notification_rule_id: str # The oncall handoff notification rule ID on the user.}\n@returns(200) {oncall_handoff_notification_rule: map{id: str, notify_advance_in_minutes: int, handoff_type: str, contact_method: any}} # The user's handoff notification rule requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id}\n@desc Delete a User's Handoff Notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., oncall_handoff_notification_rule_id: str # The oncall handoff notification rule ID on the user.}\n@returns(204) The handoff notification rule was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /users/{id}/oncall_handoff_notification_rules/{oncall_handoff_notification_rule_id}\n@desc Update a User's Handoff Notification Rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., oncall_handoff_notification_rule_id: str # The oncall handoff notification rule ID on the user., oncall_handoff_notification_rule: map{id!: str, notify_advance_in_minutes: int, handoff_type!: str, contact_method!: any} # A rule for contacting the user for Handoff Notifications.}\n@returns(200) {oncall_handoff_notification_rule: map{id: str, notify_advance_in_minutes: int, handoff_type: str, contact_method: any}} # The User's Handoff Notification Rule that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"oncall_handoff_notification_rule\":{\"id\":\"PXPGF42\",\"handoff_type\":\"both\",\"notify_advance_in_minutes\":60,\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method_reference\"}}}\n\n@endpoint GET /users/{id}/sessions\n@desc List a user's active sessions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {user_sessions: [map]} # A list of the user's active sessions.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}/sessions\n@desc Delete all user sessions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) The user sessions were all deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /users/{id}/sessions/{type}/{session_id}\n@desc Get a user's session\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., type: str # The session type for the user session ID., session_id: str # The session ID for the user.}\n@returns(200) {user_session: map{id: str, user_id: str, created_at: str(date-time), type: str, summary: str}} # The user's session requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}/sessions/{type}/{session_id}\n@desc Delete a user's session\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., type: str # The session type for the user session ID., session_id: str # The session ID for the user.}\n@returns(204) The user session was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /users/{id}/status_update_notification_rules\n@desc List a user's status update notification rules\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {status_update_notification_rules: [map]} # A list of status update notification rules.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /users/{id}/status_update_notification_rules\n@desc Create a user status update notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., status_update_notification_rule: map{contact_method!: any} # A rule for contacting the user for Incident Status Updates.}\n@returns(201) {status_update_notification_rule: map{contact_method: any}} # The status update notification rule that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"status_update_notification_rule\":{\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method_reference\"}}}\n\n@endpoint GET /users/{id}/status_update_notification_rules/{status_update_notification_rule_id}\n@desc Get a user's status update notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., status_update_notification_rule_id: str # The status update notification rule ID on the user.}\n@optional {include[]: str: any # Array of additional details to include.}\n@returns(200) {notification_rule: map{contact_method: any}} # The user's status update notification rule requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint DELETE /users/{id}/status_update_notification_rules/{status_update_notification_rule_id}\n@desc Delete a user's status update notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., status_update_notification_rule_id: str # The status update notification rule ID on the user.}\n@returns(204) The status update notification rule was deleted successfully.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PUT /users/{id}/status_update_notification_rules/{status_update_notification_rule_id}\n@desc Update a user's status update notification rule\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., status_update_notification_rule_id: str # The status update notification rule ID on the user., status_update_notification_rule: map{contact_method!: any} # A rule for contacting the user for Incident Status Updates.}\n@returns(200) {notification_rule: map{contact_method: any}} # The user's status update notification rule that was updated.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 402: Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"status_update_notification_rule\":{\"contact_method\":{\"id\":\"PXPGF42\",\"type\":\"email_contact_method_reference\"}}}\n\n@endpoint GET /users/me\n@desc Get the current user\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {include[]: str(contact_methods/notification_rules/teams/subdomains): any # Array of additional Models to include in response.}\n@returns(200) {user: any} # The requesting user.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group vendors\n@endpoint GET /vendors\n@desc List vendors\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information.}\n@returns(200) A paginated array of vendors.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group schedules\n@endpoint GET /v3/schedules\n@desc List schedules\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!}\n@optional {limit: int=100 # Maximum number of schedules to return, offset: int=0}\n@returns(200) {schedules: [map], limit: int, offset: int, more: bool} # Schedules retrieved successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /v3/schedules\n@desc Create a schedule\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, schedule: map{name!: str, time_zone!: str, description: str, teams: [map]}}\n@returns(201) {schedule: map{id: str, type: str, name: str, time_zone: str, description: str, teams: [any], escalation_policies: [any], users: [any], rotations: [map], final_schedule: map{type: str, rendered_coverage_percentage: num(double), computed_shift_assignments: [map]}, http_cal_url: str(uri), web_cal_url: str(uri), self: str(uri), html_url: str(uri)}} # Schedule created successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"schedule\":{\"name\":\"Engineering On-Call\",\"time_zone\":\"America/New_York\"}}\n\n@endpoint GET /v3/schedules/{id}\n@desc Get a schedule\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule.}\n@optional {since: str(date-time) # Start of time range (ISO 8601), until: str(date-time) # End of time range (ISO 8601), time_zone: str # IANA timezone identifier for rendering shift times. Defaults to the schedule's configured time zone., overflow: bool=false # Include shifts that extend beyond the requested time range boundaries, include[]: [str] # Additional data to include in the schedule response: - `final_schedule`: computed on-call assignments for the time range}\n@returns(200) {schedule: map{id: str, type: str, name: str, time_zone: str, description: str, teams: [any], escalation_policies: [any], users: [any], rotations: [map], final_schedule: map{type: str, rendered_coverage_percentage: num(double), computed_shift_assignments: [map]}, http_cal_url: str(uri), web_cal_url: str(uri), self: str(uri), html_url: str(uri)}} # Schedule retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /v3/schedules/{id}\n@desc Update a schedule\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., schedule: map{name: str, time_zone: str, description: str}}\n@returns(200) {schedule: map{id: str, type: str, name: str, time_zone: str, description: str, teams: [any], escalation_policies: [any], users: [any], rotations: [map], final_schedule: map{type: str, rendered_coverage_percentage: num(double), computed_shift_assignments: [map]}, http_cal_url: str(uri), web_cal_url: str(uri), self: str(uri), html_url: str(uri)}} # Schedule updated successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"schedule\":{\"name\":\"New Schedule Name\"}}\n\n@endpoint DELETE /v3/schedules/{id}\n@desc Delete a schedule\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule.}\n@returns(204) Schedule deleted successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /v3/schedules/{id}/custom_shifts\n@desc List custom shifts\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., since: str(date-time) # Start of time range (ISO 8601), until: str(date-time) # End of time range (ISO 8601)}\n@optional {time_zone: str # IANA timezone identifier for rendering shift times. Defaults to the schedule's configured time zone., overflow: bool=false # Include shifts that extend beyond the requested time range boundaries, limit: int=25, offset: int=0}\n@returns(200) {custom_shifts: [map], limit: int, offset: int, more: bool} # Custom shifts retrieved successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /v3/schedules/{id}/custom_shifts\n@desc Create custom shifts\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., custom_shifts: [map{type!: str, start_time!: str(date-time), end_time!: str(date-time), assignments!: [map]}]}\n@returns(201) {custom_shifts: [map]} # Custom shifts created successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"custom_shifts\":[{\"type\":\"custom_shift\",\"start_time\":\"2025-03-15T09:00:00Z\",\"end_time\":\"2025-03-15T17:00:00Z\",\"assignments\":[{\"type\":\"shift_assignment\",\"member\":{\"type\":\"user_member\",\"user_id\":\"PUSER123\"}}]}]}\n\n@endpoint GET /v3/schedules/{id}/custom_shifts/{custom_shift_id}\n@desc Get a custom shift\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., custom_shift_id: str # The ID of the custom shift.}\n@returns(200) {custom_shift: map{id: str, type: str, start_time: str(date-time), end_time: str(date-time), assignments: [map], self: str(uri), html_url: str(uri)}} # Custom shift retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /v3/schedules/{id}/custom_shifts/{custom_shift_id}\n@desc Update a custom shift\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., custom_shift_id: str # The ID of the custom shift., custom_shift: map{start_time: str(date-time), end_time: str(date-time), assignments: [map]} # If the shift has already started, only `end_time` can be modified.}\n@returns(200) {custom_shift: map{id: str, type: str, start_time: str(date-time), end_time: str(date-time), assignments: [map], self: str(uri), html_url: str(uri)}} # Custom shift updated successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"custom_shift\":{\"start_time\":\"2025-03-15T10:00:00Z\",\"end_time\":\"2025-03-15T18:00:00Z\",\"assignments\":[{\"type\":\"shift_assignment\",\"member\":{\"type\":\"user_member\",\"user_id\":\"PUSER456\"}}]}}\n\n@endpoint DELETE /v3/schedules/{id}/custom_shifts/{custom_shift_id}\n@desc Delete a custom shift\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., custom_shift_id: str # The ID of the custom shift.}\n@returns(204) Custom shift deleted successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /v3/schedules/{id}/overrides\n@desc List overrides\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., since: str(date-time) # Start of time range (ISO 8601), until: str(date-time) # End of time range (ISO 8601)}\n@optional {time_zone: str # IANA timezone identifier for rendering shift times. Defaults to the schedule's configured time zone., overflow: bool=false # Include shifts that extend beyond the requested time range boundaries, limit: int=25, offset: int=0}\n@returns(200) {overrides: [map], limit: int, offset: int, more: bool} # Overrides retrieved successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /v3/schedules/{id}/overrides\n@desc Create overrides\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., overrides: [map{type!: str, rotation_id: str, custom_shift_id: str, start_time!: str(date-time), end_time!: str(date-time), overridden_member!: map, overriding_member!: map}]}\n@returns(201) {overrides: [map]} # Overrides created successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"overrides\":[{\"type\":\"override_shift\",\"rotation_id\":\"ABCDEFGHIJKLMNOPQRSTUVWXY\",\"start_time\":\"2025-03-15T09:00:00Z\",\"end_time\":\"2025-03-15T17:00:00Z\",\"overridden_member\":{\"type\":\"user_member\",\"user_id\":\"PUSER123\"},\"overriding_member\":{\"type\":\"user_member\",\"user_id\":\"PUSER456\"}}]}\n\n@endpoint GET /v3/schedules/{id}/overrides/{override_id}\n@desc Get an override\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., override_id: str # The ID of the override.}\n@returns(200) {override: map{id: str, type: str, rotation_id: str, custom_shift_id: str, start_time: str(date-time), end_time: str(date-time), overridden_member: map{type: str, user_id: str}, overriding_member: map{type: str, user_id: str}, self: str(uri), html_url: str(uri)}} # Override retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /v3/schedules/{id}/overrides/{override_id}\n@desc Update an override\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., override_id: str # The ID of the override., override: map{start_time: str(date-time), end_time: str(date-time), overriding_member: map}}\n@returns(200) {override: map{id: str, type: str, rotation_id: str, custom_shift_id: str, start_time: str(date-time), end_time: str(date-time), overridden_member: map{type: str, user_id: str}, overriding_member: map{type: str, user_id: str}, self: str(uri), html_url: str(uri)}} # Override updated successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"override\":{\"start_time\":\"2025-03-15T10:00:00Z\",\"end_time\":\"2025-03-15T18:00:00Z\",\"overriding_member\":{\"type\":\"user_member\",\"user_id\":\"PUSER789\"}}}\n\n@endpoint DELETE /v3/schedules/{id}/overrides/{override_id}\n@desc Delete an override\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., override_id: str # The ID of the override.}\n@returns(204) Override deleted successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /v3/schedules/{id}/rotations\n@desc List rotations\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule.}\n@optional {limit: int=25, offset: int=0}\n@returns(200) {rotations: [map], limit: int, offset: int, more: bool} # Rotations retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /v3/schedules/{id}/rotations\n@desc Create a rotation\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule.}\n@returns(201) {rotation: map{id: str, type: str, events: [map], self: str(uri), html_url: str(uri)}} # Rotation created successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /v3/schedules/{id}/rotations/{rotation_id}\n@desc Get a rotation\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation.}\n@optional {since: str(date-time) # Start of time range (ISO 8601), until: str(date-time) # End of time range (ISO 8601)}\n@returns(200) {rotation: map{id: str, type: str, events: [map], self: str(uri), html_url: str(uri)}} # Rotation retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint DELETE /v3/schedules/{id}/rotations/{rotation_id}\n@desc Delete a rotation\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation.}\n@returns(204) Rotation deleted successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint GET /v3/schedules/{id}/rotations/{rotation_id}/events\n@desc List events\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation.}\n@optional {limit: int=25, offset: int=0}\n@returns(200) {events: [map], limit: int, offset: int, more: bool} # Events retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint POST /v3/schedules/{id}/rotations/{rotation_id}/events\n@desc Create an event\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation., event: map{name!: str, start_time!: map, end_time!: map, effective_since!: str(date-time), effective_until: str(date-time), recurrence!: [str], assignment_strategy!: map}}\n@returns(201) {event: map{id: str, type: str, name: str, start_time: map{date_time: str(date-time), time_zone: str}, end_time: map{date_time: str(date-time), time_zone: str}, effective_since: str(date-time), effective_until: str(date-time)?, recurrence: [str], assignment_strategy: map{type: str, shifts_per_member: int, members: [map]}, self: str(uri), html_url: str(uri)}} # Event created successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"event\":{\"name\":\"Weekly On-Call\",\"start_time\":{\"date_time\":\"2025-03-03T09:00:00Z\",\"time_zone\":\"America/New_York\"},\"end_time\":{\"date_time\":\"2025-03-10T09:00:00Z\",\"time_zone\":\"America/New_York\"},\"effective_since\":\"2025-03-03T00:00:00Z\",\"recurrence\":[\"RRULE:FREQ=WEEKLY\"],\"assignment_strategy\":{\"type\":\"rotating_member_assignment_strategy\",\"shifts_per_member\":1,\"members\":[{\"type\":\"user_member\",\"user_id\":\"PUSER123\"},{\"type\":\"user_member\",\"user_id\":\"PUSER456\"}]}}}\n\n@endpoint GET /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id}\n@desc Get an event\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation., event_id: str # The ID of the event.}\n@optional {since: str(date-time) # Start of time range (ISO 8601), until: str(date-time) # End of time range (ISO 8601)}\n@returns(200) {event: map{id: str, type: str, name: str, start_time: map{date_time: str(date-time), time_zone: str}, end_time: map{date_time: str(date-time), time_zone: str}, effective_since: str(date-time), effective_until: str(date-time)?, recurrence: [str], assignment_strategy: map{type: str, shifts_per_member: int, members: [map]}, self: str(uri), html_url: str(uri)}} # Event retrieved successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endpoint PUT /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id}\n@desc Update an event\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation., event_id: str # The ID of the event., event: map{name: str, start_time: map, end_time: map, effective_since: str(date-time), effective_until: str(date-time), recurrence: [str], assignment_strategy: map}}\n@returns(200) {event: map{id: str, type: str, name: str, start_time: map{date_time: str(date-time), time_zone: str}, end_time: map{date_time: str(date-time), time_zone: str}, effective_since: str(date-time), effective_until: str(date-time)?, recurrence: [str], assignment_strategy: map{type: str, shifts_per_member: int, members: [map]}, self: str(uri), html_url: str(uri)}} # Event updated successfully\n@errors {400: Bad Request — The request contains invalid parameters or data, 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n@example_request {\"event\":{\"effective_until\":\"2025-09-01T00:00:00Z\"}}\n\n@endpoint DELETE /v3/schedules/{id}/rotations/{rotation_id}/events/{event_id}\n@desc Delete an event\n@required {X-EARLY-ACCESS: str=flexible-schedules-early-access # This header indicates that this API endpoint is __UNDER CONSTRUCTION__ and may change at any time. You __MUST__ pass in this header with the value `flexible-schedules-early-access`. Do not use this endpoint in production, as it may change!, id: str # The ID of the schedule., rotation_id: str # The ID of the rotation., event_id: str # The ID of the event.}\n@returns(204) Event deleted successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 500: Internal Server Error the PagerDuty server experienced an error.}\n\n@endgroup\n\n@group vendors\n@endpoint GET /vendors/{id}\n@desc Get a vendor\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {vendor: [any]} # The vendor requested\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@group webhook_subscriptions\n@endpoint GET /webhook_subscriptions\n@desc List webhook subscriptions\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {limit: int # The number of results per page., offset: int # Offset to start pagination search results., total: bool=false # By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated.  See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more information., filter_type: str(account/service/team) # The type of resource to filter upon., filter_id: str # The id of the resource to filter upon. Required if filter_type is service or team.}\n@returns(200) A set of webhook subscriptions matching the request.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint POST /webhook_subscriptions\n@desc Create a webhook subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, webhook_subscription: map{id: str, type!: str, active: bool, delivery_method!: map, description: str, events!: [str], filter!: map, oauth_client: map}}\n@returns(200) {webhook_subscription: map{id: str, type: str, active: bool, delivery_method: map{id: str, secret: str?, temporarily_disabled: bool, type: str, url: str(url), custom_headers: [map]}, description: str, events: [str], filter: map{id: str, type: str}, oauth_client: map{id: str, type: str, summary: str}}} # The webhook subscription that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n@example_request {\"webhook_subscription\":{\"delivery_method\":{\"type\":\"http_delivery_method\",\"url\":\"https://example.com/receive_a_pagerduty_webhook\",\"custom_headers\":[{\"name\":\"header-name\",\"value\":\"header-value\"}]},\"description\":\"Sends PagerDuty v3 webhook events somewhere interesting.\",\"events\":[\"incident.acknowledged\",\"incident.annotated\",\"incident.delegated\",\"incident.escalated\",\"incident.priority_updated\",\"incident.reassigned\",\"incident.reopened\",\"incident.resolved\",\"incident.responder.added\",\"incident.responder.replied\",\"incident.triggered\",\"incident.unacknowledged\"],\"filter\":{\"id\":\"P393ZNQ\",\"type\":\"service_reference\"},\"oauth_client_id\":\"AGMEB7F7YJYELCPG4Y5YWMYGXE\",\"type\":\"webhook_subscription\"}}\n\n@endpoint GET /webhook_subscriptions/{id}\n@desc Get a webhook subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) {webhook_subscription: map{id: str, type: str, active: bool, delivery_method: map{id: str, secret: str?, temporarily_disabled: bool, type: str, url: str(url), custom_headers: [map]}, description: str, events: [str], filter: map{id: str, type: str}, oauth_client: map{id: str, type: str, summary: str}}} # The webhook subscription that was requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /webhook_subscriptions/{id}\n@desc Update a webhook subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@optional {webhook_subscription: map{description: str, events: [str], filter: map, active: bool, oauth_client_id: str}}\n@returns(200) {webhook_subscription: map{id: str, type: str, active: bool, delivery_method: map{id: str, secret: str?, temporarily_disabled: bool, type: str, url: str(url), custom_headers: [map]}, description: str, events: [str], filter: map{id: str, type: str}, oauth_client: map{id: str, type: str, summary: str}}} # The updated webhook subscription.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"webhook_subscription\":{\"events\":[\"incident.acknowledged\",\"incident.annotated\",\"incident.delegated\",\"incident.escalated\",\"incident.priority_updated\",\"incident.reassigned\",\"incident.reopened\",\"incident.resolved\",\"incident.responder.added\",\"incident.responder.replied\",\"incident.triggered\",\"incident.unacknowledged\"]}}\n\n@endpoint DELETE /webhook_subscriptions/{id}\n@desc Delete a webhook subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(204) The webhook subscription was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /webhook_subscriptions/{id}/enable\n@desc Enable a webhook subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) {webhook_subscription: map{id: str, type: str, active: bool, delivery_method: map{id: str, secret: str?, temporarily_disabled: bool, type: str, url: str(url), custom_headers: [map]}, description: str, events: [str], filter: map{id: str, type: str}, oauth_client: map{id: str, type: str, summary: str}}} # The webhook subscription that was successfully enabled.\n@errors {401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint POST /webhook_subscriptions/{id}/ping\n@desc Test a webhook subscription\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(202) Accepted\n@errors {401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint GET /webhook_subscriptions/oauth_clients\n@desc List OAuth clients\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json}\n@returns(200) {oauth_clients: [map]} # A list of OAuth clients\n@errors {401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n\n@endpoint POST /webhook_subscriptions/oauth_clients\n@desc Create an OAuth client\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, oauth_client: map{name!: str, client_id!: str, client_secret!: str, scope: str, token_url!: str(uri), grant_type!: str}}\n@returns(201) {oauth_client: map{id: str, type: str, name: str, client_id: str, scope: str?, token_url: str(uri), grant_type: str, status: str}} # OAuth client created successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action.}\n@example_request {\"oauth_client\":{\"name\":\"PagerDuty Webhook Integration\",\"client_id\":\"oauth-client-id\",\"client_secret\":\"oauth-secret-id\",\"token_url\":\"https://foo.oauth-server.com/oauth_token.do\",\"grant_type\":\"client_credentials\"}}\n\n@endpoint GET /webhook_subscriptions/oauth_clients/{id}\n@desc Get an OAuth client\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(200) {oauth_client: map{id: str, type: str, name: str, client_id: str, scope: str?, token_url: str(uri), grant_type: str, status: str}} # OAuth client details\n@errors {401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endpoint PUT /webhook_subscriptions/oauth_clients/{id}\n@desc Update an OAuth client\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource., oauth_client: map{name: str, client_id: str, client_secret: str, scope: str, token_url: str(uri), grant_type: str}}\n@returns(200) {oauth_client: map{id: str, type: str, name: str, client_id: str, scope: str?, token_url: str(uri), grant_type: str, status: str}} # OAuth client updated successfully\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n@example_request {\"oauth_client\":{\"name\":\"Updated ServiceNow Integration\",\"scope\":\"read write admin\"}}\n\n@endpoint DELETE /webhook_subscriptions/oauth_clients/{id}\n@desc Delete an OAuth client\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, id: str # The ID of the resource.}\n@returns(204) OAuth client deleted successfully\n@errors {401: Caller did not supply credentials or did not provide the correct credentials.  If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource.  While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found.}\n\n@endgroup\n\n@group workflows\n@endpoint GET /workflows/integrations\n@desc List Workflow Integrations\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., include_deprecated: bool=false # Whether to include deprecated Integrations in the response.}\n@returns(200) A paginated list of Workflow Integrations.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /workflows/integrations/{id}\n@desc Get Workflow Integration\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., id: str # The ID of the resource.}\n@returns(200) The Workflow Integration requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /workflows/integrations/connections\n@desc List all Workflow Integration Connections\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., name: str # Filter Integrations by partial name.}\n@returns(200) A paginated list of Workflow Integration Connections.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint GET /workflows/integrations/{integration_id}/connections\n@desc List Workflow Integration Connections\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@optional {limit: int # The minimum of the `limit` parameter used in the request or the maximum request size of the API., cursor: str # Optional parameter used to request the \"next\" set of results from an API.  The value provided here is most commonly obtained from the `next_cursor` field of the previous request.  When no value is provided, the request starts at the beginning of the result set., name: str # Filter Integrations by partial name.}\n@returns(200) A paginated list of Workflow Integration Connections.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint POST /workflows/integrations/{integration_id}/connections\n@desc Create Workflow Integration Connection\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, name: str # The name given to the connection, secrets: map # The secrets for this connection. The secrets schema is defined in the Workflow Integration's `secrets_schema` property. It is dynamic based on the specific Workflow Integration. This field is write-only and will always be `null` on a response so that secrets are not leaked.}\n@optional {id: str # The ID of the connection, type: str # The type of the connection, integration_id: str # The integration ID that this connection is associated with, service_url: str # The URL of the service that this connection is associated with, external_id: str # The ID of the external system that this connection is used to connect to, external_id_label: str # The label of the external system that this connection is used to connect to, scopes: [str], is_default: bool # Whether or not this connection is the default connection for this integration, health: map{is_healthy: bool, health_message: str, last_checked_at: str(date-time)}, configuration: map # The configuration for this connection. The configuration schema is defined in the Workflow Integration's `configuration_schema` property. It is dynamic based on the specific Workflow Integration., teams: [map{team_id: str, type: str}] # The teams whose managers are allowed to use or edit this connection, apps: [map{app_id: str, type: str}] # The app IDs for this connection}\n@returns(201) The Workflow Integration Connection that was created.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"connection\":{\"name\":\"My Connection\",\"service_url\":\"https://webhook.site\",\"external_id\":\"My Connection\",\"external_id_label\":\"Connection Name\",\"configuration\":{\"Health Check URL\":\"https://example.com/health\",\"Allowed Hostnames\":\"webhook.site\",\"Health Check Method\":\"GET\"},\"secrets\":{\"Authentication Headers\":\"x-api-key: 1234abcd\"},\"is_default\":true,\"teams\":[],\"apps\":[]}}\n\n@endpoint GET /workflows/integrations/{integration_id}/connections/{id}\n@desc Get Workflow Integration Connection\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@returns(200) The Workflow Integration Connection requested.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endpoint PATCH /workflows/integrations/{integration_id}/connections/{id}\n@desc Update Workflow Integration Connection\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header., Content-Type: str=application/json, name: str # The name given to the connection, secrets: map # The secrets for this connection. The secrets schema is defined in the Workflow Integration's `secrets_schema` property. It is dynamic based on the specific Workflow Integration. This field is write-only and will always be `null` on a response so that secrets are not leaked.}\n@optional {id: str # The ID of the connection, type: str # The type of the connection, integration_id: str # The integration ID that this connection is associated with, service_url: str # The URL of the service that this connection is associated with, external_id: str # The ID of the external system that this connection is used to connect to, external_id_label: str # The label of the external system that this connection is used to connect to, scopes: [str], is_default: bool # Whether or not this connection is the default connection for this integration, health: map{is_healthy: bool, health_message: str, last_checked_at: str(date-time)}, configuration: map # The configuration for this connection. The configuration schema is defined in the Workflow Integration's `configuration_schema` property. It is dynamic based on the specific Workflow Integration., teams: [map{team_id: str, type: str}] # The teams whose managers are allowed to use or edit this connection, apps: [map{app_id: str, type: str}] # The app IDs for this connection}\n@returns(200) The updated Workflow Integration Connection.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n@example_request {\"connection\":{\"name\":\"My Connection\",\"service_url\":\"https://webhook.site\",\"external_id\":\"My Connection\",\"external_id_label\":\"Connection Name\",\"configuration\":{\"Health Check URL\":\"https://example.com/health\",\"Allowed Hostnames\":\"webhook.site\",\"Health Check Method\":\"GET\"},\"secrets\":{\"Authentication Headers\":\"x-api-key: 1234abcd\"},\"is_default\":true,\"teams\":[],\"apps\":[]}}\n\n@endpoint DELETE /workflows/integrations/{integration_id}/connections/{id}\n@desc Delete Workflow Integration Connection\n@required {Accept: str=application/vnd.pagerduty+json;version=2 # The `Accept` header is used as a versioning header.}\n@returns(204) The Workflow Integration Connection was deleted successfully.\n@errors {400: Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work., 401: Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed., 403: Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action., 404: The requested resource was not found., 429: Too many requests have been made, the rate limit has been reached.}\n\n@endgroup\n\n@end\n"}}