Getting started

Quickstart

Get a sandbox key, create your first confirmation and receive the webhook. About 30 minutes, most of it reading.

This walks you through one confirmation end to end in the sandbox: you create it, play the customer, and receive the signed webhook your system would act on.

1. Get a sandbox key

Ask for a sandbox key and we'll send it with your webhook signing secret. Put both in environment variables on your server.

Check the key works by listing confirmations. A 200 with an empty list means you're in. A 401 means the key is wrong: see Authentication.

2. Create a confirmation

Send the customer, the order date and window, and at least one item. Use "cadence": "demo" while you're testing: the steps then run about 90 seconds apart instead of days.

The response is the new confirmation, with status: "scheduled" and its plan in steps.

Tip

Add rescheduleOptions with one or two other slots. If the customer can't make the first date, the agent offers these and books the one they pick, and the confirmation ends rescheduled instead of needing a person.

3. Play the customer

Open the sandbox console. Your confirmation's email arrives first, then the text. Reply as the customer would, in your own words:

  • "Yes, I'll be in" confirms it.
  • "I'm at work but my partner Jo will sign" confirms it with a named signer.
  • "Tuesday's no good, any chance of Thursday?" picks one of your other slots, or asks for a different day.
  • "STOP" opts them out.

Or ignore the text and answer the simulated call when it rings. If nobody answers anything, the confirmation ends unreachable a couple of minutes after the last step.

Note

In the sandbox nothing reaches a real phone or inbox, and every step has "live": false. Replying through the API is on the roadmap; for now the console is how you play the customer.

4. Receive the webhook

When there's an outcome, AnyoneIn POSTs a confirmation.updated event to your webhookUrl. Verify the X-AnyoneIn-Signature header, then act on data.status.

Your endpoint must be public and use https. For local testing, a tunnel such as ngrok or Cloudflare Tunnel works well. The full details are in Webhooks.

Going live

Before you switch to your live key:

  • Send "cadence": "standard". It's what real customers should get: email three days out, a text two days out and a call the day before, only in sensible hours.
  • Set brand on every request, so messages carry your name, colour, support email and tone.
  • Store the returned id against your order, and send your own order number as externalId.
  • Make your webhook handler safe to run twice for the same event (see handling deliveries).
  • Decide who picks up action_needed and unreachable confirmations before dispatch.

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