Idempotency is the property of an operation that gives the same result whether it runs once or several times, so repeating it does not create duplicates.
Integration · Reviewed by Ray Rasouli
Ask about idempotency
Plain answers, with your setup in mind.
Ask anything about idempotency. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Networks are unreliable. An integration sends "create this invoice," the connection drops, and it is unclear whether the invoice was made. If the integration retries and the operation is not idempotent, you now have two invoices and an unhappy customer.
A common fix is an idempotency key: a unique ID sent with each request. If the receiving system has already seen that ID, it returns the original result instead of doing the work again.
For a wholesaler syncing orders and payments, idempotency is what lets retries be safe, which in turn lets the integration recover from glitches on its own.
In practice
Retries create duplicate records.
Without a unique key, every timeout risks a second order, payment or shipment.
The key is not truly unique.
Using something like a date or customer name as the key causes different requests to collide.
Keys expire too soon.
Some systems only remember keys for a short window, so late retries slip through as new requests.
Webhook receivers skip the check.
Senders deliver the same event more than once, and receivers that do not track event IDs process it twice.
Anything that creates or moves money or goods, such as orders, payments, refunds and shipments.
By design, yes. Reading data should not change it, so repeating a GET is safe.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.