Uptimeify Docs
Incident management

Snooze Incident

Pauses escalation and reminders of an open Incident Management incident until a given time (at most 7 days ahead), or ends a snooze early.

POST /api/im/incidents/:id/snooze

Pauses an open incident's escalation and reminders until snoozedUntil. Pending escalation jobs are cancelled and paging resumes automatically when the snooze ends. Sending null (or omitting the field) ends a snooze immediately: a triggered incident resumes escalating at its current tier right away. Each call is recorded on the incident timeline.

Authentication

Any IM-eligible role (admin, editor, responder) or an organization-wide API token, see Authentication. Incident Management must be enabled for the organization.

Restricted to the incident's team: you must be a member of the incident's team (teamId) or an organization admin. An organization-wide API token passes as an organization admin.

Request Body

FieldTypeRequiredDescription
snoozedUntilISO 8601 date-time or nullNoWhen paging resumes. Must be in the future and at most 7 days from now. null or omitted clears the snooze.

Example (cURL)

curl -X POST "$BASE_URL/api/im/incidents/42/snooze" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "snoozedUntil": "2026-07-17T13:00:00.000Z" }'

End a snooze early:

curl -X POST "$BASE_URL/api/im/incidents/42/snooze" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "snoozedUntil": null }'

Response

200 OK: the updated incident row (same shape as the items of List Incidents, without the enrichment fields).

{
  "id": 42,
  "teamId": 3,
  "title": "Database connection pool exhausted",
  "severity": "sev1",
  "status": "triggered",
  "currentTier": 1,
  "escalationEpoch": 2,
  "snoozedUntil": "2026-07-17T13:00:00.000Z"
}

(Shortened; the full row is returned.)

Common errors

  • 401 Unauthorized when not authenticated
  • 403 Forbidden (customerScopedTokenForbidden) when using a customer-scoped token
  • 403 Forbidden (imAccessDenied) when the session user has no IM-eligible role
  • 403 Forbidden (imNotEnabled) when Incident Management is not enabled for the organization
  • 403 Forbidden (imTeamMembershipRequired) when you are neither a member of the incident's team nor an organization admin
  • 400 Bad Request (invalidRequestBody) when :id is not a positive integer, or snoozedUntil is not a valid date-time
  • 400 Bad Request (imSnoozeRangeInvalid) when snoozedUntil is not in the future or more than 7 days ahead
  • 404 Not Found (imIncidentNotFound) when the incident does not exist, or belongs to another organization
  • 422 Unprocessable Entity (imIncidentClosed) when the incident is resolved or merged

On this page