GET /incident_workflows/triggers

List existing Incident Workflow Triggers

Scoped OAuth requires: incident_workflows.read

Servers

https://api.pagerduty.com

Request headers

Name Type Required Description

Name	Type	Required	Description
`Accept`	String	Yes	The `Accept` header is used as a versioning header. Default value: "application/vnd.pagerduty+json;version=2"
`Content-Type`	String	Yes	Possible values: `"application/json"` Default value: "application/json"

Accept

String

Yes

The Accept header is used as a versioning header.

Default value: "application/vnd.pagerduty+json;version=2"

Content-Type

String

Yes

Possible values:

"application/json"

Default value: "application/json"

Query parameters

Name	Type	Required	Description
`trigger_type`	String	No	If provided, only show triggers of the given type. For example “manual” to search for manual triggers Possible values: `"manual"` `"conditional"` `"incident_type"`
`is_disabled`	Boolean	No	If provided, filters between disabled and enabled Triggers. This query parameter is deprecated, and will be removed in a future version of this API.
`limit`	Integer	No	The minimum of the `limit` parameter used in the request or the maximum request size of the API.
`incident_id`	String	No	If provided, only show triggers configured on the service of the given incident. Useful for finding manual triggers that are configured on the service for a specific incident. Cannot be specified if `service_id` is provided.
`service_id`	String	No	If provided, only show triggers configured for incidents in the given service. Useful for listing all workflows associated with the given service. Cannot be specified if `incident_id` is provided.
`workflow_id`	String	No	If provided, only show triggers configured to start the given workflow. Useful for listing all services associated with the given workflow
`workflow_name_contains`	String	No	If provided, only show triggers configured to start workflows whose name contain the provided value.
`cursor`	String	No	Optional parameter used to request the "next" set of results from an API. The value provided here is most commonly obtained from the `next_cursor` field of the previous request. When no value is provided, the request starts at the beginning of the result set.
`sort_by`	String	No	If provided, returns triggers sorted by the specified property. Possible values: `"workflow_name asc"` `"workflow_id"` `"workflow_id desc"` `"workflow_name desc"` `"workflow_name"` `"workflow_id asc"`

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.