gensta DOCS
api-platform.gensta.ai/v1 Developer portal
DocsIdempotency and safe retries

Idempotency and safe retries

The header is optional, but it is the only safe way to retry a create request after an ambiguous network failure.

Key behavior

http
Idempotency-Key: order-8493-shot-1

A key is 1–255 visible ASCII characters and unique inside one API project. Generate it for one logical generation and persist it with your own job record.

RetryResult
Same key + same bodyThe original response is replayed with Idempotent-Replayed: true
Same key + different body409 idempotency_conflict
No keyEvery POST creates a new paid generation

Retry decisions

  • After a 202, save the ID and poll it; do not create a replacement.
  • If the POST response is lost, resend the exact body with the exact same key.
  • If the original POST had no key, do not retry automatically. Reconciliation is safer than a duplicate charge.
  • GET requests are safe to retry. Increase the interval after network or 5xx errors.

Unknown submission status

For submission_unknown, do not submit a replacement with a new key: the first generation may already be accepted and billable.