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
Scoped OAuth requires: event_orchestrations.write
Authorization
api_key The API Key with format Token token=<API_KEY>
In: header
Path Parameters
The ID of an Event Orchestration.
The ID of an Integration.
Header Parameters
The Accept header is used as a versioning header.
"application/vnd.pagerduty+json;version=2""application/json"Value in
- "application/json"
Response Body
application/json
application/json
application/json
application/json
application/json
Delete Data for an External Data Cache Variable on a Service Event Orchestration DELETE
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`
Delete an Orchestration DELETE
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](https://developer.pagerduty.com/api-reference/a47605517c19a-api-concepts#event-orchestrations) Scoped OAuth requires: `event_orchestrations.write`