idempotency_conflict (1201, HTTP 409) · TranscriptFetch API error

Idempotency-Key reused with a different body, or a request with that key is still in flight.

Number1201

HTTP status409Conflict

Familyrequest1xxx · the request itself

Example response

JSON

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "idempotency_conflict",
    "number": 1201,
    "message": "Idempotency-Key reused with a different body, or a request with that key is still in flight.",
    "docs": "https://transcriptfetch.com/docs/errors/idempotency_conflict"
  }
}

Every failure carries error.code, error.number, error.message and error.docs, plus at most one of retry_with (the request change that would succeed), details (structured specifics) or issues (validation problems).

What it means

Idempotency-Key reused with a different body, or a request with that key is still in flight.

Why it happens

An Idempotency-Key header was reused with a different request body.
A request with the same key is still in flight (a client retried before the first attempt finished).

What to do

Generate a fresh key (UUID) per logical request; reuse a key only to retry the exact same body.
If the first request is still running, wait for it to settle instead of firing a duplicate.

Retryable? Yes, with a new Idempotency-Key, or after the in-flight request completes. Every error response carries a request_id; include it when contacting support.