idempotency_key_reused

What it means

An `Idempotency-Key` header was reused with a DIFFERENT request body or endpoint than its first use. A key maps to exactly one logical request.

Common causes

• A key-generation bug that reuses keys across distinct operations.
• The request body changed between retries (timestamps, random ids) so the retry no longer matches byte-for-byte.

How to fix it

Mint one unique key per logical operation and reuse it ONLY for byte-identical retries of that operation.

Should you retry?

No — use a fresh key for the new request.

The response shape

Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.

API overview · API reference · All error codes:

• missing_credentials — HTTP 401, Missing credentials
• invalid_api_key — HTTP 401, Invalid API key
• invalid_token — HTTP 401, Invalid access token
• unsupported_credential_type — HTTP 403, Credential type not usable on this surface
• insufficient_scope — HTTP 403, Insufficient scope
• feature_not_enabled — HTTP 403, Feature not enabled on this plan
• validation_failed — HTTP 400, Request validation failed
• resource_not_found — HTTP 404, Resource not found
• rate_limited — HTTP 429, Rate limit exceeded
• quota_exhausted — HTTP 429, Plan quota exhausted
• idempotency_in_progress — HTTP 409, A request with this Idempotency-Key is still in progress
• internal_error — HTTP 500, Internal server error