Retries and idempotency
Retry network failures without duplicating work.
Use an Idempotency-Key on POST /requests. Reuse the same key when retrying the same logical submission; create a new key for a genuinely new request.
Retry transient transport failures and rate limits with exponential backoff and jitter. Do not blindly retry validation errors, authentication failures, email verification errors, or expired results. Polling should also use backoff and should stop at a terminal state.
The exact retention window and plan-specific limits are deployment data. See limits for the contract-level bounds documented here.
Last updated on