Track your work
Use stable internal references to reconcile job creation, processing, and charges without assuming every retry is a new task.
Define what counts as the same work
Use an internal operation reference for a user’s intended submission. Do not generate a new reference merely because a transport request is retried.
Respect the server contract
Idempotency support requires documented key scope, expiry, payload matching, and replay behavior. An arbitrary client header cannot create a server-side guarantee.
Reconcile ambiguous responses
If a create request times out after reaching the server, use the documented lookup or replay mechanism. Keep the operation pending until its state can be reconciled.
Before you enable this workflow
| Confirm | Why it matters |
|---|---|
| Production contract | Use documented fields, limits, and supported operations. |
| Failure policy | Decide what the application does when a check cannot complete. |
| Data boundaries | Keep credentials and customer data out of unnecessary logs. |