Order Email Data (Standard Context)

Order confirmations, resends, refunds, membership emails and Email ALL Attendees messages all use the order context ({{context}} = order_context). This article covers where to view an order's data, how to open it step by step, and a reference for every order, event, session, ticket, flow, payment and membership field.

Where to find it

https://<web domain>/api/ticket_order/<order id>/context.

Required access: Portal Admin

View an order's data

Open the order — in the CMS, go to Orders and open the order.
Select View tickets — from the order's ⋮ menu, then copy the URL. It looks like https://demo.web.d1tix.com/ticket_order/019a16a6-74f7-fbbd-b910-319e50ac4397.
Add /api and /context — https://demo.web.d1tix.com/api/ticket_order/019a16a6-74f7-fbbd-b910-319e50ac4397/context.
Find the field you need — match it to the tables below. A field that is missing from the page has no data for that order.

Reference

How the data is nested

An order holds events. Each event holds sessions, and each session holds tickets. Flow orders add a flows list that groups the same events by flow.

order
├─ flows[] (flow orders only)
│ └─ event_templates[] events bought through this flow
├─ event_templates[] every event in the order
├─ direct_event_templates[] events bought outside a flow
│ └─ event_sessions[]
│ ├─ tickets[]
│ └─ tickets_summary[]
├─ cart_fees[]
├─ payments[]
├─ portal, seller, gateway
└─ membership (membership orders only)

