Skip to content

Idempotency-Key missing

HTTP 422idempotency_key_missing

When the API answers 422 idempotency_key_missing, and how to fix it.

Version v1.1, updated

The type field of every idempotency_key_missing response links to this page.

On this page

Every POST must carry an Idempotency-Key header, and this one has none. BIRP refuses it rather than risk a write applied twice.

At a glance

  • Status: 422 Unprocessable Content

  • Code: idempotency_key_missing

  • Retry: No. Fix the cause first: the same request gets the same answer.

Causes and fixes

Likely cause

How to fix it

The request has no Idempotency-Key header.

Create a new UUID for each write, send it in Idempotency-Key, and keep it for the retries of that write.

Example

422 idempotency_key_missingJSON
{
  "code": "idempotency_key_missing",
  "detail": "POST requests must carry an Idempotency-Key header, unique for each distinct request.",
  "instance": "/v1/categories",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 422,
  "title": "Idempotency-Key missing",
  "type": "https://birp.io/developers/errors/idempotency_key_missing"
}

Related

  • idempotency
  • handling-errors
  • idempotency-key-reused