Associate a Trigger and Service Associate a Service with an existing Incident Workflow Trigger Scoped OAuth requires: `incident_workflows.write`

Lua path

app.integrations.pagerduty.associate_trigger_and_service

Full name

pagerduty.pagerduty_associate_service_to_incident_workflow_trigger

Cancel responder requests for an incident Cancel pending responder requests for the specified incident. This endpoint allows you to cancel responder requests for specified targets that are in a pending state. Only responders who have not yet joined or declined can be cancelled. This endpoint requires the account to have access to the [responder requests](https://support.pagerduty.com/main/docs/add-responders) feature. **Account Ability Requirement**: The account must have the `coordinated_responding` ability. Returns 402 Payment Required if the ability is missing. You can use the [List Abilities API](openapiv3.json/paths/~1abilities/get) to check account abilities. **State Constraints**: Only responders in the `pending` state can be cancelled. Responders who have already `joined` or `declined` are not affected (the result will indicate their current state). **User vs Escalation Policy Behavior**: - **Users**: Direct cancellation, updates state to `user_cancelled`, stops notifications - **Escalation Policies**: Stops the escalation process, updates state of all pending users from that escalation policy to `user_cancelled` and stops notifications **Result Values**: - `cancelled`: Successfully cancelled - `joined`: User already joined (not cancelled) - `declined`: User already declined (not cancelled) - `not_found`: Target not found or not part of any responder request Scoped OAuth requires: `incidents.write`

Lua path

app.integrations.pagerduty.cancel_responder_requests_incident

Full name

pagerduty.pagerduty_cancel_incident_responder_request

Convert a Service's Event Rules into Event Orchestration Rules Convert this Service's Event Rules into functionally equivalent Event Orchestration Rules. Sending a request to this API endpoint has several effects: 1. Automatically creates Event Orchestration Rules for this Service that will behave identically as this Service's currently configured Event Rules. 2. Makes all existing Event Rules for this Service read-only. All future updates need to be made via the newly created Event Orchestration rules. Sending a request to this API endpoint will **not** change how future events will be processed. If past events for this Service have been evaluated via Event Rules then new events sent to this Service will also continue to be evaluated via the (now read-only) Event Rules. To change this Service so that new events start being evaluated via the newly created Event Orchestration Rules use the [Update the Service Orchestration active status for a Service API](https://developer.pagerduty.com/api-reference/855659be83d9e-update-the-service-orchestration-active-status-for-a-service). > ### End-of-life > Event Rules will end-of-life soon. We highly recommend that you use this API to [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.convert_service_event_rules_into_event_orchestration_rules

Full name

pagerduty.pagerduty_convert_service_event_rules_to_event_orchestration

Install an Add-on for your account. Addon's are pieces of functionality that developers can write to insert new functionality into PagerDuty's UI. Given a configuration containing a `src` parameter, that URL will be embedded in an `iframe` on a page that's available to users from a drop-down menu. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#add-ons) Scoped OAuth requires: `addons.write`

Lua path

app.integrations.pagerduty.install_add

Full name

pagerduty.pagerduty_create_addon

Create an Automation Action Create a Script, Process Automation, or Runbook Automation action

Lua path

app.integrations.pagerduty.create_automation_action

Full name

pagerduty.pagerduty_create_automation_action

Create an Invocation Invokes an Action

Lua path

app.integrations.pagerduty.create_invocation

Full name

pagerduty.pagerduty_create_automation_action_invocation

Associate an Automation Action with a service

Lua path

app.integrations.pagerduty.associate_automation_action_with_service

Full name

pagerduty.pagerduty_create_automation_action_service_assocation

Associate an Automation Action with a team

Lua path

app.integrations.pagerduty.associate_automation_action_with_team

Full name

pagerduty.pagerduty_create_automation_action_team_association

Create an Automation Action runner. Create a Process Automation or a Runbook Automation runner.

Lua path

app.integrations.pagerduty.create_automation_action_runner

Full name

pagerduty.pagerduty_create_automation_actions_runner

Associate a runner with a team

Lua path

app.integrations.pagerduty.associate_runner_with_team

Full name

pagerduty.pagerduty_create_automation_actions_runner_team_association

Create a Business Service Create a new Business Service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. There is a limit of 5,000 business services per account. If the limit is reached, the API will respond with an error. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.create_business_service

Full name

pagerduty.pagerduty_create_business_service

Create Business Service Account Subscription Subscribe your Account to a Business Service. Scoped OAuth requires: `subscribers.write`

Lua path

app.integrations.pagerduty.create_business_service_account_subscription

Full name

pagerduty.pagerduty_create_business_service_account_subscription

Create Business Service Subscribers Subscribe the given entities to the given Business Service. Scoped OAuth requires: `subscribers.write`

Lua path

app.integrations.pagerduty.create_business_service_subscribers

Full name

pagerduty.pagerduty_create_business_service_notification_subscribers

Create a Cache Variable for a Global Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.write`

Lua path

app.integrations.pagerduty.create_cache_variable_global_event_orchestration

Full name

pagerduty.pagerduty_create_cache_var_on_global_orch

Create a Cache Variable for a Service Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.create_cache_variable_service_event_orchestration

Full name

pagerduty.pagerduty_create_cache_var_on_service_orch

Create a Change Event Sending Change Events is documented as part of the V2 Events API. See [`Send Change Event`](https://developer.pagerduty.com/api-reference/b3A6Mjc0ODI2Ng-send-change-events-to-the-pager-duty-events-api).

Lua path

app.integrations.pagerduty.create_change_event

Full name

pagerduty.pagerduty_create_change_event

Create a Field <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields/post) Creates a new Custom Field on the Base Incident Type, along with the Field Options if provided. \ An account may have up to 10 Fields. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.create_field

Full name

pagerduty.pagerduty_create_custom_fields_field

Create a Field Option <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}~1field_options/post) Create a new Field Option for a Custom Field on the Base Incident Type. Field Options may only be created for Fields that have `field_options`. A Field may have no more than 10 enabled options. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.create_field_option

Full name

pagerduty.pagerduty_create_custom_fields_field_option

Create custom shifts <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Create one or more custom shifts for a schedule. Custom shifts are ad-hoc one-off coverage periods that exist outside of rotation events. Each custom shift requires exactly one assignment.

Lua path

app.integrations.pagerduty.create_custom_shifts

Full name

pagerduty.pagerduty_create_custom_shifts

Assign tags Assign existing or new tags. A Tag is applied to Escalation Policies, Teams or Users and can be used to filter them. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#tags) Scoped OAuth requires: `tags.write`

Lua path

app.integrations.pagerduty.assign_tags

Full name

pagerduty.pagerduty_create_entity_type_by_id_change_tags

Create an escalation policy Creates a new escalation policy. At least one escalation rule must be provided. Escalation policies define which user should be alerted at which time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#escalation-policies) Scoped OAuth requires: `escalation_policies.write`

Lua path

app.integrations.pagerduty.create_escalation_policy

Full name

pagerduty.pagerduty_create_escalation_policy

Create an event <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Create a new event that defines when and how users are on-call within a rotation. **Constraints:** - Maximum 5 events per rotation - Events within a rotation cannot overlap - `effective_since` must be in the future (past values are clamped to now) - All users referenced in `assignment_strategy.members` must exist and belong to the account

Lua path

app.integrations.pagerduty.create_event

Full name

pagerduty.pagerduty_create_event

Create an extension Create a new Extension. Extensions are representations of Extension Schema objects that are attached to Services. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extensions) Scoped OAuth requires: `extensions.write`

Lua path

app.integrations.pagerduty.create_extension

Full name

pagerduty.pagerduty_create_extension

Create an Incident Create an incident synchronously without a corresponding event from a monitoring service. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.write` This API operation has operation specific rate limits. See the [Rate Limits](https://developer.pagerduty.com/docs/72d3b724589e3-rest-api-rate-limits) page for more information.

Lua path

app.integrations.pagerduty.create_incident

Full name

pagerduty.pagerduty_create_incident

Create a note on an incident Create a new note for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. A maximum of 2000 notes can be added to an incident. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.write`

Lua path

app.integrations.pagerduty.create_note_incident

Full name

pagerduty.pagerduty_create_incident_note

Add Notification Subscribers Subscribe the given entities to Incident Status Update Notifications. Scoped OAuth requires: `subscribers.write`

Lua path

app.integrations.pagerduty.add_notification_subscribers

Full name

pagerduty.pagerduty_create_incident_notification_subscribers

Create a responder request for an incident Send a new responder request for the specified incident. This endpoint requires the account to have access to the [responder requests](https://support.pagerduty.com/main/docs/add-responders) feature. **Account Ability Requirement**: The account must have the `coordinated_responding` ability. Returns 402 Payment Required if the ability is missing. You can use the [List Abilities API](openapiv3.json/paths/~1abilities/get) to check account abilities. A user or an escalation policy can be requested. The responder targets will be notified via their high urgency notification rules, until the target user has either accepted or declined the request. Previous responder requests for a given target can be cancelled (preventing them from further notifying or escalating), with the [Cancel Responder Requests](openapiv3.json/paths/~1incidents~1{id}~1responder_requests~1cancel/put) endpoint. Scoped OAuth requires: `incidents.write`

Lua path

app.integrations.pagerduty.create_responder_request_incident

Full name

pagerduty.pagerduty_create_incident_responder_request

Snooze an incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.write`

Lua path

app.integrations.pagerduty.snooze_incident

Full name

pagerduty.pagerduty_create_incident_snooze

Create a status update on an incident Create a new status update for the specified incident. Optionally pass `subject` and `html_message` properties in the request body to override the email notification that gets sent. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.write`

Lua path

app.integrations.pagerduty.create_status_update_incident

Full name

pagerduty.pagerduty_create_incident_status_update

Create an Incident Type Create a new incident type. Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidentType) Scoped OAuth requires: `incident_types.write`

Lua path

app.integrations.pagerduty.create_incident_type

Full name

pagerduty.pagerduty_create_incident_type

Create a Custom Field for an Incident Type Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.create_custom_field_incident_type

Full name

pagerduty.pagerduty_create_incident_type_custom_field

Create a Field Option for a Custom Field Create a field option for a custom field. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.create_field_option_custom_field

Full name

pagerduty.pagerduty_create_incident_type_custom_field_field_options

Start an Incident Workflow Instance Start an Instance of an Incident Workflow. Sometimes referred to as "triggering a workflow on an incident." An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident. Scoped OAuth requires: `incident_workflows:instances.write`

Lua path

app.integrations.pagerduty.start_incident_workflow_instance

Full name

pagerduty.pagerduty_create_incident_workflow_instance

Create a Trigger Create new Incident Workflow Trigger Scoped OAuth requires: `incident_workflows.write`

Lua path

app.integrations.pagerduty.create_trigger

Full name

pagerduty.pagerduty_create_incident_workflow_trigger

Create a maintenance window Create a new maintenance window for the specified services. No new incidents will be created for a service that is in maintenance. A Maintenance Window is used to temporarily disable one or more Services for a set period of time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#maintenance-windows) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.create_maintenance_window

Full name

pagerduty.pagerduty_create_maintenance_window

Create an OAuth client Create a new OAuth client for webhook subscriptions. The client credentials will be validated by attempting to obtain an access token before creation. Requires admin or owner role permissions. Maximum of 10 OAuth clients per account.

Lua path

app.integrations.pagerduty.create_oauth_client

Full name

pagerduty.pagerduty_create_oauth_client

Create or Update a Post Postmortem Create or Update a Postmortem for a Post by Post ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.create_or_update_post_postmortem

Full name

pagerduty.pagerduty_create_or_update_status_page_postmortem

Create overrides <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Create one or more overrides for a schedule. An override temporarily replaces a scheduled on-call member with a different member for a specific time period. Each override must reference either a `rotation_id` or a `custom_shift_id` (not both). The overriding member must belong to the account. **Note:** The create response wraps the result in an `overrides` array. Single-resource endpoints (get, update) wrap in `override` (singular).

Lua path

app.integrations.pagerduty.create_overrides

Full name

pagerduty.pagerduty_create_overrides

Create a rotation <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Create a new empty rotation for a schedule. After creating a rotation, add events to define the on-call pattern. **Note:** Rotations have no configuration of their own - all scheduling logic (recurrence, assignment strategy, members) is specified on events. The request body must be empty or `{}`.

Lua path

app.integrations.pagerduty.create_rotation

Full name

pagerduty.pagerduty_create_rotation

Create a Ruleset Create a new Ruleset. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#rulesets) Scoped OAuth requires: `event_rules.write`

Lua path

app.integrations.pagerduty.create_ruleset

Full name

pagerduty.pagerduty_create_ruleset

Create an Event Rule Create a new Event Rule. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#rulesets) Note: Create and Update on rules will accept 'description' or 'summary' interchangeably as an extraction action target. Get and List on rules will always return 'summary' as the target. If you are expecting 'description' please change your automation code to expect 'summary' instead. Scoped OAuth requires: `event_rules.write`

Lua path

app.integrations.pagerduty.create_event_rule

Full name

pagerduty.pagerduty_create_ruleset_event_rule

Create a schedule Create a new on-call schedule. A Schedule determines the time periods that users are On-Call. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#schedules) Scoped OAuth requires: `schedules.write`

Lua path

app.integrations.pagerduty.create_schedule

Full name

pagerduty.pagerduty_create_schedule

Create one or more overrides, each for a specific user covering a specified time range. If you create an override on top of an existing override, the last created override will have priority. A Schedule determines the time periods that users are On-Call. Note: An older implementation of this endpoint only supported creating a single ocverride per request. That functionality is still supported, but deprecated and may be removed in the future. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#schedules) Scoped OAuth requires: `schedules.write`

Lua path

app.integrations.pagerduty.create_one_or_more_overrides

Full name

pagerduty.pagerduty_create_schedule_override

Preview a schedule Preview what an on-call schedule would look like without saving it. A Schedule determines the time periods that users are On-Call. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#schedules) Scoped OAuth requires: `schedules.write`

Lua path

app.integrations.pagerduty.preview_schedule

Full name

pagerduty.pagerduty_create_schedule_preview

Create a schedule <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Create a new on-call schedule with basic metadata. Rotations and events must be added via separate API calls after creation. **Rejected fields:** `rotations` and `escalation_policies` are not accepted in the request body and will result in a 400 error.

Lua path

app.integrations.pagerduty.create_schedule

Full name

pagerduty.pagerduty_create_schedule_v3

Create a service Create a new service. If `status` is included in the request, it must have a value of `active` when creating a new service. If a different status is required, make a second request to update the service. A service may represent an application, component, or team you wish to open incidents against. There is a limit of 25,000 services per account. If the limit is reached, the API will respond with an error. There is also a limit of 100,000 open Incidents per Service. If the limit is reached and `auto_resolve_timeout` is disabled (set to 0 or null), the `auto_resolve_timeout` property will automatically be set to 84600 (1 day). For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.create_service

Full name

pagerduty.pagerduty_create_service

Create a Field Creates a new Custom Field for Services, along with the Field Options if provided. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.create_field

Full name

pagerduty.pagerduty_create_service_custom_field

Create a Field Option Create a new option for the given field. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.create_field_option

Full name

pagerduty.pagerduty_create_service_custom_field_option

Associate service dependencies Create new dependencies between two services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. A service can have a maximum of 2,000 dependencies with a depth limit of 100. If the limit is reached, the API will respond with an error. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.associate_service_dependencies

Full name

pagerduty.pagerduty_create_service_dependency

Create an Event Rule on a Service Create a new Event Rule on a Service. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.create_event_rule_service

Full name

pagerduty.pagerduty_create_service_event_rule

Create a new integration belonging to a Service. A service may represent an application, component, or team you wish to open incidents against. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.create_new_integration

Full name

pagerduty.pagerduty_create_service_integration

Create a Status Page Post Create a Post for a Status Page by Status Page ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.create_status_post

Full name

pagerduty.pagerduty_create_status_page_post

Create a Status Page Post Update Create a Post Update for a Post by Post ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.create_status_post_update

Full name

pagerduty.pagerduty_create_status_page_post_update

Create a Status Page Subscription Create a Subscription for a Status Page by Status Page ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.create_status_subscription

Full name

pagerduty.pagerduty_create_status_page_subscription

Create a tag Create a Tag. A Tag is applied to Escalation Policies, Teams or Users and can be used to filter them. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#tags) Scoped OAuth requires: `tags.write`

Lua path

app.integrations.pagerduty.create_tag

Full name

pagerduty.pagerduty_create_tags

Create a team Create a new Team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#teams) Scoped OAuth requires: `teams.write`

Lua path

app.integrations.pagerduty.create_team

Full name

pagerduty.pagerduty_create_team

Create Team Notification Subscriptions Create new Notification Subscriptions for the given Team. Scoped OAuth requires: `subscribers.write`

Lua path

app.integrations.pagerduty.create_team_notification_subscriptions

Full name

pagerduty.pagerduty_create_team_notification_subscriptions

Create a template Create a new template Scoped OAuth requires: `templates.write`

Lua path

app.integrations.pagerduty.create_template

Full name

pagerduty.pagerduty_create_template

Create a user Create a new user. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.write`

Lua path

app.integrations.pagerduty.create_user

Full name

pagerduty.pagerduty_create_user

Create a user contact method Create a new contact method for the User. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.write`

Lua path

app.integrations.pagerduty.create_user_contact_method

Full name

pagerduty.pagerduty_create_user_contact_method

Create a User Handoff Notification Rule Create a new Handoff Notification Rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.write`

Lua path

app.integrations.pagerduty.create_user_handoff_notification_rule

Full name

pagerduty.pagerduty_create_user_handoff_notification_rule

Create a user notification rule Create a new notification rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.write`

Lua path

app.integrations.pagerduty.create_user_notification_rule

Full name

pagerduty.pagerduty_create_user_notification_rule

Create Notification Subcriptions Create new Notification Subscriptions for the given User. Scoped OAuth requires: `subscribers.write`

Lua path

app.integrations.pagerduty.create_notification_subcriptions

Full name

pagerduty.pagerduty_create_user_notification_subscriptions

Create a user status update notification rule Create a new status update notification rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.write`

Lua path

app.integrations.pagerduty.create_user_status_update_notification_rule

Full name

pagerduty.pagerduty_create_user_status_update_notification_rule

Create a webhook subscription Creates a new webhook subscription. For more information on webhook subscriptions and how they are used to configure v3 webhooks see the [Webhooks v3 Developer Documentation](https://developer.pagerduty.com/docs/webhooks/v3-overview/). Scoped OAuth requires: `webhook_subscriptions.write`

Lua path

app.integrations.pagerduty.create_webhook_subscription

Full name

pagerduty.pagerduty_create_webhook_subscription

Create Workflow Integration Connection Create a new Workflow Integration Connection. Scoped OAuth requires: `workflow_integrations:connections.write`

Lua path

app.integrations.pagerduty.create_workflow_integration_connection

Full name

pagerduty.pagerduty_create_workflow_integration_connection

Delete an Add-on Remove an existing Add-on. Addon's are pieces of functionality that developers can write to insert new functionality into PagerDuty's UI. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#add-ons) Scoped OAuth requires: `addons.write`

Lua path

app.integrations.pagerduty.delete_add

Full name

pagerduty.pagerduty_delete_addon

Delete an Alert Grouping Setting Delete an existing Alert Grouping Setting. The settings part of Alert Grouper service allows us to create Alert Grouping Settings and configs that are required to be used during grouping of the alerts. Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_alert_grouping_setting

Full name

pagerduty.pagerduty_delete_alert_grouping_setting

Delete an Automation Action

Lua path

app.integrations.pagerduty.delete_automation_action

Full name

pagerduty.pagerduty_delete_automation_action

Disassociate an Automation Action from a service

Lua path

app.integrations.pagerduty.disassociate_automation_action_from_service

Full name

pagerduty.pagerduty_delete_automation_action_service_association

Disassociate an Automation Action from a team

Lua path

app.integrations.pagerduty.disassociate_automation_action_from_team

Full name

pagerduty.pagerduty_delete_automation_action_team_association

Delete an Automation Action runner

Lua path

app.integrations.pagerduty.delete_automation_action_runner

Full name

pagerduty.pagerduty_delete_automation_actions_runner

Disassociate a runner from a team Disassociates a runner from a team

Lua path

app.integrations.pagerduty.disassociate_runner_from_team

Full name

pagerduty.pagerduty_delete_automation_actions_runner_team_association

Delete a Business Service Delete an existing Business Service. Once the service is deleted, it will not be accessible from the web UI and new incidents won't be able to be created for this service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_business_service

Full name

pagerduty.pagerduty_delete_business_service

Deletes the account-level priority threshold for Business Service impact Clears the Priority Threshold for the account. If the priority threshold is cleared, any Incident with a Priority set will be able to impact Business Services. Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.deletes_account_level_priority_threshold_business_service_impact

Full name

pagerduty.pagerduty_delete_business_service_priority_thresholds

Delete a Cache Variable for a Global Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.write`

Lua path

app.integrations.pagerduty.delete_cache_variable_global_event_orchestration

Full name

pagerduty.pagerduty_delete_cache_var_on_global_orch

Delete a Cache Variable for a Service Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_cache_variable_service_event_orchestration

Full name

pagerduty.pagerduty_delete_cache_var_on_service_orch

Delete a Field <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields/{field_id}](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}/delete) Delete a Custom Field from the Base Incident Type. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.delete_field

Full name

pagerduty.pagerduty_delete_custom_fields_field

Delete a Field Option <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options/{field_option_id}](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}~1field_options~1{field_option_id}/delete) Delete a Field Option for a Custom Field on the Base Incident Type. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.delete_field_option

Full name

pagerduty.pagerduty_delete_custom_fields_field_option

Delete a custom shift <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Delete a custom shift by ID. When the shift is not started, it deletes the shift entirely. If the shift is already started, it sets the end_time to now. It returns Bad Request when shift is already ended.

Lua path

app.integrations.pagerduty.delete_custom_shift

Full name

pagerduty.pagerduty_delete_custom_shift

Delete an escalation policy Deletes an existing escalation policy and rules. The escalation policy must not be in use by any services. Escalation policies define which user should be alerted at which time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#escalation-policies) Scoped OAuth requires: `escalation_policies.write`

Lua path

app.integrations.pagerduty.delete_escalation_policy

Full name

pagerduty.pagerduty_delete_escalation_policy

Delete an event <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Delete an event from a rotation.

Lua path

app.integrations.pagerduty.delete_event

Full name

pagerduty.pagerduty_delete_event

Delete an extension Delete an existing extension. Once the extension is deleted, it will not be accessible from the web UI and new incidents won't be able to be created for this extension. Extensions are representations of Extension Schema objects that are attached to Services. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extensions) Scoped OAuth requires: `extensions.write`

Lua path

app.integrations.pagerduty.delete_extension

Full name

pagerduty.pagerduty_delete_extension

Delete Data for an External Data Cache Variable on a Global Event Orchestration Delete data for an `external_data` type Cache Variable on a Global Event Orchestration Use External Data type Cache Variables to store string, number, or boolean values via a dedicated API endpoint. These stored values can then be used in conditions or actions in Event Orchestration rules. For more information see the [Knowledge Base](https://support.pagerduty.com/main/docs/event-orchestration-cache-variables) Scoped OAuth requires: `event_orchestrations.write`

Lua path

app.integrations.pagerduty.delete_data_external_data_cache_variable_global_event_orchestration

Full name

pagerduty.pagerduty_delete_external_data_cache_var_data_on_global_orch

Delete Data for an External Data Cache Variable on a Service Event Orchestration Delete Data for an `external_data` type Cache Variable on a Service Event Orchestration. Use External Data type Cache Variables to store string, number, or boolean values via a dedicated API endpoint. These stored values can then be used in conditions or actions in Event Orchestration rules. For more information see the [Knowledge Base](https://support.pagerduty.com/main/docs/event-orchestration-cache-variables) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_data_external_data_cache_variable_service_event_orchestration

Full name

pagerduty.pagerduty_delete_external_data_cache_var_data_on_service_orch

Delete a note on an incident Delete an existing note for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.write`

Lua path

app.integrations.pagerduty.delete_note_incident

Full name

pagerduty.pagerduty_delete_incident_note

Delete a Custom Field for an Incident Type Delete a custom field for an incident type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.delete_custom_field_incident_type

Full name

pagerduty.pagerduty_delete_incident_type_custom_field

Delete a Field Option for a Custom Field Delete a field option for a custom field. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.delete_field_option_custom_field

Full name

pagerduty.pagerduty_delete_incident_type_custom_field_field_option

Delete an Incident Workflow Delete an existing Incident Workflow An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident. Scoped OAuth requires: `incident_workflows.write`

Lua path

app.integrations.pagerduty.delete_incident_workflow

Full name

pagerduty.pagerduty_delete_incident_workflow

Delete a Trigger Delete an existing Incident Workflow Trigger Scoped OAuth requires: `incident_workflows.write`

Lua path

app.integrations.pagerduty.delete_trigger

Full name

pagerduty.pagerduty_delete_incident_workflow_trigger

Delete or end a maintenance window Delete an existing maintenance window if it's in the future, or end it if it's currently on-going. If the maintenance window has already ended it cannot be deleted. A Maintenance Window is used to temporarily disable one or more Services for a set period of time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#maintenance-windows) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_or_end_maintenance_window

Full name

pagerduty.pagerduty_delete_maintenance_window

Delete an OAuth client. This will also remove the OAuth client association from any webhook subscriptions using it. Requires admin or owner role permissions.

Lua path

app.integrations.pagerduty.delete_oauth_client

Full name

pagerduty.pagerduty_delete_oauth_client

Delete all OAuth delegations as per provided query parameters. An OAuth delegation represents an instance of a user or account's authorization to an app (via OAuth) to access their PagerDuty account. Common apps include the PagerDuty mobile app, Slack, Microsoft Teams, and third-party apps. It also represents a user session in the PagerDuty web app. Deleting an OAuth delegation will revoke that instance of an app's access to that user or account. To grant access again, reauthorization/reauthentication will be required. This endpoint supports deleting mobile app OAuth delegations for a given user, which is equivalent to signing users out of the mobile app. It also supports deleting delegations of type web, which is equivalent to signing users out of the web app. This is a synchronous API. Scoped OAuth requires: `oauth_delegations.write`

Lua path

app.integrations.pagerduty.delete_all_oauth_delegations

Full name

pagerduty.pagerduty_delete_oauth_delegations

Delete an Orchestration Delete a Global Event Orchestration. Once deleted, you will no longer be able to ingest events into PagerDuty using this Orchestration's Routing Key. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.write`

Lua path

app.integrations.pagerduty.delete_orchestration

Full name

pagerduty.pagerduty_delete_orchestration

Delete an Integration for an Event Orchestration Delete an Integration and its associated Routing Key. Once deleted, PagerDuty will drop all future events sent to PagerDuty using the Routing Key. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.write`

Lua path

app.integrations.pagerduty.delete_integration_event_orchestration

Full name

pagerduty.pagerduty_delete_orchestration_integration

Delete an override <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Delete an override by ID.

Lua path

app.integrations.pagerduty.delete_override

Full name

pagerduty.pagerduty_delete_override

Delete a rotation <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Delete a rotation and all its events. On deletion, past events are preserved in the audit history, the current active event is truncated to the deletion time, and future events are removed.

Lua path

app.integrations.pagerduty.delete_rotation

Full name

pagerduty.pagerduty_delete_rotation

Delete a Ruleset. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#rulesets) Scoped OAuth requires: `event_rules.write`

Lua path

app.integrations.pagerduty.delete_ruleset

Full name

pagerduty.pagerduty_delete_ruleset

Delete an Event Rule. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#rulesets) Scoped OAuth requires: `event_rules.write`

Lua path

app.integrations.pagerduty.delete_event_rule

Full name

pagerduty.pagerduty_delete_ruleset_event_rule

Delete a schedule Delete an on-call schedule. A Schedule determines the time periods that users are On-Call. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#schedules) Scoped OAuth requires: `schedules.write`

Lua path

app.integrations.pagerduty.delete_schedule

Full name

pagerduty.pagerduty_delete_schedule

Delete an override Remove an override. You cannot remove a past override. If the override start time is before the current time, but the end time is after the current time, the override will be truncated to the current time. If the override is truncated, the status code will be 200 OK, as opposed to a 204 No Content for a successful delete. A Schedule determines the time periods that users are On-Call. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#schedules) Scoped OAuth requires: `schedules.write`

Lua path

app.integrations.pagerduty.delete_override

Full name

pagerduty.pagerduty_delete_schedule_override

Delete a schedule <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Delete a schedule and all associated rotations and events. If the schedule is referenced by an active escalation policy, the deletion will be rejected.

Lua path

app.integrations.pagerduty.delete_schedule

Full name

pagerduty.pagerduty_delete_schedule_v3

Delete a service Delete an existing service. Once the service is deleted, it will not be accessible from the web UI and new incidents won't be able to be created for this service. A service may represent an application, component, or team you wish to open incidents against. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_service

Full name

pagerduty.pagerduty_delete_service

Delete a Field Delete a Custom Field from Services. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.delete_field

Full name

pagerduty.pagerduty_delete_service_custom_field

Delete a Field Option Delete a field option. Scoped OAuth requires: `custom_fields.write`

Lua path

app.integrations.pagerduty.delete_field_option

Full name

pagerduty.pagerduty_delete_service_custom_field_option

Disassociate service dependencies Disassociate dependencies between two services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.disassociate_service_dependencies

Full name

pagerduty.pagerduty_delete_service_dependency

Delete an Event Rule from a Service. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Scoped OAuth requires: `services.write`

Lua path

app.integrations.pagerduty.delete_event_rule_from_service

Full name

pagerduty.pagerduty_delete_service_event_rule

Dissociate a Trigger and Service Remove a an existing Service from an Incident Workflow Trigger Scoped OAuth requires: `incident_workflows.write`

Lua path

app.integrations.pagerduty.dissociate_trigger_and_service

Full name

pagerduty.pagerduty_delete_service_from_incident_workflow_trigger

Delete an account's session configurations. Deletes the session configurations for a PagerDuty account that was previously set. The type parameter is required and specifies which configurations to delete. A single type ('mobile' or 'web') or comma-separated list may be passed in. Scoped OAuth requires: `session_configurations.write`

Lua path

app.integrations.pagerduty.delete_account_session_configurations

Full name

pagerduty.pagerduty_delete_session_configurations

Delete an SRE Agent memory Permanently delete an SRE Agent memory. Scoped OAuth requires: `sre_agent.write`

Lua path

app.integrations.pagerduty.delete_sre_agent_memory

Full name

pagerduty.pagerduty_delete_sre_memory

Delete a Status Page Post Delete a Post for a Status Page by Status Page ID and Post ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.delete_status_post

Full name

pagerduty.pagerduty_delete_status_page_post

Delete a Status Page Post Update Delete a Post Update for a Post by Post ID and Post Update ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.delete_status_post_update

Full name

pagerduty.pagerduty_delete_status_page_post_update

Delete a Post Postmortem Delete a Postmortem for a Post by Post ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.delete_post_postmortem

Full name

pagerduty.pagerduty_delete_status_page_postmortem

Delete a Status Page Subscription Delete a Subscription for a Status Page by Status Page ID and Subscription ID. Scoped OAuth requires: `status_pages.write`

Lua path

app.integrations.pagerduty.delete_status_subscription

Full name

pagerduty.pagerduty_delete_status_page_subscription

Delete a tag Remove an existing Tag. A Tag is applied to Escalation Policies, Teams or Users and can be used to filter them. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#tags) Scoped OAuth requires: `tags.write`

Lua path

app.integrations.pagerduty.delete_tag

Full name

pagerduty.pagerduty_delete_tag

Delete a team Remove an existing team. Succeeds only if the team has no associated Escalation Policies, Services, Schedules and Subteams. All associated unresovled incidents will be reassigned to another team (if specified) or will loose team association, thus becoming account-level (with visibility implications). Note that the incidents reassignment process is asynchronous and has no guarantee to complete before the API call return. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#teams) Scoped OAuth requires: `teams.write`

Lua path

app.integrations.pagerduty.delete_team

Full name

pagerduty.pagerduty_delete_team

Remove an escalation policy from a team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#teams) Scoped OAuth requires: `teams.write`

Lua path

app.integrations.pagerduty.remove_escalation_policy_from_team

Full name

pagerduty.pagerduty_delete_team_escalation_policy

Remove a user from a team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#teams) Scoped OAuth requires: `teams.write`

Lua path

app.integrations.pagerduty.remove_user_from_team

Full name

pagerduty.pagerduty_delete_team_user

Delete a template Delete a specific of templates on the account Scoped OAuth requires: `templates.write`

Lua path

app.integrations.pagerduty.delete_template

Full name

pagerduty.pagerduty_delete_template

Delete a user Remove an existing user. Returns 400 if the user has assigned incidents unless your [pricing plan](https://www.pagerduty.com/pricing) has the `offboarding` feature and the account is [configured](https://support.pagerduty.com/docs/offboarding#section-additional-configurations) appropriately. Note that the incidents reassignment process is asynchronous and has no guarantee to complete before the api call return. [*Learn more about `offboarding` feature*](https://support.pagerduty.com/docs/offboarding). Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.write`

Lua path

app.integrations.pagerduty.delete_user

Full name

pagerduty.pagerduty_delete_user

Delete a user's contact method Remove a user's contact method. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.write`

Lua path

app.integrations.pagerduty.delete_user_contact_method

Full name

pagerduty.pagerduty_delete_user_contact_method

Delete a User's Handoff Notification rule Remove a User's Handoff Notification Rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.write`

Lua path

app.integrations.pagerduty.delete_user_handoff_notification_rule

Full name

pagerduty.pagerduty_delete_user_handoff_notification_rule

Delete a user's notification rule Remove a user's notification rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.write`

Lua path

app.integrations.pagerduty.delete_user_notification_rule

Full name

pagerduty.pagerduty_delete_user_notification_rule

Delete a user's session <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated as OAuth token revocation is now synchronous. Please use the [DELETE /oauth_delegations endpoint](https://developer.pagerduty.com/api-reference/ad1161db75db1-delete-all-o-auth-delegations) instead. Delete a user's session. Beginning November 2021, user sessions no longer includes newly issued OAuth tokens. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:sessions.write`

Lua path

app.integrations.pagerduty.delete_user_session

Full name

pagerduty.pagerduty_delete_user_session

Delete all user sessions <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated as OAuth token revocation is now synchronous. Please use the [DELETE /oauth_delegations endpoint](https://developer.pagerduty.com/api-reference/ad1161db75db1-delete-all-o-auth-delegations) instead. Delete all user sessions. Beginning November 2021, user sessions no longer includes newly issued OAuth tokens. If you are interested in deleting mobile app sessions, refer to the Delete OAuth Delegations endpoint. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:sessions.write`

Lua path

app.integrations.pagerduty.delete_all_user_sessions

Full name

pagerduty.pagerduty_delete_user_sessions

Delete a user's status update notification rule Remove a user's status update notification rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.write`

Lua path

app.integrations.pagerduty.delete_user_status_update_notification_rule

Full name

pagerduty.pagerduty_delete_user_status_update_notification_rule

Delete a webhook subscription Deletes a webhook subscription. Scoped OAuth requires: `webhook_subscriptions.write`

Lua path

app.integrations.pagerduty.delete_webhook_subscription

Full name

pagerduty.pagerduty_delete_webhook_subscription

Delete Workflow Integration Connection Delete a Workflow Integration Connection. Scoped OAuth requires: `workflow_integrations:connections.write`

Lua path

app.integrations.pagerduty.delete_workflow_integration_connection

Full name

pagerduty.pagerduty_delete_workflow_integration_connection

Enable an extension that is temporarily disabled. (This API does not require a request body.) Extensions are representations of Extension Schema objects that are attached to Services. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extensions) Scoped OAuth requires: `extensions.write`

Lua path

app.integrations.pagerduty.enable_extension

Full name

pagerduty.pagerduty_enable_extension

Enable a webhook subscription that is temporarily disabled. (This API does not require a request body.) Webhook subscriptions can become temporarily disabled when the subscription's delivery method is repeatedly rejected by the server. Scoped OAuth requires: `webhook_subscriptions.write`

Lua path

app.integrations.pagerduty.enable_webhook_subscription

Full name

pagerduty.pagerduty_enable_webhook_subscription

Test an ability Test whether your account has a given ability. "Abilities" describes your account's capabilities by feature name. For example `"teams"`. An ability may be available to your account based on things like your pricing plan or account state. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#abilities) Scoped OAuth requires: `abilities.read`

Lua path

app.integrations.pagerduty.test_ability

Full name

pagerduty.pagerduty_get_ability

Get an Add-on Get details about an existing Add-on. Addon's are pieces of functionality that developers can write to insert new functionality into PagerDuty's UI. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#add-ons) Scoped OAuth requires: `addons.read`

Lua path

app.integrations.pagerduty.get_add

Full name

pagerduty.pagerduty_get_addon

Get an Alert Grouping Setting Get an existing Alert Grouping Setting. The settings part of Alert Grouper service allows us to create Alert Grouping Settings and configs that are required to be used during grouping of the alerts. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_alert_grouping_setting

Full name

pagerduty.pagerduty_get_alert_grouping_setting

List Automation Actions Lists Automation Actions matching provided query params. The returned records are sorted by action name in alphabetical order. See [`Cursor-based pagination`](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for instructions on how to paginate through the result set.

Lua path

app.integrations.pagerduty.list_automation_actions

Full name

pagerduty.pagerduty_get_all_automation_actions

Get raw responses from a single incident Provides enriched responder data for a single incident. Example metrics include Time to Respond, Responder Type, and Response Status. See metric definitions below. <!-- theme: info --> > **Note:** Analytics data is updated once per day. It takes up to 24 hours before new incident responses appear in the Analytics API. Scoped OAuth requires: `analytics.read`

Lua path

app.integrations.pagerduty.get_raw_responses_from_single_incident

Full name

pagerduty.pagerduty_get_analytics_incident_responses_by_id

Get raw data - multiple incidents Provides enriched incident data and metrics for multiple incidents. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#incidents-list). <!-- theme: info --> > A `team_ids` or `service_ids` filter is required for [user-level API keys](https://support.pagerduty.com/docs/using-the-api#section-generating-a-personal-rest-api-key) or keys generated through an OAuth flow. Account-level API keys do not have this requirement. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_raw_data_multiple_incidents

Full name

pagerduty.pagerduty_get_analytics_incidents

Get raw data - single incident Provides enriched incident data and metrics for a single incident. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#incidents-list). <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.read`

Lua path

app.integrations.pagerduty.get_raw_data_single_incident

Full name

pagerduty.pagerduty_get_analytics_incidents_by_id

Get aggregated incident data Provides aggregated enriched metrics for incidents. The provided metrics are aggregated by day, week, month using the aggregate_unit parameter, or for the entire period if no aggregate_unit is provided. <!-- theme: info --> > A `team_ids` or `service_ids` filter is required for [user-level API keys](https://support.pagerduty.com/docs/using-the-api#section-generating-a-personal-rest-api-key) or keys generated through an OAuth flow. Account-level API keys do not have this requirement. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_incident_data

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_all

Get aggregated escalation policy data Provides aggregated metrics for incidents aggregated into units of time by escalation policy. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#escalation-policy-list). <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_escalation_policy_data

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_escalation_policy

Get aggregated metrics for all escalation policies Provides aggregated metrics across all escalation policies. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#escalation-policy-list). <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_metrics_all_escalation_policies

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_escalation_policy_all

Get aggregated service data Provides aggregated metrics for incidents aggregated into units of time by service. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#services-list). Data can be aggregated by day, week or month in addition to by service, or provided just as a collection of aggregates for each service in the dataset for the entire period. If a unit is provided, each row in the returned dataset will include a 'range_start' timestamp. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_service_data

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_service

Get aggregated metrics for all services Provides aggregated metrics across all services. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#services-list). <!-- theme: info --> > A `team_ids` or `service_ids` filter is required for [user-level API keys](https://support.pagerduty.com/docs/using-the-api#section-generating-a-personal-rest-api-key) or keys generated through an OAuth flow. Account-level API keys do not have this requirement. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_metrics_all_services

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_service_all

Get aggregated team data Provides aggregated metrics for incidents aggregated into units of time by team. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#teams-list). Data can be aggregated by day, week or month in addition to by team, or provided just as a collection of aggregates for each team in the dataset for the entire period. If a unit is provided, each row in the returned dataset will include a 'range_start' timestamp. <!-- theme: info --> > A `team_ids` or `service_ids` filter is required for [user-level API keys](https://support.pagerduty.com/docs/using-the-api#section-generating-a-personal-rest-api-key) or keys generated through an OAuth flow. Account-level API keys do not have this requirement. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_team_data

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_team

Get aggregated metrics for all teams Provides aggregated metrics across all teams. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#teams-list). <!-- theme: info --> > A `team_ids` or `service_ids` filter is required for [user-level API keys](https://support.pagerduty.com/docs/using-the-api#section-generating-a-personal-rest-api-key) or keys generated through an OAuth flow. Account-level API keys do not have this requirement. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_metrics_all_teams

Full name

pagerduty.pagerduty_get_analytics_metrics_incidents_team_all

Get aggregated PD Advance usage data Provides aggregated metrics for the usage of PD Advance. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_pd_advance_usage_data

Full name

pagerduty.pagerduty_get_analytics_metrics_pd_advance_usage_features

Get aggregated metrics for all responders Provides aggregated incident metrics for all selected responders. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#responders-list). <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_metrics_all_responders

Full name

pagerduty.pagerduty_get_analytics_metrics_responders_all

Get responder data aggregated by team Provides incident metrics aggregated by responder. Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#responders-list). <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_responder_data_aggregated_by_team

Full name

pagerduty.pagerduty_get_analytics_metrics_responders_team

Get aggregated metrics for all users Provides aggregated metrics across all users within their account. This endpoint provides summary statistics about user activity and performance. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_aggregated_metrics_all_users

Full name

pagerduty.pagerduty_get_analytics_metrics_users_all

Get raw incidents for a single responder_id Provides enriched incident data and metrics for a specific responder. Example metrics include Mean Seconds to Resolve, Mean Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https://support.pagerduty.com/docs/insights#incidents-list). <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new incidents appear in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_raw_incidents_single_responder_id

Full name

pagerduty.pagerduty_get_analytics_responder_incidents

Get raw user analytics data Allows users to retrieve a raw list of user analytics data within their account. This endpoint provides detailed data about user activity and account configuration. <!-- theme: info --> > **Note:** Analytics data is updated [periodically](https://support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule). It takes up to 24 hours before new user data appears in the Analytics API. Scoped OAuth requires: `analytics.write`

Lua path

app.integrations.pagerduty.get_raw_user_analytics_data

Full name

pagerduty.pagerduty_get_analytics_users

Get an Automation Action

Lua path

app.integrations.pagerduty.get_automation_action

Full name

pagerduty.pagerduty_get_automation_action

Get the details of an Automation Action / service relation Gets the details of a Automation Action / service relation

Lua path

app.integrations.pagerduty.get_details_automation_action_service_relation

Full name

pagerduty.pagerduty_get_automation_actions_action_service_association

Get all service references associated with an Automation Action Gets all service references associated with an Automation Action

Lua path

app.integrations.pagerduty.get_all_service_references_associated_with_automation_action

Full name

pagerduty.pagerduty_get_automation_actions_action_service_associations

Get the details of an Automation Action / team relation Gets the details of an Automation Action / team relation

Lua path

app.integrations.pagerduty.get_details_automation_action_team_relation

Full name

pagerduty.pagerduty_get_automation_actions_action_team_association

Get all team references associated with an Automation Action Gets all team references associated with an Automation Action

Lua path

app.integrations.pagerduty.get_all_team_references_associated_with_automation_action

Full name

pagerduty.pagerduty_get_automation_actions_action_team_associations

Get an Invocation Get an Automation Action Invocation

Lua path

app.integrations.pagerduty.get_invocation

Full name

pagerduty.pagerduty_get_automation_actions_invocation

Get an Automation Action runner

Lua path

app.integrations.pagerduty.get_automation_action_runner

Full name

pagerduty.pagerduty_get_automation_actions_runner

Get the details of a runner / team relation Gets the details of a runner / team relation

Lua path

app.integrations.pagerduty.get_details_runner_team_relation

Full name

pagerduty.pagerduty_get_automation_actions_runner_team_association

Get all team references associated with a runner Gets all team references associated with a runner

Lua path

app.integrations.pagerduty.get_all_team_references_associated_with_runner

Full name

pagerduty.pagerduty_get_automation_actions_runner_team_associations

List Automation Action runners Lists Automation Action runners matching provided query params. The returned records are sorted by runner name in alphabetical order. See [`Cursor-based pagination`](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for instructions on how to paginate through the result set.

Lua path

app.integrations.pagerduty.list_automation_action_runners

Full name

pagerduty.pagerduty_get_automation_actions_runners

Get a Business Service Get details about an existing Business Service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_business_service

Full name

pagerduty.pagerduty_get_business_service

List Business Services sorted by impacted status Retrieve a list top-level Business Services sorted by highest Impact with `status` included. When called without the `ids[]` parameter, this endpoint does not return an exhaustive list of Business Services but rather provides access to the most impacted up to the limit of 200. The returned Business Services are sorted first by Impact, secondarily by most recently impacted, and finally by name. To get impact information about a specific set of Business Services, use the `ids[]` parameter. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.list_business_services_sorted_by_impacted_status

Full name

pagerduty.pagerduty_get_business_service_impacts

Get the global priority threshold for a Business Service to be considered impacted by an Incident Retrieves the priority threshold information for an account. Currently, there is a `global_threshold` that can be set for the account. Incidents that have a priority meeting or exceeding this threshold will be considered impacting on any Business Service that depends on the Service to which the Incident belongs. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_global_priority_threshold_business_service_be_considered_impacted_by_incident

Full name

pagerduty.pagerduty_get_business_service_priority_thresholds

Get Business Service dependencies Get all immediate dependencies of any Business Service. Business Services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_business_service_dependencies

Full name

pagerduty.pagerduty_get_business_service_service_dependencies

List Business Service Subscribers Retrieve a list of Notification Subscribers on the Business Service. <!-- theme: warning --> > Users must be added through `POST /business_services/{id}/subscribers` to be returned from this endpoint. Scoped OAuth requires: `subscribers.read`

Lua path

app.integrations.pagerduty.list_business_service_subscribers

Full name

pagerduty.pagerduty_get_business_service_subscribers

List the supporting Business Services for the given Business Service Id, sorted by impacted status. Retrieve of Business Services that support the given Business Service sorted by highest Impact with `status` included. This endpoint does not return an exhaustive list of Business Services but rather provides access to the most impacted up to the limit of 200. The returned Business Services are sorted first by Impact, secondarily by most recently impacted, and finally by name. To get impact information about a specific set of Business Services, use the `ids[]` parameter on the `/business_services/impacts` endpoint. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.list_supporting_business_services_given_business_service_id_sorted_by_impacted_status

Full name

pagerduty.pagerduty_get_business_service_supporting_service_impacts

List Impactors affecting Business Services Retrieve a list of Impactors for the top-level Business Services on the account. Impactors are currently limited to Incidents. This endpoint does not return an exhaustive list of Impactors but rather provides access to the highest priority Impactors for the Business Services in question up to the limit of 200. To get Impactors for a specific set of Business Services, use the `ids[]` parameter. The returned Impactors are sorted first by priority and secondarily by their creation date. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.list_impactors_affecting_business_services

Full name

pagerduty.pagerduty_get_business_service_top_level_impactors

Get a Cache Variable for a Global Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_cache_variable_global_event_orchestration

Full name

pagerduty.pagerduty_get_cache_var_on_global_orch

Get a Cache Variable for a Service Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_cache_variable_service_event_orchestration

Full name

pagerduty.pagerduty_get_cache_var_on_service_orch

Get a Change Event Get details about an existing Change Event. Scoped OAuth requires: `change_events.read`

Lua path

app.integrations.pagerduty.get_change_event

Full name

pagerduty.pagerduty_get_change_event

Get the current user Get details about the current user. This endpoint can only be used with a [user-level API key](https://support.pagerduty.com/docs/using-the-api#section-generating-a-personal-rest-api-key) or a key generated through an OAuth flow. This will not work if the request is made with an account-level access token. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users)

Lua path

app.integrations.pagerduty.get_current_user

Full name

pagerduty.pagerduty_get_current_user

Get a Field <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields/{field_id}](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}/get) Show detailed information about a Custom Field on the Base Incident Type. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.get_field

Full name

pagerduty.pagerduty_get_custom_fields_field

Get a custom shift <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve a single custom shift by ID.

Lua path

app.integrations.pagerduty.get_custom_shift

Full name

pagerduty.pagerduty_get_custom_shift

Get tags for entities Get related tags for Users, Teams or Escalation Policies. A Tag is applied to Escalation Policies, Teams or Users and can be used to filter them. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#tags) Scoped OAuth requires: `tags.read`

Lua path

app.integrations.pagerduty.get_tags_entities

Full name

pagerduty.pagerduty_get_entity_type_by_id_tags

Get an escalation policy Get information about an existing escalation policy and its rules. Escalation policies define which user should be alerted at which time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#escalation-policies) Scoped OAuth requires: `escalation_policies.read`

Lua path

app.integrations.pagerduty.get_escalation_policy

Full name

pagerduty.pagerduty_get_escalation_policy

Get an event <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve a specific event by ID.

Lua path

app.integrations.pagerduty.get_event

Full name

pagerduty.pagerduty_get_event

Get an extension Get details about an existing extension. Extensions are representations of Extension Schema objects that are attached to Services. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extensions) Scoped OAuth requires: `extensions.read`

Lua path

app.integrations.pagerduty.get_extension

Full name

pagerduty.pagerduty_get_extension

Get an extension vendor Get details about one specific extension vendor. A PagerDuty extension vendor represents a specific type of outbound extension such as Generic Webhook, Slack, ServiceNow. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extension-schemas) Scoped OAuth requires: `extension_schemas.read`

Lua path

app.integrations.pagerduty.get_extension_vendor

Full name

pagerduty.pagerduty_get_extension_schema

Get Data for an External Data Cache Variable on a Global Event Orchestration Get the data for an `external_data` type Cache Variable on a Global Orchestration. Use External Data type Cache Variables to store string, number, or boolean values via a dedicated API endpoint. These stored values can then be used in conditions or actions in Event Orchestration rules. For more information see the [Knowledge Base](https://support.pagerduty.com/main/docs/event-orchestration-cache-variables) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_data_external_data_cache_variable_global_event_orchestration

Full name

pagerduty.pagerduty_get_external_data_cache_var_data_on_global_orch

Get Data for an External Data Cache Variable on a Service Event Orchestration Get the data for an `external_data` type Cache Variable for a Service Event Orchestration. Use External Data type Cache Variables to store string, number, or boolean values via a dedicated API endpoint. These stored values can then be used in conditions or actions in Event Orchestration rules. For more information see the [Knowledge Base](https://support.pagerduty.com/main/docs/event-orchestration-cache-variables) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_data_external_data_cache_variable_service_event_orchestration

Full name

pagerduty.pagerduty_get_external_data_cache_var_data_on_service_orch

Get an incident Show detailed information about an incident. Accepts either an incident id, or an incident number. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_incident

Full name

pagerduty.pagerduty_get_incident

Get an alert Show detailed information about an alert. Accepts an alert id. An incident represents a problem or an issue that needs to be addressed and resolved. When a service sends an event to PagerDuty, an alert and corresponding incident is triggered in PagerDuty. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_alert

Full name

pagerduty.pagerduty_get_incident_alert

Get Custom Field Values Get custom field values for an incident. <!-- theme: warning --> Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_custom_field_values

Full name

pagerduty.pagerduty_get_incident_field_values

List Business Services impacted by the given Incident Retrieve a list of Business Services that are being impacted by the given Incident. Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.list_business_services_impacted_by_given_incident

Full name

pagerduty.pagerduty_get_incident_impacted_business_services

List Notification Subscribers Retrieve a list of Notification Subscribers on the Incident. <!-- theme: warning --> > Users must be added through `POST /incident/{id}/status_updates/subscribers` to be returned from this endpoint. Scoped OAuth requires: `subscribers.read`

Lua path

app.integrations.pagerduty.list_notification_subscribers

Full name

pagerduty.pagerduty_get_incident_notification_subscribers

Get an Incident Type Get detailed information about a single incident type. Accepts either an incident type id, or an incident type name. Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incident) Scoped OAuth requires: `incident_types.read`

Lua path

app.integrations.pagerduty.get_incident_type

Full name

pagerduty.pagerduty_get_incident_type

Get an Incident Type Custom Field Get a custom field for an incident type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.get_incident_type_custom_field

Full name

pagerduty.pagerduty_get_incident_type_custom_field

Get a Field Option on a Custom Field Get a field option on a custom field Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.get_field_option_custom_field

Full name

pagerduty.pagerduty_get_incident_type_custom_field_field_options

Get an Incident Workflow Get an existing Incident Workflow An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident. Scoped OAuth requires: `incident_workflows.read`

Lua path

app.integrations.pagerduty.get_incident_workflow

Full name

pagerduty.pagerduty_get_incident_workflow

Get an Action Get an Incident Workflow Action Scoped OAuth requires: `incident_workflows.read`

Lua path

app.integrations.pagerduty.get_action

Full name

pagerduty.pagerduty_get_incident_workflow_action

Get a Trigger Retrieve an existing Incident Workflows Trigger Scoped OAuth requires: `incident_workflows.read`

Lua path

app.integrations.pagerduty.get_trigger

Full name

pagerduty.pagerduty_get_incident_workflow_trigger

Get a log entry Get details for a specific incident log entry. This method provides additional information you can use to get at raw event data. A log of all the events that happen to an Incident, and these are exposed as Log Entries. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#log-entries) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_log_entry

Full name

pagerduty.pagerduty_get_log_entry

Get a maintenance window Get an existing maintenance window. A Maintenance Window is used to temporarily disable one or more Services for a set period of time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#maintenance-windows) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_maintenance_window

Full name

pagerduty.pagerduty_get_maintenance_window

Get an OAuth client Get details of a specific OAuth client by ID. Requires admin or owner role permissions.

Lua path

app.integrations.pagerduty.get_oauth_client

Full name

pagerduty.pagerduty_get_oauth_client

Get OAuth delegations revocation requests status <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated as OAuth token revocation is now synchronous. Please use the [DELETE /oauth_delegations endpoint](https://developer.pagerduty.com/api-reference/ad1161db75db1-delete-all-o-auth-delegations) instead. Get the status of all OAuth delegations revocation requests for this account, specifically how many requests are still pending. As all requests are now synchronous, no pending requests will be found. This endpoint is limited to account owners and admins. Scoped OAuth requires: `oauth_delegations.read`

Lua path

app.integrations.pagerduty.get_oauth_delegations_revocation_requests_status

Full name

pagerduty.pagerduty_get_oauth_delegations_revocation_requests_status

Get the Service Orchestration active status for a Service Get a Service Orchestration's active status. A Service Orchestration allows you to set an active status based on whether an event will be evaluated against a service orchestration path (true) or service ruleset (false). For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_service_orchestration_active_status_service

Full name

pagerduty.pagerduty_get_orch_active_status

Get the Global Orchestration for an Event Orchestration. Global Orchestration Rules allows you to create a set of Event Rules. These rules evaluate against all Events sent to an Event Orchestration. When a matching rule is found, it can modify and enhance the event and can route the event to another set of Global Rules within this Orchestration for further processing. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_global_orchestration_event_orchestration

Full name

pagerduty.pagerduty_get_orch_path_global

Get the Router for an Event Orchestration Get a Global Orchestration's Routing Rules. An Orchestration Router allows you to create a set of Event Rules. The Router evaluates Events you send to this Global Orchestration against each of its rules, one at a time, and routes the event to a specific Service based on the first rule that matches. If an event doesn't match any rules, it'll be sent to service specified in as the `catch_all` or the "Unrouted" Orchestration if no service is specified. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_router_event_orchestration

Full name

pagerduty.pagerduty_get_orch_path_router

Get the Service Orchestration for a Service Get a Service Orchestration. A Service Orchestration allows you to create a set of Event Rules. The Service Orchestration evaluates Events sent to this Service against each of its rules, beginning with the rules in the "start" set. When a matching rule is found, it can modify and enhance the event and can route the event to another set of rules within this Service Orchestration for further processing. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_service_orchestration_service

Full name

pagerduty.pagerduty_get_orch_path_service

Get the Unrouted Orchestration for an Event Orchestration Get a Global Event Orchestration's Rules for Unrouted events. An Unrouted Orchestration allows you to create a set of Event Rules that will be evaluated against all events that don't match any rules in the Global Orchestration's Router. Events that reach the Unrouted Orchestration will never be routed to a specific Service. The Unrouted Orchestration evaluates Events sent to it against each of its rules, beginning with the rules in the "start" set. When a matching rule is found, it can modify and enhance the event and can route the event to another set of rules within this Unrouted Orchestration for further processing. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_unrouted_orchestration_event_orchestration

Full name

pagerduty.pagerduty_get_orch_path_unrouted

Get an Orchestration Get a Global Event Orchestration. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_orchestration

Full name

pagerduty.pagerduty_get_orchestration

Get an Integration for an Event Orchestration Get an Integration associated with this Event Orchestrations. You can use the Routing Key from this Integration to send events to PagerDuty! For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.get_integration_event_orchestration

Full name

pagerduty.pagerduty_get_orchestration_integration

Get Outlier Incident Gets Outlier Incident information for a given Incident on its Service. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#outlier-incident) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_outlier_incident

Full name

pagerduty.pagerduty_get_outlier_incident

Get an override <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve a single override by ID.

Lua path

app.integrations.pagerduty.get_override

Full name

pagerduty.pagerduty_get_override

Get Past Incidents Past Incidents returns Incidents within the past 6 months that have similar metadata and were generated on the same Service as the parent Incident. By default, 5 Past Incidents are returned. Note: This feature is currently available as part of the Event Intelligence package or Digital Operations plan only. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#past_incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_past_incidents

Full name

pagerduty.pagerduty_get_past_incidents

Get Paused Incident Reporting on Alerts Returns the 5 most recent alerts that were triggered after being paused and the 5 most recent alerts that were resolved after being paused for a given reporting period (maximum 6 months lookback period). Note: This feature is currently available as part of the Event Intelligence package or Digital Operations plan only. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#paused-incident-reports) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_paused_incident_reporting_alerts

Full name

pagerduty.pagerduty_get_paused_incident_report_alerts

Get Paused Incident Reporting counts Returns reporting counts for paused Incident usage for a given reporting period (maximum 6 months lookback period). Note: This feature is currently available as part of the Event Intelligence package or Digital Operations plan only. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#paused-incident-reports) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_paused_incident_reporting_counts

Full name

pagerduty.pagerduty_get_paused_incident_report_counts

Get a Status Page Post Update Get a Post Update for a Post by Post ID and Post Update ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_post_update

Full name

pagerduty.pagerduty_get_post_update

Get a Post Postmortem Get a Postmortem for a Post by Post ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_post_postmortem

Full name

pagerduty.pagerduty_get_postmortem

Get Related Incidents Returns the 20 most recent Related Incidents that are impacting other Responders and Services. Note: This feature is currently available as part of the Event Intelligence package or Digital Operations plan only. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#related_incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.get_related_incidents

Full name

pagerduty.pagerduty_get_related_incidents

Get a rotation <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve a rotation by ID including all its events.

Lua path

app.integrations.pagerduty.get_rotation

Full name

pagerduty.pagerduty_get_rotation

Get a Ruleset. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#rulesets) Scoped OAuth requires: `event_rules.read`

Lua path

app.integrations.pagerduty.get_ruleset

Full name

pagerduty.pagerduty_get_ruleset

Get an Event Rule. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#rulesets) Note: Create and Update on rules will accept 'description' or 'summary' interchangeably as an extraction action target. Get and List on rules will always return 'summary' as the target. If you are expecting 'description' please change your automation code to expect 'summary' instead. Scoped OAuth requires: `event_rules.read`

Lua path

app.integrations.pagerduty.get_event_rule

Full name

pagerduty.pagerduty_get_ruleset_event_rule

Get a schedule Show detailed information about a schedule, including entries for each layer. Scoped OAuth requires: `schedules.read`

Lua path

app.integrations.pagerduty.get_schedule

Full name

pagerduty.pagerduty_get_schedule

Get a schedule <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve a schedule by ID including rotations and events. Optionally include the computed final schedule for a time range. Use `include[]=final_schedule` to get computed on-call assignments. Use `since` and `until` to specify the time range.

Lua path

app.integrations.pagerduty.get_schedule

Full name

pagerduty.pagerduty_get_schedule_v3

Get a service Get details about an existing service. A service may represent an application, component, or team you wish to open incidents against. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_service

Full name

pagerduty.pagerduty_get_service

Get a Field Show detailed information about a Custom Field for Services. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.get_field

Full name

pagerduty.pagerduty_get_service_custom_field

Get a Field Option Get a field option for a given field. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.get_field_option

Full name

pagerduty.pagerduty_get_service_custom_field_option

Get Custom Field Values Get custom field values for a service. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_custom_field_values

Full name

pagerduty.pagerduty_get_service_custom_field_values

Get an Event Rule from a Service. <!-- theme: warning --> > ### End-of-life > Rulesets and Event Rules will end-of-life soon. We highly recommend that you [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_event_rule_from_service

Full name

pagerduty.pagerduty_get_service_event_rule

View an integration Get details about an integration belonging to a service. A service may represent an application, component, or team you wish to open incidents against. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.view_integration

Full name

pagerduty.pagerduty_get_service_integration

Get an account's session configurations Retrieves session configurations for a PagerDuty account. Returns an array containing the requested configurations. If a specific type is requested, the array contains one item. If no type is specified, the array contains all available configurations (mobile and web). If no configurations exist, a 404 Not Found error will be returned. A Session Configuration needs to be created before it can be retrieved and used. Scoped OAuth requires: `session_configurations.read`

Lua path

app.integrations.pagerduty.get_account_session_configurations

Full name

pagerduty.pagerduty_get_session_configurations

Get a single Status Dashboard by `id` Get a Status Dashboard by its PagerDuty `id`. Scoped OAuth requires: `status_dashboards.read`

Lua path

app.integrations.pagerduty.get_single_status_dashboard_by_id

Full name

pagerduty.pagerduty_get_status_dashboard_by_id

Get a single Status Dashboard by `url_slug` Get a Status Dashboard by its PagerDuty `url_slug`. A `url_slug` is a human-readable reference for a custom Status Dashboard that may be created or changed in the UI. It will generally be a `dash-separated-string-like-this`. Scoped OAuth requires: `status_dashboards.read`

Lua path

app.integrations.pagerduty.get_single_status_dashboard_by_url_slug

Full name

pagerduty.pagerduty_get_status_dashboard_by_url_slug

Get impacted Business Services for a Status Dashboard by `id`. Get impacted Business Services for a Status Dashboard by `id` This endpoint does not return an exhaustive list of Business Services but rather provides access to the most impacted on the specified Status Dashboard up to the limit of 200. The returned Business Services are sorted first by Impact, secondarily by most recently impacted, and finally by name. To get Impact information about a specific Business Service on the Status Dashboard that does not appear in the Impact-sorted response, use the `ids[]` parameter on the `/business_services/impacts` endpoint. Scoped OAuth requires: `status_dashboards.read`

Lua path

app.integrations.pagerduty.get_impacted_business_services_status_dashboard_by_id

Full name

pagerduty.pagerduty_get_status_dashboard_service_impacts_by_id

Get impacted Business Services for a Status Dashboard by `url_slug` Get Business Service Impacts for the Business Services on a Status Dashboard by its `url_slug`. A `url_slug` is a human-readable reference for a custom Status Dashboard that may be created or changed in the UI. It will generally be a `dash-separated-string-like-this`. This endpoint does not return an exhaustive list of Business Services but rather provides access to the most impacted on the Status Dashboard up to the limit of 200. The returned Business Services are sorted first by Impact, secondarily by most recently impacted, and finally by name. To get impact information about a specific Business Service on the Status Dashboard that does not appear in the Impact-sored response, use the `ids[]` parameter on the `/business_services/impacts` endpoint. Scoped OAuth requires: `status_dashboards.read`

Lua path

app.integrations.pagerduty.get_impacted_business_services_status_dashboard_by_url_slug

Full name

pagerduty.pagerduty_get_status_dashboard_service_impacts_by_url_slug

Get a Status Page Impact Get an Impact for a Status Page by Status Page ID and Impact ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_impact

Full name

pagerduty.pagerduty_get_status_page_impact

Get a Status Page Post Get a Post for a Status Page by Status Page ID and Post ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_post

Full name

pagerduty.pagerduty_get_status_page_post

Get a Status Page Service Get a Service for a Status Page by Status Page ID and Service ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_service

Full name

pagerduty.pagerduty_get_status_page_service

Get a Status Page Severity Get a Severity for a Status Page by Status Page ID and Severity ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_severity

Full name

pagerduty.pagerduty_get_status_page_severity

Get a Status Page Status Get a Status for a Status Page by Status Page ID and Status ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_status

Full name

pagerduty.pagerduty_get_status_page_status

Get a Status Page Subscription Get a Subscription for a Status Page by Status Page ID and Subscription ID. Scoped OAuth requires: `status_pages.read`

Lua path

app.integrations.pagerduty.get_status_subscription

Full name

pagerduty.pagerduty_get_status_page_subscription

Get a tag Get details about an existing Tag. A Tag is applied to Escalation Policies, Teams or Users and can be used to filter them. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#tags) Scoped OAuth requires: `tags.read`

Lua path

app.integrations.pagerduty.get_tag

Full name

pagerduty.pagerduty_get_tag

Get connected entities Get related Users, Teams or Escalation Policies for the Tag. A Tag is applied to Escalation Policies, Teams or Users and can be used to filter them. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#tags) Scoped OAuth requires: `tags.read`

Lua path

app.integrations.pagerduty.get_connected_entities

Full name

pagerduty.pagerduty_get_tags_by_entity_type

Get a team Get details about an existing team. A team is a collection of Users and Escalation Policies that represent a group of people within an organization. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#teams) Scoped OAuth requires: `teams.read`

Lua path

app.integrations.pagerduty.get_team

Full name

pagerduty.pagerduty_get_team

List Team Notification Subscriptions Retrieve a list of Notification Subscriptions the given Team has. <!-- theme: warning --> > Teams must be added through `POST /teams/{id}/notification_subscriptions` to be returned from this endpoint. Scoped OAuth requires: `subscribers.read`

Lua path

app.integrations.pagerduty.list_team_notification_subscriptions

Full name

pagerduty.pagerduty_get_team_notification_subscriptions

Get technical service dependencies Get all immediate dependencies of any technical service. Technical services are also known as `services`. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.get_technical_service_dependencies

Full name

pagerduty.pagerduty_get_technical_service_service_dependencies

Get a template Get a single template on the account Scoped OAuth requires: `templates.read`

Lua path

app.integrations.pagerduty.get_template

Full name

pagerduty.pagerduty_get_template

List template fields Get a list of fields that can be used on the account templates. Scoped OAuth requires: `templates.read`

Lua path

app.integrations.pagerduty.list_template_fields

Full name

pagerduty.pagerduty_get_template_fields

List templates Get a list of all the template on an account Scoped OAuth requires: `templates.read`

Lua path

app.integrations.pagerduty.list_templates

Full name

pagerduty.pagerduty_get_templates

Get a user Get details about an existing user. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.read`

Lua path

app.integrations.pagerduty.get_user

Full name

pagerduty.pagerduty_get_user

Get a user's contact method Get details about a User's contact method. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.read`

Lua path

app.integrations.pagerduty.get_user_contact_method

Full name

pagerduty.pagerduty_get_user_contact_method

List a user's contact methods List contact methods of your PagerDuty user. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.read`

Lua path

app.integrations.pagerduty.list_user_contact_methods

Full name

pagerduty.pagerduty_get_user_contact_methods

Get a user's delegation Get details about a specific OAuth delegation. This endpoint replaces the deprecated `/users/{id}/sessions/{session_id}` endpoint. **Required OAuth Scope:** For Scoped OAuth requests, this operation requires the `oauth_delegations.read` scope. Scoped OAuth requires: `oauth_delegations.read`

Lua path

app.integrations.pagerduty.get_user_delegation

Full name

pagerduty.pagerduty_get_user_delegation

Get a user's handoff notification rule Get details about a User's Handoff Notification Rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.read`

Lua path

app.integrations.pagerduty.get_user_handoff_notification_rule

Full name

pagerduty.pagerduty_get_user_handoff_notifiaction_rule

List a User's Handoff Notification Rules List Handoff Notification Rules of your PagerDuty User. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.read`

Lua path

app.integrations.pagerduty.list_user_handoff_notification_rules

Full name

pagerduty.pagerduty_get_user_handoff_notification_rules

Get the License allocated to a User Scoped OAuth requires: `licenses.read`

Lua path

app.integrations.pagerduty.get_license_allocated_user

Full name

pagerduty.pagerduty_get_user_license

Get a user's notification rule Get details about a user's notification rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.read`

Lua path

app.integrations.pagerduty.get_user_notification_rule

Full name

pagerduty.pagerduty_get_user_notification_rule

List a user's notification rules List notification rules of your PagerDuty user. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:contact_methods.read`

Lua path

app.integrations.pagerduty.list_user_notification_rules

Full name

pagerduty.pagerduty_get_user_notification_rules

List Notification Subscriptions Retrieve a list of Notification Subscriptions the given User has. <!-- theme: warning --> > Users must be added through `POST /users/{id}/notification_subscriptions` to be returned from this endpoint. Scoped OAuth requires: `subscribers.read`

Lua path

app.integrations.pagerduty.list_notification_subscriptions

Full name

pagerduty.pagerduty_get_user_notification_subscriptions

Get a user's session <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated, please use the [Get OAuth Delegation endpoint](https://developer.pagerduty.com/api-reference//e3c7cd550aa2b-get-a-user-oauth-delegation) instead. Get details about a user's session. Beginning November 2021, user sessions no longer includes newly issued OAuth tokens. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:sessions.read`

Lua path

app.integrations.pagerduty.get_user_session

Full name

pagerduty.pagerduty_get_user_session

List a user's active sessions <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated, please use the [List OAuth Delegations endpoint](https://developer.pagerduty.com/api-reference/fc03ba9dffd1f-list-user-oauth-delegations) instead. List active sessions of a PagerDuty user. Beginning November 2021, active sessions no longer includes newly issued OAuth tokens. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users:sessions.read`

Lua path

app.integrations.pagerduty.list_user_active_sessions

Full name

pagerduty.pagerduty_get_user_sessions

Get a user's status update notification rule Get details about a user's status update notification rule. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.read`

Lua path

app.integrations.pagerduty.get_user_status_update_notification_rule

Full name

pagerduty.pagerduty_get_user_status_update_notification_rule

List a user's status update notification rules List status update notification rules of your PagerDuty user. Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#users) Scoped OAuth requires: `users.read`

Lua path

app.integrations.pagerduty.list_user_status_update_notification_rules

Full name

pagerduty.pagerduty_get_user_status_update_notification_rules

Get a vendor Get details about one specific vendor. A PagerDuty Vendor represents a specific type of integration. AWS Cloudwatch, Splunk, Datadog are all examples of vendors For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#vendors) Scoped OAuth requires: `vendors.read`

Lua path

app.integrations.pagerduty.get_vendor

Full name

pagerduty.pagerduty_get_vendor

Get a webhook subscription Gets details about an existing webhook subscription. Scoped OAuth requires: `webhook_subscriptions.read`

Lua path

app.integrations.pagerduty.get_webhook_subscription

Full name

pagerduty.pagerduty_get_webhook_subscription

Get Workflow Integration Get details about a Workflow Integration. Scoped OAuth requires: `workflow_integrations.read`

Lua path

app.integrations.pagerduty.get_workflow_integration

Full name

pagerduty.pagerduty_get_workflow_integration

Get Workflow Integration Connection Get details about a Workflow Integration Connection. Scoped OAuth requires: `workflow_integrations:connections.read`

Lua path

app.integrations.pagerduty.get_workflow_integration_connection

Full name

pagerduty.pagerduty_get_workflow_integration_connection

List abilities List all of your account's abilities, by name. "Abilities" describes your account's capabilities by feature name. For example `"teams"`. An ability may be available to your account based on things like your pricing plan or account state. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#abilities) Scoped OAuth requires: `abilities.read`

Lua path

app.integrations.pagerduty.list_abilities

Full name

pagerduty.pagerduty_list_abilities

List installed Add-ons List all of the Add-ons installed on your account. Addon's are pieces of functionality that developers can write to insert new functionality into PagerDuty's UI. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#add-ons) Scoped OAuth requires: `addons.read`

Lua path

app.integrations.pagerduty.list_installed_add_ons

Full name

pagerduty.pagerduty_list_addon

List alert grouping settings List all of your alert grouping settings including both single service settings and global content based settings. The settings part of Alert Grouper service allows us to create Alert Grouping Settings and configs that are required to be used during grouping of the alerts. Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.list_alert_grouping_settings

Full name

pagerduty.pagerduty_list_alert_grouping_settings

List audit records List audit trail records matching provided query params or default criteria. The returned records are sorted by the `execution_time` from newest to oldest. See [`Cursor-based pagination`](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for instructions on how to paginate through the result set. Only admins, account owners, or global API tokens on PagerDuty account [pricing plans](https://www.pagerduty.com/pricing) with the "Audit Trail" feature can access this endpoint. For other role based access to audit records by resource ID, see the resource's API documentation. For more information see the [Audit API Document](https://developer.pagerduty.com/docs/rest-api-v2/audit-records-api/). Scoped OAuth requires: `audit_records.read`

Lua path

app.integrations.pagerduty.list_audit_records

Full name

pagerduty.pagerduty_list_audit_records

List Invocations

Lua path

app.integrations.pagerduty.list_invocations

Full name

pagerduty.pagerduty_list_automation_action_invocations

List Business Services List existing Business Services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#business-services) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.list_business_services

Full name

pagerduty.pagerduty_list_business_services

List Cache Variables for a Global Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.list_cache_variables_global_event_orchestration

Full name

pagerduty.pagerduty_list_cache_var_on_global_orch

List Cache Variables for a Service Event Orchestration. Cache Variables allow you to store event data on an Event Orchestration, which can then be used in Event Orchestration rules as part of conditions or actions. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `services.read`

Lua path

app.integrations.pagerduty.list_cache_variables_service_event_orchestration

Full name

pagerduty.pagerduty_list_cache_var_on_service_orch

List Change Events List all of the existing Change Events. Scoped OAuth requires: `change_events.read`

Lua path

app.integrations.pagerduty.list_change_events

Full name

pagerduty.pagerduty_list_change_events

List Field Options <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields/{field_id}/field_options](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}~1field_options/get) List all enabled Field Options for a Custom Field on the Base Incident Type. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.list_field_options

Full name

pagerduty.pagerduty_list_custom_fields_field_options

List Fields <!-- theme: warning --> > ### Deprecated > This endpoint is deprecated and only works for fields on the Base Incident Type. \ > For more flexibility, we recommend using the Incident Types endpoint: \ > [/incidents/types/{type_id_or_name}/custom_fields](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields/get) List Custom Fields on the Base Incident Type. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.list_fields

Full name

pagerduty.pagerduty_list_custom_fields_fields

List custom shifts <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve custom shifts for a schedule within a time range. **`since` and `until` are required.**

Lua path

app.integrations.pagerduty.list_custom_shifts

Full name

pagerduty.pagerduty_list_custom_shifts

List escalation policies List all of the existing escalation policies. Escalation policies define which user should be alerted at which time. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#escalation-policies) Scoped OAuth requires: `escalation_policies.read`

Lua path

app.integrations.pagerduty.list_escalation_policies

Full name

pagerduty.pagerduty_list_escalation_policies

List audit records for an escalation policy The returned records are sorted by the `execution_time` from newest to oldest. See [`Cursor-based pagination`](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for instructions on how to paginate through the result set. For more information see the [Audit API Document](https://developer.pagerduty.com/docs/rest-api-v2/audit-records-api/). Scoped OAuth requires: `audit_records.read`

Lua path

app.integrations.pagerduty.list_audit_records_escalation_policy

Full name

pagerduty.pagerduty_list_escalation_policy_audit_records

List Enablements for an Event Orchestration List all feature enablement settings for an Event Orchestration. Currently, only the `aiops` enablement is supported. For any account with the AIOps product addon, every Event Orchestration will have AIOps features enabled by default. **Warning conditions**: - If the account is not entitled to use AIOps features, a warning will be returned alongside the enablement data. Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.list_enablements_event_orchestration

Full name

pagerduty.pagerduty_list_event_orchestration_feature_enablements

List Event Orchestrations List all Global Event Orchestrations on an Account. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.read`

Lua path

app.integrations.pagerduty.list_event_orchestrations

Full name

pagerduty.pagerduty_list_event_orchestrations

List events <!-- theme: warning --> > ### Early Access > This API is in Early Access and may change at any time. You must pass the `X-EARLY-ACCESS: flexible-schedules-early-access` header on every request. <!-- theme: info --> > **Important note:** Shift-based schedules use the V3 API and are not compatible with V2 automations. **To create automations for Shift-Based Schedules, you need to:** > > 1. **Update your automations** to use the V3 API for all new shift-based schedules > 2. **Keep the V2 endpoint** for your existing schedules > > An upgrade tool for existing schedules is coming soon; your legacy schedules will keep working in the meantime. [Learn more](https://support.pagerduty.com/main/docs/shift-based-schedules-api-upgrade-examples). Retrieve all events for a rotation, ordered by start time.

Lua path

app.integrations.pagerduty.list_events

Full name

pagerduty.pagerduty_list_events

List extension schemas List all extension schemas. A PagerDuty extension vendor represents a specific type of outbound extension such as Generic Webhook, Slack, ServiceNow. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extension-schemas) Scoped OAuth requires: `extension_schemas.read`

Lua path

app.integrations.pagerduty.list_extension_schemas

Full name

pagerduty.pagerduty_list_extension_schemas

List extensions List existing extensions. Extensions are representations of Extension Schema objects that are attached to Services. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#extensions) Scoped OAuth requires: `extensions.read`

Lua path

app.integrations.pagerduty.list_extensions

Full name

pagerduty.pagerduty_list_extensions

List alerts for an incident List alerts for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.list_alerts_incident

Full name

pagerduty.pagerduty_list_incident_alerts

List log entries for an incident List log entries for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. A Log Entry are a record of all events on your account. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.list_log_entries_incident

Full name

pagerduty.pagerduty_list_incident_log_entries

List notes for an incident List existing notes for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.list_notes_incident

Full name

pagerduty.pagerduty_list_incident_notes

List related Change Events for an Incident, as well as the reason these changes are correlated with the incident. Change events represent service changes such as deploys, build completion, and configuration changes, providing information that is critical during incident triage or hypercare. For more information on change events, see [Change Events](https://support.pagerduty.com/docs/change-events). The Change Correlation feature provides incident responders with recent change events that are most relevant to that incident. Change Correlation informs the responder why a particular change event was surfaced and correlated to an incident based on three key factors which include time, related service, or intelligence (machine learning). Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.list_related_change_events_incident

Full name

pagerduty.pagerduty_list_incident_related_change_events

List Field Options on a Custom Field List field options for a custom field. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.list_field_options_custom_field

Full name

pagerduty.pagerduty_list_incident_type_custom_field

List Incident Type Custom Fields List the custom fields for an incident type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types. Scoped OAuth requires: `custom_fields.read`

Lua path

app.integrations.pagerduty.list_incident_type_custom_fields

Full name

pagerduty.pagerduty_list_incident_type_custom_fields

List incident types List the available incident types Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident. These can be filtered by enabled or disabled types. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidentType) Scoped OAuth requires: `incident_types.read`

Lua path

app.integrations.pagerduty.list_incident_types

Full name

pagerduty.pagerduty_list_incident_types

List Actions List Incident Workflow Actions Scoped OAuth requires: `incident_workflows.read`

Lua path

app.integrations.pagerduty.list_actions

Full name

pagerduty.pagerduty_list_incident_workflow_actions

List Triggers List existing Incident Workflow Triggers Scoped OAuth requires: `incident_workflows.read`

Lua path

app.integrations.pagerduty.list_triggers

Full name

pagerduty.pagerduty_list_incident_workflow_triggers

List Incident Workflows List existing Incident Workflows. This is the best method to use to list all Incident Workflows in your account. If your use case requires listing Incident Workflows associated with a particular Service, you can use the "List Triggers" method to find Incident Workflows configured to start for Incidents in a given Service. An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident. Scoped OAuth requires: `incident_workflows.read`

Lua path

app.integrations.pagerduty.list_incident_workflows

Full name

pagerduty.pagerduty_list_incident_workflows

List incidents List existing incidents. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#incidents) Scoped OAuth requires: `incidents.read`

Lua path

app.integrations.pagerduty.list_incidents

Full name

pagerduty.pagerduty_list_incidents