All three event lists contain the same event fields. Use {{#each event_templates}} to list every event. Use {{#each flows}} and {{#each direct_event_templates}} to show flow items and other items separately.

Order fields

Field	Description	Example
`ticket_order_id`	The order's unique ID, also found in the View tickets URL	`019a16a6-74f7-…`
`ticket_order_number`	Customer-facing order number	`HY9-CLL-8KYX`
`cart_id`	ID of the cart the order came from. The CMS shows the first 8 characters as the cart number	`d1530476-12b5-…`
`scan_code`	Order number in barcode format	`HY9CLL8KYX`
`qr_code_base64`	QR code image for the order. Use it as an `<img src>`	—
`context`	Always `order_context`	`order_context`

Purchaser fields

Field	Description	Example
`identity_id`	The purchaser's account ID	`01a1a34b-…`
`identity_name`	Full name	`Jamie Rivera`
`identity_first_name`	First name	`Jamie`
`identity_last_name`	Last name	`Rivera`
`identity_email`	Email address	`jamie@example.com`
`identity_provider`	Sign-in provider	`tix`
`identity_meta.<field>`	Fields collected at checkout: `address`, `address_more`, `city`, `state`, `zip_code`, `country`, `phone`, `newsletter`. Only filled fields appear

Flow fields (flows[])

Field	Description	Example
`flow_id`	The flow's unique ID	`01a0d076-…`
`flow_name`	Flow name	`Zoo Keepers in Training`
`flow_description`	Flow description, including its HTML. Use triple braces, `{{{flow_description}}}`, to keep the formatting	—
`event_templates[]`	Events bought through this flow, with the event fields below	—

Event fields (event_templates[], direct_event_templates[], flows[].event_templates[])

Field	Description	Example
`event_template_id`	The event's unique ID, found in the event's CMS URL	`257a8a02-…`
`event_template_name`	Event name	`Garden Admission`
`event_template_category`	Event category	`Admission`
`venue_name`	Venue name	`Ticketure Garden`
`venue_address`	Venue address	`7512 Garden Way`
`scan_code`	Order scan code plus the first 8 characters of the event ID	`HY9*CLL8KYX\|257a8a02`
`qr_code_base64`	QR code for the event	—
`purchased_on`	Purchase date and time, formatted	`Thursday, Nov 12 2026 - 11:54am`
`purchased_on_raw`	Purchase date and time, unformatted. Use it with a date helper to change the format	`2026-11-12T11:54:55-08:00`
`event_template_meta.<field>`	Event images: `image_cover`, `image_cover_alt_text`, `image_profile`, `image_profile_alt_text` and their size and cropping settings. Empty when the event has no images
`additional_info`	Answers to the event's questions, grouped by ticket group name. A group with no answers is empty	`Campers.child_name` = `Cameran`
`event_sessions[]`	The sessions booked for this event	—

Session fields (event_sessions[])

Field	Description	Example
`scan_code`	Order scan code plus the first 8 characters of the session ID	`HY9*CLL8KYX~70a037a3`
`qr_code_base64`	QR code for the session	—
`start_time`	Start time	`8:00am`
`start_datetime`	Start date and time, formatted	`Wednesday, Nov 18 2026 - 8:00am`
`start_datetime_raw`	Start date and time, unformatted	`2026-11-18T08:00:00-08:00`
`end_datetime_raw`	End date and time, unformatted	`2026-11-18T20:00:00-08:00`
`tickets[]`	One row per ticket	—
`tickets_summary[]`	One row per ticket type, with counts and totals	—

Ticket fields (tickets[])

Field	Description	Example
`ticket_id`	The ticket's unique ID	`01a1d153-0520-…`
`scan_code`	The ticket's 10-character scan code, shown under each ticket on the order page	`4K9EPTS9MB`
`qr_code_base64`	QR code for the ticket	—
`ticket_holder_name`	Name entered for this ticket. Uses the purchaser's name if none was entered	`Jamie Rivera`
`ticket_holder_email`	Email entered for this ticket. Only appears when one was entered	—
`ticket_type_name`	Ticket type	`Member Adult`
`ticket_group_name`	Ticket group	`Member Admission`
`handler`	Kind of item: `tickets`, `codes`, `passes` or `membership`	`tickets`
`state`	`booked` (not yet used), `redeemed` (scanned), `void` (invalidated) or `cancelled` (refunded)	`booked`
`ticket_currency`	Currency	`USD`
`ticket_price`	Price before discounts	`100.00`
`ticket_adjusted_price`	Price after discounts	`100.00`
`valid_from` / `valid_to`	When a pass becomes valid and expires, formatted. `N/A` for timed tickets	`Friday, Feb 20 2026 - 8:48am`
`valid_from_raw` / `valid_to_raw`	The same dates, unformatted. Passes only	`2027-02-28T23:59:59-05:00`
`ticket_group_meta`	Custom fields set on the ticket group	—

Ticket summary fields (tickets_summary[])

Field	Description	Example
`count`	Number of tickets of this type, not the order total	`1`
`ticket_type_name`	Ticket type	`Camper`
`ticket_group_name`	Ticket group	`Campers`
`flow_name`	The flow these tickets were bought through. Flow orders only	`Zoo Keepers in Training`
`currency`	Currency	`USD`
`single_price` / `single_adjusted_price`	One ticket, before and after discounts	`100.00`
`row_price` / `row_adjusted_price`	All tickets of this type, before and after discounts	`100.00`

Price fields

When an event sends its own email, these totals cover that event only. Fee fields appear only when the order has that fee.

Field	Description	Example
`before_adjustments_price`	Order total before discounts	`500.00`
`total_adjustments`	Total discounts	`0.00`
`before_fees_price`	Order total before fees	`500.00`
`total_inside_percent_fees`	Percentage fees included in the ticket price	`75.00`
`total_outside_fees`	All fees added on top of the ticket price	`25.00`
`total_outside_percent_fees`	Percentage fees added on top	`25.00`
`total_outside_fixed_fees`	Fixed fees added on top	`0.00`
`total_cart_fees`	Cart fees, such as a handling fee	`2.50`
`total_cart_fees_face`	Cart fees before discounts	`2.50`
`total_price`	Order total	`527.50`
`total_payments`	Amount paid	`527.50`

Cart fee fields (cart_fees[])

Field	Description	Example
`name`	Fee name	`Handling Fees`
`ticket_type_name`	Fee label as set on the fee	`Handling Fee`
`face_amount`	Fee before discounts	`2.50`
`amount`	Fee charged	`2.50`
`currency`	Currency	`USD`

Payment fields

Field	Description	Example
`gateway.name`	Payment gateway	`stripe`
`gateway.receipt`	Gateway receipt details, when the gateway provides them	—
`payments[].occurred_on_raw`	Payment date and time, unformatted	`2026-11-12T11:58:57-08:00`
`payments[].name`	Payment method name	`stripe`
`payments[].action`	`capture` (payment) or `refund`	`capture`
`payments[].amount`	Amount	`527.50`
`payments[].identifier`	Card brand and last 4 digits. Card payments only	`Visa …4242`
`payments[].payment_method_type`	Payment type	`card`
`discounts`	Checkout rules and discount codes applied. Empty when there are none	—

Portal and seller fields

Field	Description	Example
`portal.name`	Portal name	`Team Knowledge Enablement`
`portal.domain`	Portal web domain	`teamke.web.use2.ticketuretest.com`
`portal.slug`	Portal identifier	`teamke`
`seller.name`	Seller name	`Garden`
`seller.slug`	Seller identifier	`garden`
`seller.meta.<field>`	Seller settings, such as `image` (the seller logo)	`{{seller.meta.image}}`

Membership fields (membership, membership orders only)

Field	Description	Example
`scan_code`	Member ID	`1234516`
`qr_code_base64`	QR code for the membership	—
`program`	Membership event name	`Botanic Garden Membership`
`role`	Membership level	`Individual Membership`
`expiry_raw`	Expiry date, unformatted	`2027-11-30T23:59:59-08:00`
`programs[]`	Every membership the member holds, each with `program`, `role`, `expiry_raw` and `auto_renew_on` (`true` or `false`)	—

Best practices

Use the _raw dates for custom formats. The formatted dates can't be changed. The _raw versions work with date helpers.
Use direct_event_templates with flows to avoid listing items twice. event_templates already includes the flow items.
Use triple braces for HTML fields. {{{flow_description}}} keeps bold text and line breaks. Double braces show the tags as text.
Check handler before showing pass dates. Timed tickets show N/A for valid_from and valid_to.

Order Email Data (Standard Context)

This article lists every field in the order context, including the new flow and cart-fee fields, and how to view them for a real order.

Where to find it

View an order's data

Reference

Best practices