idempotency_conflict
The same idempotency key was reused with a different body
HTTP 409idempotency_conflict
This Idempotency-Key was already used for a request whose body differed, so replaying it would be a lie.
Why it happens
- A key derived from something that is not unique per request, such as a user id rather than an order id.
- A retry that rebuilt the body and changed a timestamp inside it.
How to fix it
- Derive the key from the thing the send is about, once, and store it:
order-4821-otp, notuser-19. - Keep the body byte-identical across retries. If the body must change, the request is a new one and needs a new key.
Is it worth retrying?
Only after you change something. Retrying as-is will fail again.
What the response looks like
HTTP/1.1 409
Content-Type: application/json
Woyra-Request-Id: req_01J...
{
"error": {
"code": "idempotency_conflict",
"message": "…",
"doc_url": "https://docs.woyra.io/errors/idempotency_conflict",
"param": null,
"request_id": "req_01J..."
}
}