Incidents

Receive Datadog monitor webhooks

POST/v1/integrations/datadog/{configurationId}/{escalationPolicyId}requires incidents:ingest

Accepts the body produced by the documented Datadog webhook payload template. transition Recovered resolves the active incident for the aggregate key; every other transition opens or joins one. $ALERT_PRIORITY P1–P5 sets severity; otherwise warnings are medium and alerts high. Requires both incidents:ingest and incidents:write. Body limit 64 KiB. See /docs/incident-datadog.

Requestcurl -X POST https://api.transmit.dev/v1/integrations/datadog/{configurationId}/{escalationPolicyId} \
  -H "Authorization: Bearer tr_v2_…" \
  -H "Content-Type: application/json" \
  -d '{
       "alert_id": "12345",
       "aggregate": "a1b2c3",
       "transition": "Triggered",
       "title": "[Triggered] Database unavailable",
       "body": "Primary is refusing connections.",
       "priority": "P1",
       "link": "https://app.datadoghq.com/monitors/12345"
     }'

Parameters

Name	In	Notes
`configurationId` required	path	Routing resource UUID in the API key's workspace.
`escalationPolicyId` required	path	Routing resource UUID in the API key's workspace.

Body

Field	Type	Notes
`alert_id`	`string`	at most 128 characters. defaults to ""
`aggregate`	`string`	at most 256 characters. defaults to ""
`transition` required	`string`	1–64 characters
`title` required	`string`	1–1000 characters
`body`	`string`	at most 20000 characters. defaults to ""
`priority`	`string`	at most 16 characters. defaults to ""
`link`	`string`	at most 2048 characters. defaults to ""

Responses

Status	Meaning
`200`	Committed outcome
`401`	The API key is missing, malformed, expired or revoked
`403`	The API key lacks the `incidents:ingest` scope
`404`	Routing resources are outside this workspace
`413`	Body exceeds 64 KiB
`415`	Use application/json
`422`	Invalid event

Every response body is described in the OpenAPI spec, which this page is generated from.