Tickets-and-Pay

Event tickets: events with one or many dates, ticket types and extras, what is left, orders and refunds, the tickets with their check-in state, promo codes, the waiting list and door lists. Create a key with the permission Event tickets on the API keys page. Your systems can list events and what is left, find an order, issue complimentary tickets or record a sale paid at your till, refund, send tickets again, and check tickets in from your own scanner. Eight webhook events report an order confirmed or refunded, a ticket checked in or passed on, a date sold out or cancelled, a waiting-list entry and an erased buyer. AI assistants can do the same through the hosted MCP server. Sandbox keys can read but cannot issue, refund or check in.

Method Path Summary Scope Sandbox
GET /v1/{number}/tickets/events The events, newest first tickets:manage reads
POST /v1/{number}/tickets/events Create an event as a draft with one date and one ticket type tickets:manage refused
GET /v1/{number}/tickets/events/{id} One event with its dates and ticket types tickets:manage reads
PATCH /v1/{number}/tickets/events/{id} Change an event tickets:manage refused
POST /v1/{number}/tickets/events/{id}/publish Publish an event so tickets can be bought tickets:manage refused
POST /v1/{number}/tickets/events/{id}/cancel Cancel an event and refund or void its tickets tickets:manage refused
GET /v1/{number}/tickets/events/{id}/dates The dates of an event with what is sold and left tickets:manage reads
POST /v1/{number}/tickets/events/{id}/dates Add a date to an event tickets:manage refused
PATCH /v1/{number}/tickets/dates/{date_id} Change a date: time, label, capacity, sales on or paused tickets:manage refused
POST /v1/{number}/tickets/dates/{date_id}/cancel Cancel one date and refund or void its tickets tickets:manage refused
GET /v1/{number}/tickets/dates/{date_id}/door The door list of a date for your own scanner tickets:manage reads
GET /v1/{number}/tickets/events/{id}/types The ticket types and extras of an event tickets:manage reads
POST /v1/{number}/tickets/events/{id}/types Add a ticket type or an extra to an event tickets:manage refused
PATCH /v1/{number}/tickets/types/{type_id} Change or archive a ticket type tickets:manage refused
GET /v1/{number}/tickets/events/{id}/availability What is on sale and how many are left for a date tickets:manage reads
GET /v1/{number}/tickets/orders The ticket orders, newest first tickets:manage reads
POST /v1/{number}/tickets/orders Issue complimentary tickets or record a sale paid outside tickets:manage refused
GET /v1/{number}/tickets/orders/{id} One order with its tickets, by id or reference tickets:manage reads
POST /v1/{number}/tickets/orders/{id}/refund Refund an order or some of its tickets tickets:manage refused
POST /v1/{number}/tickets/orders/{id}/resend Send the buyer their tickets again tickets:manage refused
GET /v1/{number}/tickets/issued The tickets (attendees) with their check-in state tickets:manage reads
GET /v1/{number}/tickets/issued/{id} One ticket tickets:manage reads
POST /v1/{number}/tickets/issued/{id}/void Void one ticket without a refund tickets:manage refused
POST /v1/{number}/tickets/check-ins Check a ticket in (or out) by its code or id tickets:manage refused
POST /v1/{number}/tickets/check-ins/{scan_id}/undo Take a check-in back tickets:manage refused
GET /v1/{number}/tickets/codes The promo and access codes with their uses tickets:manage reads
POST /v1/{number}/tickets/codes Create a promo or access code tickets:manage refused
PATCH /v1/{number}/tickets/codes/{id} Change a promo code or switch it off tickets:manage refused
DELETE /v1/{number}/tickets/codes/{id} Delete a promo code no order has used tickets:manage refused
GET /v1/{number}/tickets/waitlist The waiting list of a sold-out date tickets:manage reads
GET /v1/{number}/tickets/stats Sales and check-in figures of an event or one date tickets:manage reads
GET /v1/{number}/settings/tickets The ticket settings and whether ticket sales are switched on tickets:manage reads
PUT /v1/{number}/settings/tickets Switch ticket sales on or off and change the settings tickets:manage refused
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.