APIs.io Engineering Platform Notification Destinations with PagerDuty API
The Notification Destinations with PagerDuty API from APIs.io Engineering Platform — 3 operation(s) for notification destinations with pagerduty.
This API exposes 4 operations across 3 paths, and defines 15 schemas. It is described by OpenAPI 3.0.0, at version 2015-07-09.
Requests are made against 4 base URLs: http://apigateway.{region}.amazonaws.com, https://apigateway.{region}.amazonaws.com, http://apigateway.{region}.amazonaws.com.cn, https://apigateway.{region}.amazonaws.com.cn.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
APIs.io Engineering Platform Notification Destinations with PagerDuty API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (hmac).
By default, every request must be authenticated.
hmac— Amazon Signature authorization v4
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are aaa_result_info (4 properties), aaa_schemas-api-response-common-failure (3 properties), aaa_api-response-common (3 properties), aaa_pagerduty (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.