Error reference / idempotency-key-reused
Idempotency-Key was already used with a different request
The same key arrived with a different method, path, or body.
| Problem type | /problems/idempotency-key-reused |
|---|---|
| HTTP status | 422 |
| Emitted by | REST API (/v1) |
| Title values | Idempotency-Key was already used with a different request |
| Trigger | REST API (/v1): same Idempotency-Key, different request |
What happened
An Idempotency-Key was reused within its 24-hour window, but the request it now accompanies is not the one it was first used for. The response is HTTP 422.
What it means
Keys are a promise that the request is the same; a different body under the same key is refused rather than guessed at. Nothing was processed.
What to do next
Use a fresh key (a UUID) for each distinct request. Reuse a key only to retry the identical request after a network failure.
Problem body
Every error is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/idempotency-key-reused",
"title": "Idempotency-Key was already used with a different request",
"status": 422,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/idempotency-key-reused"
}