Unique order number.
Reservation ID.
Payment snapshot ID. Empty for FREE order.
Event ID.
Contact ID of buyer (resolved using email address).
Member ID of buyer (if relevant).
RSVP created timestamp.
Guest first name.
Guest last name.
Guest email.
Checkout form response. When each purchased ticket is assigned to a guest, guest forms are returned for each ticket, and buyer info is returned.
Whether the order is confirmed (triggered once payment gateway processes the payment and funds reach the merchant's account).
Order status.
Payment method used for purchase, e.g., "payPal", "creditCard", etc.
Tickets ordered.
Total order price.
URL to ticket PDF.
Tickets (generated after payment).
Whether the order is archived.
Whether the order is anonymized by GDPR delete.
Guest full name.
Order invoice.
Whether all tickets in order are checked-in.
Internal order payment details
Checkout channel type
Retrieves a list of orders, including ticket data, with basic filter support.
Permission Scopes
For app development, you must have one of the following permission scopes:Retrieves an order, including ticket data.
Permission Scopes
For app development, you must have one of the following permission scopes:Updates an order's checkoutForm and/or archived status.
Permission Scopes
For app development, you must have one of the following permission scopes:Updates multiple orders' archived status.
Permission Scopes
For app development, you must have one of the following permission scopes:Changes order status to "CONFIRMED" - from "INITIATED, "PENDING", "OFFLINE_PENDING" to "PAID". Previously confirmed orders (with status "PAID" or "FREE") are not changed. Confirming previously "INITIATED" or "PENDING" orders triggers an email with the tickets to the buyer (and to additional guests, if relevant and provided).
Permission Scopes
For app development, you must have one of the following permission scopes:Retrieves a summary of total ticket sales.
Permission Scopes
For app development, you must have one of the following permission scopes:Returns checkout meta data used in checkout UX.
Permission Scopes
For app development, you must have one of the following permission scopes:Returns tickets available to reserve.
Permission Scopes
For app development, you must have one of the following permission scopes:Returns tickets available to reserve.
Permission Scopes
For app development, you must have one of the following permission scopes:Reserves tickets for 20 minutes. Reserved tickets are deducted from tickets stock and cannot be bought by another party. When the reservation expires, the tickets are added back in the stock.
Permission Scopes
For app development, you must have one of the following permission scopes:Cancels ticket reservation and returns tickets to stock.
Permission Scopes
For app development, you must have one of the following permission scopes:Generates a preview of a reservation invoice, including the given coupon or pricing plan.
Permission Scopes
For app development, you must have one of the following permission scopes:Checkout reserved tickets. Creates order and associates it with a site contact. Guest details must be sent according to Registration Form input fields. (To change an existing "INITIATED, "PENDING", or "OFFLINE_PENDING" order, call the Update Checkout endpoint).
Permission Scopes
For app development, you must have one of the following permission scopes:Updates order and tickets (supported only for unconfirmed orders). Guest details must be sent according to Registration Form input fields.
Permission Scopes
For app development, you must have one of the following permission scopes:This event is triggered when an order is deleted via GDPR request.
Order deleted timestamp in ISO UTC format.
Event ID.
Unique order number.
Contact ID associated with this order
Member ID associated with this order.
Whether order was anonymized by GDPR delete.
Order type.
Whether event was triggered by GDPR delete request.
Tickets generated after payment.
Order updated timestamp in ISO UTC format.
Site language when Order initiated
Locale in which Order was created.
Event ID.
Unique order number.
Contact ID associated with this order.
Member ID associated with this order.
Order created timestamp.
Buyer first name.
Buyer last name.
Buyer email.
Checkout form response.
Whether order is confirmed - occurs once payment gateway processes the payment and funds reach merchant's account.
Order status.
Payment method used for paid tickets purchase, i.e. "payPal", "creditCard", etc.
Tickets generated after payment.
Whether order was archived and excluded from results.
Whether event was triggered by GDPR delete request.
Order confirmation timestamp in ISO UTC.
Site language when Order initiated
Notifications silenced for this domain event.
Locale in which Order was created.
Event ID.
Unique order number.
Contact ID associated with this order.
Member ID associated with this order.
Order created timestamp
Buyer first name.
Buyer last name.
Buyer email address.
Checkout form response.
Order status.
Payment method used for paid tickets purchase, i.e. "payPal", "creditCard", etc.
Tickets (generated after payment).
Invoice.
Reservation ID associated with this order.
Reservation created timestamp in ISO UTC format.
Event ID.
Reservation ID. Can be used to retrieve a reservation invoice.
Reservation expiration timestamp.
Reservation status.
Reservation ticket quantities.
Reservation updated timestamp.
Event ID.
Reservation ID. Can be used to retrieve a reservation invoice.
Reservation status.
Reservation expiration timestamp.
Reservation ticket quantities.
Order initiated timestamp in ISO UTC format.
Site language when Order initiated
Locale in which Order was created.
Event ID.
Unique order number.
Contact ID associated with this order.
Member ID associated with this order.
Guest first name.
Guest last name.
Guest email address.
Checkout form response.
Order status.
Invoice.
Reservation ID associated with this order.
Order was marked as paid.