409 Conflict

https://sealdeal.ai/errors/conflict

The resource exists and you may touch it, but its current state does not permit this operation.

Retry only after changing the request

What causes it

Acting on an already-terminal record, for example dismissing an action item that is already closed.

How to fix it

Refetch the resource and decide from its current state. A 409 is safe to resolve programmatically, which is exactly why it is kept distinct from a 400 (malformed) and a 403 (escalate to a human).

Example response

HTTP/1.1 409
Content-Type: application/problem+json

{
  "type": "https://sealdeal.ai/errors/conflict",
  "title": "Conflict",
  "status": 409,
  "detail": "..."
}

`type` is stable and safe to branch on in code. `detail` is specific to your request and is the field to read for the particulars; its wording may change.

All error types · API documentation · Integrations