ticket.checked_in

Send this to my URL
Tickets-and-Pay X-App2email-Event: ticket.checked_in

A ticket was admitted for the first time (not for a re-entry, a check-out or a refused scan). page_url is empty in events: read the order with GET /tickets/orders/{id}.

data

  • ticket object required

    One ticket (or one extra) of an order, with its check-in state. The ticket code, the text of its QR code, is never in an answer. Also inside ticket.checked_in and ticket.passed_on, there with an empty page_url.

    29 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
  • order object required
    2 fields
    • id integer

      The order's id.

      e.g. 8812
    • reference string
      e.g. TK-7H3KQ9
  • check_in object required
    6 fields
    • id integer

      The check-in's id.

    • at string (date-time)
    • people integer

      People admitted by this scan.

    • gate string

      The id of the entrance.

    • method string

      How it was scanned, eg camera, list or api.

    • by string

      Who scanned.

  • timestamp string (date-time) required

Inside the envelope {id, type, created, number, test?, data}: envelope, headers, signature.

Caused by

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.