idempotency_in_progress

What it means

A request with this `Idempotency-Key` is still executing. The retry arrived before the first attempt finished.

Common causes

• An aggressive retry fired while the original request was still being processed.

How to fix it

Wait briefly and retry with the SAME key — once the first execution finishes, the retry replays its recorded response.

Should you retry?

Yes — with the same key, after a short delay. The official SDK does this automatically.

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_key_reused — HTTP 422, Idempotency-Key reused with a different request
• internal_error — HTTP 500, Internal server error