IDEMPOTENCY_KEY_PROCESSING

When it happens

A request with the same Idempotency-Key is still being processed, usually because a client retried before the first call answered. It can happen on any operation that accepts the header.

How to fix it

Wait for the seconds in Retry-After and retry with the same key. Once the first call finishes, the retry returns its result. A new key would perform the operation a second time.

Retry

Retry the same request unchanged, with the same Idempotency-Key if you sent one. Wait first, and honour the Retry-After header when the response carries it.

Rules that cite this code

• LIF-004 Retry writes with the same Idempotency-Key

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_PROCESSING",
  "title": "IDEMPOTENCY_KEY_PROCESSING",
  "detail": "A request with this idempotency key is already being processed. Wait and retry with the same key.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "IDEMPOTENCY_KEY_PROCESSING",
    "message": "A request with this idempotency key is already being processed. Wait and retry with the same key.",
    "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

Keep exploring