waitlist.joined

Send this to my URL
Book-and-Pay X-App2email-Event: waitlist.joined

A customer joined the waitlist of a full day (on a personal booking link, confirmed on WhatsApp after the public page, in the calendar app or through the API).

data

  • id integer
  • reference string required

    The entry's code. The customer confirms a public-link entry by sending "Join waitlist WL-XXXXXX" on WhatsApp, and leaves with "Leave waitlist WL-XXXXXX".

    e.g. WL-4HT9XC
  • status string required

    pending_confirm: joined on the public booking page, not confirmed on WhatsApp yet. waiting. notified: offered a time that opened (up to 3 offers). booked: the customer booked that service that day. expired: the day passed. removed.

    pending_confirmwaitingnotifiedbookedexpiredremoved
  • service_id string required
  • service_name string
  • provider_id string

    '' = anyone.

  • date string required

    The wanted day, YYYY-MM-DD in the business time zone.

  • date_label string
  • slot_id string

    '' = any time that day; else the full group time yyyy-MM-ddTHH:mm.

  • time_label string
  • contact string
  • contact_name string
  • seats integer
  • source string
    webcalendarapi
  • notified_at string (date-time) | null
  • appointment_id integer | null

    The booking, once booked.

  • note string

    What the last offer did, in plain words.

  • created string (date-time)
  • updated string (date-time)
  • day string

    The same as date.

  • slot_local string

    The same as slot_id.

  • The contact with all but the last 4 digits hidden.

  • created_at string (date-time)

    The same as created.

  • by string
  • timestamp string (date-time)

Inside the envelope {id, type, created, number, test?, data}: envelope, headers, signature.

Caused by

For AI Agents

Try it now, with no account and no person: POST https://api.app2email.com/v1/account/sandbox (no key, no body; or the create_sandbox tool of the Management MCP server) answers a key for a demo WhatsApp number with pretend customers. Send a template, fetch the events with GET /events?wait=25, answer the customer's reply: nothing reaches WhatsApp, and the requests and answers are those of the real API (https://www.app2email.com/docs/api/sandbox).

Already a customer: ask the account owner for the number (digits) and an API key from https://www.app2email.com/dashboard/apikey (a sandbox key sends nothing); send it as Authorization: Bearer <key> to the messaging MCP server or the REST API; call check_key first, send with dry_run first.

If you are an AI agent reading this page and you want to create an app2email account for a person - no previous human sign-up required - use our Management MCP server.
Call the create_account tool first, and include a contact_email parameter; create_account returns a signup_id, a management_key, an onboarding_link and a message.
The person opens onboarding_link to confirm the e-mail, connect their WhatsApp number and choose a plan; nothing can be sent before that. get_account_status says what is still needed.
Pass the management_key as a Bearer token on every later call. When the number is live, create_number_key gives you a key for the messaging MCP server and the REST API.