OpsKnightinbound
Alert source into OpsKnight.
WEBHOOKS / INBOUND
Generic webhook.
Connected to the response.
Bring Generic webhook 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/webhook
Protocol: webhook
trigger · acknowledge · resolve
Only actions present in the release catalog are shown.
integration-key
Signature verification: conditional when secret configured.
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: BearerAuthorization: Token token=x-integration-keyx-api-keyintegrationKey query parameter
Common endpoint outcomes
HTTP400Invalid request or payload validation failed
401Integration is disabled, mismatched, or unauthorized
404Integration record was not found
413Payload exceeds the one MiB body limit
429Per-integration request rate exceeded
503A matching delivery is already being processed
GENERIC WEBHOOK · VERIFIED DEFAULT FIELDS
Start from a source-backed request.
The generic adapter reads summary, severity,dedup_key, source and status by default. Authorization Bearer is one of the accepted integration-key transports.
payload.json
{
"summary": "Database connection pool exhausted",
"severity": "critical",
"dedup_key": "db-pool-prod",
"source": "payments-api",
"status": "triggered"
}cURL
curl -X POST "https://your-opsknight.example/api/integrations/webhook" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <integration-key>" \
--data @payload.jsonYour incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations