Get It Done

HTTP 422idempotency_key_reused

Idempotency-Key reused with a different request

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 response

application/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"
}

The type field resolves to this page: https://nowgetitdone.com/docs/api/problems/idempotency-key-reused

Related

Idempotency →