Incidents
Acknowledge or resolve an incident
POST/v1/incidents/{id}requires incidents:write
Use the incident_id returned by alert ingestion. Acknowledgment and resolution cancel pending escalation atomically; resolution also releases the active alias. Repeating the same action is safe and returns unchanged: true when already in the requested state. Resolved incidents cannot be acknowledged or reopened. No Idempotency-Key is required. Actions are attributed to the API key in the incident timeline and audit log. The key is rechecked within the write transaction, and test keys cannot mutate live incidents. The JSON body is limited to 1 KiB.
Requestcurl -X POST https://api.transmit.dev/v1/incidents/{id} \
-H "Authorization: Bearer tr_v2_…" \
-H "Content-Type: application/json" \
-d '{
"action": "resolve"
}'Parameters
| Name | In | Notes |
|---|---|---|
id required | path | The incident id. |
Body
| Field | Type | Notes |
|---|---|---|
action required | "acknowledge" | "resolve" |
Responses
| Status | Meaning |
|---|---|
200 | Current state after the action |
401 | The API key is missing, malformed, expired or revoked |
403 | The API key lacks the incidents:write scope |
404 | Incident not found in this workspace and key mode |
409 | Resolved incident cannot be acknowledged |
413 | Body exceeds 1 KiB |
415 | Content-Type must be application/json |
422 | Invalid action |
Every response body is described in the OpenAPI spec, which this page is generated from.