conflict

The request contradicts the resource's current state.

• Creating something whose unique field already exists — a duplicate slug or name.
• Transitioning a resource to a state it cannot reach from where it is.
• Two writes racing against the same row.

• Re-read the resource and decide whether the write is still the one you want.
• For creates, treat a conflict as 'already exists' and read it instead.

{
  "error": {
    "code": "conflict",
    "message": "The request contradicts the resource's current state",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/conflict",
  "title": "Conflict",
  "status": 409,
  "detail": "The request contradicts the resource's current state",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• idempotency_in_progress

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.