Book a demo

Guides

IdempotencyRoadmap

Idempotency keys aren't available yet. Here's what's planned, and how to retry creates safely today.

Roadmap

Idempotency keys are not in the current release. This page describes what's planned, and how to avoid duplicate confirmations until then.

Why it matters

A duplicate confirmation means the customer gets two emails, two texts and possibly two calls about the same sofa. If a create request times out, you can't tell whether it was created, so a blind retry risks exactly that.

What's planned

Send an Idempotency-Key header, any unique string up to 255 characters, with POST /v1/confirmations. If the same key arrives again within 24 hours, the API returns the original response instead of creating a second confirmation. A different body with the same key will be rejected with a 409.

Retrying safely today

externalId is stored and returned, but the API doesn't check it for duplicates. So:

  1. Store the id from every 201 against your order before doing anything else.
  2. On a timeout or 5xx, don't retry straight away. List recent confirmations and look for one with your externalId.
  3. If it's there, save its id and carry on. If it isn't, create it again.
  4. If you created a duplicate by mistake, cancel the newer one before its first step goes out. On the standard cadence you have until three days before the delivery.

Advance and cancel are safe to retry already: repeating them on a confirmation that's moved on returns a 409 and changes nothing.

Base URL https://api.anyonein.co.uk/v1 is a placeholder until the production domain is confirmed. Found a mistake? Tell us.