pagerduty.com

Create a PagerDuty API token in your account. For account-wide REST access, follow the support guide to generate a general access REST API key at Generating a General Access REST API Key. The developer auth docs also describe account and user API tokens at Authentication. Send it in the Authorization header as Token token=<API_KEY> where supported.

Register a PagerDuty app from Register an App. On Integrations → App Registration, create a new app and add OAuth functionality. For Classic User OAuth, use the authorization code or PKCE flow described in OAuth Functionality and User OAuth Token via Code Grant. For Scoped OAuth app-to-account access, use the client credentials flow in Obtaining an App OAuth Token. This gives you a client_id and, for confidential apps, a client_secret, which you exchange for bearer access tokens from https://identity.pagerduty.com/oauth/token.

Create an Events API v2 integration on a PagerDuty service using the support steps at Services and Integrations: Events API v2. The integration exposes a 32-character Integration Key used as the routing_key in Events API v2 requests. The same key can be used for both alert and change events.

Create a PagerDuty service with service type Generic API as described in the Events API v1 schema at reference/events-v1/openapiv3.json. The service detail page exposes the service_key, which you send in Events API v1 requests.