idempotency_key_conflict

What to do

Use a new key for each distinct request. Replaying the first answer would leave the second record never created while you believed it succeeded, so this is refused loudly instead.

Should you try again?

No. The same request will fail the same way. Change something first.

How you'll see it

{
  "type": "https://www.obraledger.com/api/errors/idempotency_key_conflict",
  "detail": "..."
}

The body also carries a title and a status. The detail is written for a person and we may reword it, so don't match on it. Some failures also carry a violations list naming the fields at fault.

Building something and stuck? Tell us - we'd rather hear it than have you guess.