API reference
Idempotency and External Orders
Retry the same intended fulfillment without creating another sale or entitlement.
Partner fulfillment requires a key
POST partner /orders and /sales require Idempotency-Key. Keep the same key and same payload when retrying the same intended operation after a timeout. A stored matching response is replayed; reusing the key with different data returns IDEMPOTENCY_CONFLICT (409).
The service also checks the external order reference. Do not generate a new external order ID simply because the response was lost. Test orders use their separate test idempotency context.
Not every write has the same contract
An Idempotency-Key header does not make an arbitrary API write safe. Follow the endpoint-specific behavior. Verify whether the original operation completed before replaying a refund, access change, email send, or payment action.
Keep order/customer context private and use stable internal references in diagnostics. Idempotency does not override product assignment, partner scope, or customer ownership checks.