booking.note.created

Send this to my URL
Book-and-Pay X-App2email-Event: booking.note.created

An internal note was added to a customer or an appointment (in the calendar app or through the API).

data

  • id integer required
    e.g. 7
  • contact string required

    The customer.

    e.g. 61412345678
  • appointment_id integer | null

    The appointment it was written on. null: a note on the customer alone.

  • booking_reference string | null
    e.g. BK-7Q3M2A
  • body string required

    Up to 4000 characters.

  • author string

    A person's name or e-mail, or API key <name>.

    e.g. API key Planner
  • author_kind string
    userapiagentsystem
  • pinned boolean
  • created string (date-time)
  • updated string (date-time)
  • Only in GET /bookings/{id}/notes: written on that appointment (false: another note of the same customer).

  • booking object | null

    The appointment the note is on. null: a note on the customer alone.

    2 fields
  • 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.