IDEMPOTENCY_KEY_MISMATCH
This idempotency key was already used with a different request body. Use a new key for a different operation.
Category: General
| HTTP status | 409 Conflict |
| Retry | Yes, with a new key |
When it happens
The Idempotency-Key was already used, within the last 24 hours, for a request with a different body. A key identifies one operation, so it is not replayed for another. It can happen on any operation that accepts the header.
How to fix it
Generate a new key for each distinct operation. Reuse a key only to retry exactly the same request.
Retry
Retry under a new Idempotency-Key. Reusing the old key cannot succeed.
Rules that cite this code
Example response
When this error occurs, the API answers 409 Conflict with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/IDEMPOTENCY_KEY_MISMATCH",
"title": "IDEMPOTENCY_KEY_MISMATCH",
"detail": "This idempotency key was already used with a different request body. Use a new key for a different operation.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "IDEMPOTENCY_KEY_MISMATCH",
"message": "This idempotency key was already used with a different request body. Use a new key for a different operation.",
"details": {}
},
"meta": {
"timestamp": "2026-05-21T10:00:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}The type URI is stable and always resolves to this page.
Message
Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.
Other errors in this category
AUTOMATIC_EMAIL_CONFIG_INVALID
For automatic sending, you must provide an email configuration or a client with email
BAD_REQUEST
The provided data is not valid.
BUSINESS_RULE_VIOLATION
The operation breaks a business rule.
CITY_EMPTY
City cannot be empty
CITY_MAX_LENGTH
City cannot exceed ‹value› characters