The free slots per day for a service, as the customer would see them

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

Scope: bookings:manage (or messages:read). Every day of the range (at most 32 days, default today + 6) with its free start times: the opening hours, the closed days, the booked appointments and the calendar's busy time applied. Each slot's id is the local time POST /bookings takes as start. With staff members, providers names who is free; provider_id asks for one member's own availability.

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 (config.services[].id).

    e.g. haircut
  • from string

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

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

    The last day (included). Default from + 6 days; at most 32 days.

    e.g. 2026-11-16
  • provider_id string

    One staff member's own availability (config.providers[].id). Left out: anyone available.

    e.g. maria
  • addons string

    A comma list of the service's add-on ids: the slots are long enough for them.

    e.g. deep,trim
  • seats integer 1–200 default 1

    The places wanted on a group time (1 + guests): only times with that many places left.

Responses

200 The days and their slots.
Fields
  • success boolean
  • request_id string
  • days object[]
    3 item fields
    • date string
      e.g. 2026-11-10
    • slots object[]

      Empty on a closed or full day.

      7 item fields
      • id string

        Local time in the business time zone: what POST /bookings takes as start.

        e.g. 2026-11-10T09:00
      • title string
        e.g. 9:00 AM
      • start string
      • end string
      • providers array

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

      • start_utc string

        The same instant as start (for showing it in another time zone).

      • seats_left integer

        A group service: the places left at this time. 0 = a full time, listed only when the service has a waitlist.

    • waitlist boolean

      true: the day has no free time and the service has a waitlist (left out otherwise).

  • timezone string
  • enabled boolean

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.