Skip to main content
Send an Idempotency-Key header with every write request, including checkout link creation and sandbox-promotion plan, apply, and rollback requests:
Batch Relay stores the first result for that operation and credential scope. Order replays return the original order record. Checkout-link replays return the same lifecycle record, but never repeat a Live Mode bearer share_url. Checkout-link creation fingerprints the request: the same key with different recipient, sellable, quantity, expiry, customization, asset, or digital configuration input returns 409 checkout_link_conflict rather than changing the existing link. Use a stable value from your system:
  • Order ID
  • Workflow run ID
  • External job ID
  • n8n execution ID plus item ID
Do not reuse the same idempotency key for different payloads. For a sandbox promotion, preserve the supplied key if the network result is ambiguous. A plan, apply, or rollback key belongs to that exact operation and payload. Do not reuse it across the three actions or replace it while retrying.