Delete Incident (Manual only)

DELETE /api/incidents/:id

Deletes a manual incident (a status-page announcement created by an admin) together with its timeline updates. Monitor-generated incidents are worker-owned and can never be deleted, the endpoint rejects them with 403 notManualIncident.

AuthenticationCopy Anchor Link

Within the incident's customer scope. If the incident is linked to status pages, every linked page must allow it: organization-wide callers need the role admin or editor; customer-bound users (also with the role readonly) and customer-bound API tokens need self_service pages, or managed pages with the customer's canEditManaged exception (otherwise 403 managed_by_organization). An incident linked to no page keeps the role rule: admin or editor.

• Header: Authorization: Bearer <token>

Path ParametersCopy Anchor Link

• id (required): The incident's numeric ID or its publicId (UUID).

Example (cURL)Copy Anchor Link

BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

curl -X DELETE "$BASE_URL/api/incidents/8d1f0c2e-6a2b-4f1e-9b7c-2e5a1d3c4b5a" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Accept: application/json"

Example ResponseCopy Anchor Link

{
  "success": true,
  "ok": true
}

ok is deprecated and stays for existing readers; read success.

Common ErrorsCopy Anchor Link

• 400 Incident id is required if no ID is supplied
• 400 Invalid Incident identifier if the ID is neither a numeric incident id nor a UUID
• 401 Unauthorized if you are not authenticated
• 403 Forbidden if you do not have write access to the incident's customer
• 403 Forbidden (managed_by_organization) when you are customer-bound (user, also with the role readonly, or token) and a status page involved is managed without the customer's canEditManaged exception
• 403 Only manual incidents can be deleted (data.code: notManualIncident) if the incident is monitor-generated
• 404 Incident not found if no incident matches the ID