The tickets (attendees) with their check-in state

GET https://api.app2email.com/v1/{number}/tickets/issued
scope: tickets:manage sandbox: reads MCP: list_tickets

Scope: tickets:manage. One row per ticket, by id, with the holder, the seat, the price, the check-in state and the buyer. event_id, date_id or order is needed (400 invalid_ticket_order without one). Left out, status gives the valid and the blocked tickets and role the admission tickets (addon: the extras, all: both). checked_in=true gives who is in, checked_in=false who has not come yet. Page with next_cursor.

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

  • event_id integer

    The tickets of this event (its id).

    e.g. 12
  • date_id integer

    The tickets of this date (its id).

    e.g. 31
  • type_id integer

    Only this ticket type (its id).

  • order string

    The tickets of this order: its id or its reference (TK-XXXXXX).

    e.g. TK-7H3KQ9
  • status string

    Only tickets in this state. Left out: valid and blocked.

    validblockedrefundedcancelledtransferred
  • checked_in boolean

    true: only tickets that were used at the door. false: only the ones that were not.

  • role string default ticket

    Default ticket.

    ticketaddonall
  • q string

    Search in the holder's or the buyer's name, the reference or a seat label (2 to 80 characters).

  • limit integer 1–200 default 50

    How many (1 to 200, default 50).

  • cursor string

    The next_cursor of the previous answer, unchanged. Leave out for the first page.

Responses

200 The tickets.
Fields
  • success boolean
  • request_id string
  • tickets object[]

    By id, each with buyer.

    29 item fields
    • id integer

      The ticket's id.

      e.g. 501
    • order_id integer
      e.g. 8812
    • e.g. TK-7H3KQ9
    • event_id integer
      e.g. 12
    • date_id integer

      The date the ticket is for.

      e.g. 31
    • type_id integer
      e.g. 44
    • type_name string

      The ticket type's name as it was sold.

      e.g. Adult
    • role string
      ticketaddon
    • seq integer

      1..n inside the order.

    • status string

      valid and blocked tickets hold a place; refunded, cancelled and transferred (passed on) are final.

      validblockedrefundedcancelledtransferred
    • holder_name string
    • answers object any keys

      The answers given for this ticket: question id -> value.

    • seat object | null

      null without a seat.

      6 fields
      • key string

        The key of the seat in the seat plan.

      • label string
        e.g. Stalls, Row C, Seat 7
      • section string
      • row string
      • seat string
      • table string
    • admits integer
    • check_in object

      The check-in state of a ticket.

      7 fields
      • people integer

        People admitted so far (0 to admits). Above 0 = checked in.

      • inside integer

        People inside now, for events that count people leaving.

      • entries integer

        Accepted scans on the way in.

      • first_at string (date-time) | null
      • last_at string (date-time) | null
      • last_out_at string (date-time) | null
      • gate string

        The id of the entrance of the last scan.

    • currency string
    • price number

      What was paid for this ticket, all in: what a refund of it returns.

    • price_label string
    • face number

      The all-in list price before a discount.

    • refunded number
    • refunded_at string (date-time) | null
    • block_reason string

      Why staff blocked it. A disputed payment reads Payment disputed.

    • passed_on boolean

      true: the ticket was made when a holder passed a ticket on.

    • replaces_id integer

      The ticket this one replaced. 0 = none.

    • The ticket that replaced this one. 0 = none.

    • page_url string

      The ticket page of this ticket. Anyone who has the link can open the ticket: treat it like a password and give it only to the buyer. Empty in webhook events, for an erased order and for a ticket that is no longer valid.

    • created string (date-time)
    • updated string (date-time)
    • buyer object

      Only in the rows of GET /tickets/issued: who bought it.

      3 fields
  • next_cursor string | null

    Pass it as cursor for the next page. null on the last page.

  • count integer

    How many rows this answer has.

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.