ticket.event.sold_out

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

A date sold its last public ticket. Once per time it becomes sold out.

data

  • event object required
    3 fields
    • id integer

      The event's id.

      e.g. 12
    • name string
      e.g. Summer Quiz
    • slug string

      The last part of the event's address.

      e.g. summer-quiz
  • date object required

    The date, without 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.

  • sold integer required

    Valid tickets of the date.

  • 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.