Developer documentation
Idempotency
Use one stable idempotency key for one logical write operation. A network timeout should repeat the same key—not invent a new operation identity.
Implementation guide
What the integration should preserve.
- 01
Derive the key from the logical operation, not the HTTP attempt.
- 02
Reuse it after a timeout while checking existing state.
- 03
Do not reuse one key for a different payload.
- 04
Persist the key beside your source-system record.
- 05
Handle a conflicting payload as a client defect.
Example
Idempotency-Key: erp-acme-invoice-2026-000184Continue reading