idempotency-key-conflict
HTTP status: 422 Unprocessable Entity
Type URI: https://docs.evinor.ai/problems/idempotency-key-conflict
You reused an Idempotency-Key that was already used for a different request.
A key is bound to the first request's method, path, and body; sending a different
request under the same key is a conflict.
Common causes
- Reusing one idempotency key across unrelated operations.
- Retrying with the same key but a changed request body.
How to resolve
Use a fresh, unique idempotency key for each distinct operation. Only reuse a key when you are retrying the exact same request (same method, path, and body). See Idempotency.