OpsKnightinbound
Alert source into OpsKnight.
WEBHOOKS / INBOUND
PagerDuty Events API.
Connected to the response.
Bring PagerDuty Events API into your self-hosted incident workflow. Keep configuration and credentials on infrastructure you control.
RELEASE CONTRACT
What this connection actually accepts.
Generated from the pinned v2.0.0 provider catalog rather than a generic marketing template.
POST /api/integrations/pagerduty
Protocol: webhook
trigger · acknowledge · resolve
Only actions present in the release catalog are shown.
integration-key-or-routing-key
Signature verification: none.
Request contract
- Integration identifier
- query parameter
- Body limit
- 1 MiB
- Rate limit
- 100 requests / 60s / integration
- Correlation
- adapter EventPayload.dedup_key
- Recovery
- adapter emits resolve for its recovery state
Accepted credential forms
Authorization: Bearerx-routing-keykey query parametertoken query parameterrouting_key payload field
Common endpoint outcomes
HTTP400Invalid request or payload validation failed
401Configured authentication or signature validation failed
403Integration is disabled
404Integration record was not found
413Payload exceeds the one MiB body limit
429Per-integration request rate exceeded
500Provider event processing failed
Your incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations