Idempotency-Key reused with a different request (idempotency_key_reused)

• HTTP status: 422
• Problem type URI: https://nowgetitdone.com/docs/api/problems/idempotency-key-reused

What it means

An Idempotency-Key was reused with a DIFFERENT request body than the one it first recorded.

Likely causes

• A key was recycled across two genuinely different requests.
• The request body changed between the first attempt and the retry.

How to fix

• Generate a fresh key for every distinct request.
• Send the byte-identical body when retrying with the same key.

Example problem+json

{
    "type": "https://nowgetitdone.com/docs/api/problems/idempotency-key-reused",
    "title": "Idempotency-Key reused with a different request",
    "status": 422,
    "code": "idempotency_key_reused",
    "request_id": "req_a1b2c3d4"
}

Related

• Idempotency