422

API problem detail

Idempotency Conflict

Description

This problem happens when an X-Idempotency-Key is reused with a request body different from the one it was first used with. The Problem Details type is IdempotencyConflict. The original operation is untouched and the new request was not processed.

Experience API error bodies also carry errorCode, resolution, and traceId. Branch on errorCode, not on title or detail; see fields on every error.

How to resolve

Use a fresh UUID v4 key for every distinct operation, and never edit the body of a retry. A retry is only safe when it repeats the original operation byte-for-byte with the original key.
Back to all problem details