idempotency-conflict

idempotency-conflict

HTTP 409 Conflict
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/idempotency-conflict",
  "title": "...",
  "status": 409,
  "detail": "...",
  "requestId": "req_01J..."
}

This Idempotency-Key was already used with a different request body. The cache detects this via a hash of the body — same key + same body would have replayed the cached response instead.

Common causes

• Reusing a key for a genuinely different message
• A non-deterministic body (e.g. an embedded timestamp) making byte-identical retries impossible

How to fix it

Use a key that identifies the logical operation (statement id, file hash) and keep retry bodies byte-identical. See Idempotency.

Does it bill?

No. See Test vs Live Keys for the full billing rules.

Related

• Errors Overview — the problem+json shape and the closed catalog
• Every response carries an X-Request-Id; quote it when contacting support.