Wipe the body of an incident update and record who removed it. Append-only — the row itself is preserved.
curl --request POST \
--url "https://api.scaling.cloud/v1/incidents/YOUR_INCIDENT_ID/updates/YOUR_UPDATE_ID/redact" \
--header "Authorization: Bearer YOUR_API_KEY"
{
"data": {
"id": "0193e1a2-3b4c-7890-abcd-ef1234567890",
"incidentId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"body": null,
"statusChange": "identified",
"visibility": "public",
"postedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" },
"postedAt": "2025-04-07T09:14:00.000Z",
"redactedAt": "2025-04-07T09:17:30.000Z",
"redactedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" }
}
}
Removes the body of an incident update. The row stays at its originalDocumentation Index
Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt
Use this file to discover all available pages before exploring further.
postedAt; body is cleared, and redactedAt / redactedBy are set. The statusChange carried by the update — if any — is preserved: the system cannot lie about lifecycle state.
To correct a previous statement, redact the original and post a new update.
| Caller | When |
|---|---|
| The original author | Within 5 minutes of postedAt. |
| An organization admin | At any time. |
POST is used (not DELETE or PATCH) to reflect the append-only contract at the URL level: nothing is deleted, and no field is edited — the redaction is an explicit, named action.
Redaction is permitted even after the incident is resolved — it is the only mutation that survives the terminal status.
id of the update to redact, as returned by Post Incident Update or List Incident Updates.body will be null, and redactedAt / redactedBy will be populated. statusChange is preserved.| Status | Code | Description |
|---|---|---|
401 | not_authorized | Missing or invalid credentials. |
403 | redaction_not_permitted | The caller is not the original author within the 5-minute window, and is not an org admin. |
404 | not_found | No update with the given updateId exists on this incident in your organization. |
500 | server_error | An unexpected error occurred on our side. |
curl --request POST \
--url "https://api.scaling.cloud/v1/incidents/YOUR_INCIDENT_ID/updates/YOUR_UPDATE_ID/redact" \
--header "Authorization: Bearer YOUR_API_KEY"
{
"data": {
"id": "0193e1a2-3b4c-7890-abcd-ef1234567890",
"incidentId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"body": null,
"statusChange": "identified",
"visibility": "public",
"postedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" },
"postedAt": "2025-04-07T09:14:00.000Z",
"redactedAt": "2025-04-07T09:17:30.000Z",
"redactedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" }
}
}
curl --request POST \
--url "https://api.scaling.cloud/v1/incidents/YOUR_INCIDENT_ID/updates/YOUR_UPDATE_ID/redact" \
--header "Authorization: Bearer YOUR_API_KEY"
{
"data": {
"id": "0193e1a2-3b4c-7890-abcd-ef1234567890",
"incidentId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"body": null,
"statusChange": "identified",
"visibility": "public",
"postedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" },
"postedAt": "2025-04-07T09:14:00.000Z",
"redactedAt": "2025-04-07T09:17:30.000Z",
"redactedBy": { "id": "user_2b9a3d4e5f6g7h8j", "name": "Alice Chen" }
}
}