The next free start times for a service, across days

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

Scope: bookings:manage (or messages:read). Like GET /bookings/availability but without choosing days: the next count free start times after after (default now), looking at most 60 days ahead. Each slot's id is what POST /bookings, /bookings/holds and /bookings/{id}/reschedule take as start.

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

  • service_id string

    The service (GET /bookings/services).

    e.g. haircut
  • provider_id string

    One staff member's own availability. Left out: anyone available.

    e.g. maria
  • after string

    Only times after this: a day (YYYY-MM-DD, its start in the business time zone) or an ISO 8601 time. Default now.

    e.g. 2026-11-12
  • count integer 1–20 default 5

    How many slots (1 to 20).

Responses

200 The slots.
Fields
  • success boolean
  • request_id string
  • slots object[]
    6 item fields
    • id string

      Local time: what POST /bookings, /bookings/holds and /bookings/{id}/reschedule take as start.

      e.g. 2026-11-10T09:00
    • date string
      e.g. 2026-11-10
    • title string
      e.g. 9:00 AM
    • start string (date-time)
    • end string (date-time)
    • providers string[]

      The staff members free at this time, when the business has them.

  • count integer
  • timezone string
  • enabled boolean
  • note string

    Only when fewer free times than asked for exist in the next 60 days.

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.