The door list of a date for your own scanner

GET https://api.app2email.com/v1/{number}/tickets/dates/{date_id}/door
scope: tickets:manage sandbox: reads

Scope: tickets:manage. For a scanner of your own. Each ticket of the date comes with code_sha256, the lower-case hex SHA-256 of the text in its QR code: hash what you scan and look it up, so the codes themselves never leave app2email. No contact, email or money is in the list. The first calls page through the date (while more is true, send cursor as since); later the same call with the last cursor answers only what changed, and gone lists the ids that are no longer tickets of this date. Record an admission with POST /tickets/check-ins.

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
  • date_id string required

    The date's id.

    e.g. 31

Query

  • since string

    The cursor of an earlier answer. Left out: from the start.

    e.g. u1793926800000000.502
  • limit integer 1–2000 default 2000

    How many (1 to 2000, default 2000).

Responses

200 The door list.
Fields
  • success boolean
  • request_id string
  • date object

    The date, without the five counts.

    18 fields
    • id integer

      The date's id.

      e.g. 31
    • event_id integer

      The event it belongs to.

      e.g. 12
    • start string (date-time)

      When it starts (UTC).

    • end string (date-time)

      When it ends (UTC).

    • start_local string

      The start as clock time in the event's time zone (yyyy-MM-ddTHH:mm).

      e.g. 2026-12-12T19:30
    • end_local string

      The end as clock time in the event's time zone.

      e.g. 2026-12-12T21:30
    • label string

      A short name of the date, eg Late show. Empty when it has none.

    • capacity integer | null

      How many people fit: the date's own limit, else the event's; with a seat plan the places of the plan. null = no limit.

    • sales string

      paused: nothing is sold for this date right now.

      onpaused
    • status string
      scheduledendedcancelled
    • sold integer | null

      Valid tickets (extras not counted). The five counts sold, people, held, left and checked_in are null inside webhook events, in the door list and in next_date of the events list.

    • people integer | null

      The people those tickets admit (a group ticket admits several).

    • held integer | null

      People in baskets right now.

    • left integer | null

      People that can still be sold. null = no limit, or the counts were not read.

    • checked_in integer | null

      People admitted at the door.

    • sold_out boolean

      The date sold its last public ticket and no place has come back since.

    • changed string (date-time) | null

      When the time or the venue last changed and ticket holders were told.

    • cancelled string (date-time) | null

      When the date was cancelled.

  • counts object

    People: sold, inside or admitted, still to come.

    3 fields
  • tickets object[]

    One row per ticket. After a since, also tickets that stopped being valid: their status says so.

    15 item fields
  • gone integer[]

    Ids that are no longer tickets of this date since since: moved to another date, or erased.

  • cursor string

    Send it as since: for the next page while more is true, later for what changed.

  • more boolean

    Another page is waiting now.

  • count integer

    How many rows this answer has.

  • note string

    Only for a date with more than 20,000 tickets: its door list is not sent.

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.