IncidentsDELETE /incidents/{id}

DELETE /incidents/{id}

Soft-delete incident

Example request

curl -X DELETE "/api/v1/incidents/{id}" \
  -H "Authorization: Bearer YOUR_API_KEY"

Responses

200: deleted

401: missing or invalid bearer token

title: unauthenticated. No bearer token was sent, or the key is invalid or revoked. detail distinguishes the two.

403: missing required scope

title: forbidden. The key is valid but does not carry write:incidents.

404: not found

title: not_found. No incident with that id is available to this key. An incident owned by another organisation returns the same response, so a 404 does not confirm that the id is unused.

429: rate limit exceeded

title: rate_limited. A burst or daily limit was exceeded; detail names which. The body carries retry_after in seconds.

500: internal error

title: internal_error. An unhandled server error. Safe to retry.

Every error is an RFC 7807 problem detail served as application/problem+json:

{
  "type": "https://observer.example/problems/forbidden",
  "title": "forbidden",
  "status": 403,
  "detail": "missing scope: write:incidents"
}

Branch on title, not on detail. See Errors and status codes for the full catalogue and the rate-limit headers.