Let's Pizza Developersv1.0.0

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#

  1. Your system → Let's PizzaA write with an Idempotency-Key
  2. Let's Pizza → Your systemConnection dropped: did it land?
  3. Your system → Let's PizzaLook it up firstGET /partner/v1/orders/{id}
  4. Your system → Let's PizzaIf not applied: resend, same key

The rules#

  1. Send a stable Idempotency-Key per operation (from your own id) and reuse it on every attempt.
  2. Retry only when retryable is true, or after a network failure.
  3. Back off with a little jitter: 1 s, 2 s, 4 s… up to a minute, then alert your team.
  4. Honour Retry-After on 429.
  5. 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.