Guides
Failures, retries and duplicates
Networks fail. The golden rule: every operation can be repeated safely, and nothing is resent before you know what happened to it.
The unclear answer#
- Your system → Let's PizzaA write with an Idempotency-Key
- Let's Pizza → Your systemConnection dropped: did it land?
- Your system → Let's PizzaLook it up first
GET /partner/v1/orders/{id} - Your system → Let's PizzaIf not applied: resend, same key
The rules#
- Send a stable Idempotency-Key per operation (from your own id) and reuse it on every attempt.
- Retry only when retryable is true, or after a network failure.
- Back off with a little jitter: 1 s, 2 s, 4 s… up to a minute, then alert your team.
- Honour Retry-After on 429.
- After a timeout with no answer: look the result up first, then resend if needed.
Duplicate events#
Webhooks arrive at least once and may arrive twice. Keep the id of every event you processed and skip repeats. Details.
Endpoints used#
Anything marked “Coming soon” is not served yet; it joins the reference as soon as it ships.