The booking report of a range of days

GET https://api.app2email.com/v1/{number}/bookings/reports
scope: bookings:manage|messages:read sandbox: reads MCP: get_booking_reports

Scope: bookings:manage (or messages:read). Over the appointments whose START is in the range (days in the business time zone): totals (bookings, upcoming, completed, cancelled and by the customer, no-shows, the no-show and cancel rates, new and returning customers, revenue and refunds in minor units, the average days booked ahead, the online share), per day, per weekday and hour, per service, staff member and source, and the waitlist numbers. Revenue = online payments of those appointments, less refunds. The range: from / to (at most 366 days), or days (the last N days up to today; default 30). With days=7, 30 or 90 (or nothing) the answer also has the keys of the older report (bookings, completed, cancelled, no_shows, csat, reminders_sent, sessions, top_services, per_provider, nudges). format=csv: one line per appointment (reference, date, time, service, staff, customer name, customer phone, status, source, price, paid, add-ons, guests, series, answers); format=csv_summary: the older metric,value lines.

Path

  • number string required pattern ^[0-9]{8,15}$

    Your app2email WhatsApp number - the number the message is sent FROM. Full number with country code, digits only.

    e.g. 4976659348270

Query

  • from string

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

    e.g. 2026-11-01
  • to string

    The last day (included). With from alone: from + 29 days.

    e.g. 2026-11-30
  • days integer 1–366 default 30

    Instead of from / to: the last N days up to today (1 to 366; 7, 30 or 90 also give the older keys). Default 30.

  • service_id string

    Only this service (service is taken too).

  • provider_id string

    Only this staff member (provider is taken too).

  • format string

    csv: one line per appointment. csv_summary: the older metric,value lines.

    jsoncsvcsv_summary

Responses

200 The report.
Fields

Errors

  • 400 The request is malformed (missing or invalid fields, query parameters or times).
  • 401 Missing, invalid, revoked or expired API key.
  • 403 The key is valid but this call is not allowed: the key lacks the scope the call needs (insufficient_scope), the address is not allowed for the key (ip_not_allowed), the number or plan does not allow it, a recipient opted out or is not opted in, or a problem with the WhatsApp account.
  • 404 The number, template, message, broadcast, webhook, delivery, opt-in, logged request, booking or Flow was not found.
  • 429 A monthly plan limit, the number's own monthly cap, the key's daily cap, a WhatsApp rate limit, the API rate limit (rate_limited), or the webhook test limit (too_many_tests) was reached. Retry-After and error.retry_after_seconds say how long to wait.
  • 500 Unexpected error on app2email's side.
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.