Skip to main content
Generation submissions accept an optional Idempotency-Key header. Use it when a network failure or timeout leaves you unsure whether a request was accepted. Generate one unique key for each intended generation and keep it until you receive the initial response:
If the response is lost, repeat the same request with the same key. Higgsfield returns the original request_id without creating or charging for another generation.

​
Key rules

  • Keys must contain 1–255 visible ASCII characters without whitespace. UUIDs are recommended.
  • A key identifies one generation intent within your account. API key rotation does not change that identity.
  • Reuse the key only when the endpoint, JSON body, and webhook are unchanged.
  • JSON object field order does not matter. Array order, omitted fields, explicit null values, and different URLs do matter.
  • A completed, failed, NSFW, or canceled request keeps its identity. Retrying does not restart it.
  • A request rejected before acceptance, such as an authentication or validation failure, does not consume the key.
Create a new key when you deliberately want a new generation, even if its parameters are identical to an earlier request.

​
Parameter mismatch

Reusing a key with different request parameters returns 422 Unprocessable Entity:
Do not handle this response by generating a new key automatically. First determine whether the changed request represents a deliberate new generation or a client bug.

​
Retry after an ambiguous failure

  1. Create the key before sending the generation request.
  2. Store the key with your local operation or job record.
  3. After a network error, timeout, or 5xx, retry the same endpoint and parameters with the same key.
  4. Store the returned request_id and use its status_url for subsequent checks.
The replay response is an acceptance receipt and can contain "status": "queued" even when the original request has already finished. Read status_url for its current status and output. Idempotency keys apply to generation submission endpoints in the Model API reference. Status polling, cancellation, uploads, estimates, and webhook deliveries use their existing retry behavior.