Cart Email Data (Cart Context)

Cart summary and invoice emails use the cart context ({{context}} = cart_context), which is set up differently from the order context. Field names are shorter and grouped by object, for example cart.number, not ticket_order_number. This article covers where to view a cart's data, how to open it step by step, and a reference for every cart field.

Where to find it

https://<CMS domain>/api/cart/<cart id>/context.

Required access: Portal Admin. Use the CMS domain, not the web domain.

View a cart's data

Open the cart — in the CMS, open the cart. The page title shows the cart number, for example Cart #D154156B. The URL looks like https://demo.cms.d1tix.com/aquarium/cart/f1202584-e391-f185-d27b-b83d485c0190.
Change the path — replace /aquarium/cart/ with /api/cart/ and add /context at the end: https://demo.cms.d1tix.com/api/cart/f1202584-e391-f185-d27b-b83d485c0190/context.
Find the field you need — match it to the tables below.

Reference

How the data is nested

cart
├─ cart, totals, identity, portal, seller
├─ event_templates[]
│ ├─ venue, meta
│ └─ event_sessions[]
│ └─ tickets[] (one row per ticket type)
├─ payments[]
├─ scheduled_payments[]
└─ cartmods[]

Cart fields (cart)

Field	Description	Example
`cart.id`	The cart's unique ID, found in the cart's CMS URL	`d154156b-f6bd-…`
`cart.number`	Cart number shown in the CMS	`D154156B`
`cart.state`	`booked` (paid in full), `pending` (balance due) or `expired` (past its expiry date)	`pending`
`context`	Always `cart_context`	`cart_context`

Totals (totals)

Field	Description	Example
`currency`	Currency	`USD`
`face_value`	Cart total before discounts	`0.00`
`adjustments`	Total discounts	`0.00`
`adjusted_value`	Cart total after discounts	`0.00`
`inside_percent_fees` / `inside_fixed_fees`	Fees included in the price, percentage and fixed	`0.00`
`outside_percent_fees` / `outside_fixed_fees`	Fees added on top, percentage and fixed	`0.00`
`price`	Cart total	`0.00`
`payments`	Amount paid so far	`0.00`
`scheduled_payments`	Total of upcoming scheduled payments	`0.00`
`unpaid`	Balance due	`0.00`

Purchaser fields (identity)

Field	Description	Example
`identity.id`	The purchaser's account ID	`01a1a34b-…`
`identity.name`	Full name	`Jamie Rivera`
`identity.email`	Email address	`jamie@example.com`
`identity.meta.<field>`	Saved account details: `address`, `city`, `state`, `zip_code`, `country`, `newsletter`. Only filled fields appear	`{{identity.meta.state}}`

Event fields (event_templates[])

Field	Description	Example
`name`	Event name	`Garden Admission`
`category`	Event category	`Admission`
`venue.name`	Venue name	`Ticketure Garden`
`venue.address`	Venue address	`7512 Garden Way`
`meta.<field>`	Event images: `image_cover`, `image_cover_alt_text`, `image_profile`, `image_profile_alt_text` and their size and cropping settings	`{{meta.image_cover}}`
`event_sessions[]`	The sessions in the cart for this event	—

Session fields (event_sessions[])

Field	Description	Example
`start_datetime`	Start date and time, formatted	`Friday, Nov 27 2026 - 8:00am`
`start_datetime_raw`	Start date and time, unformatted	`2026-11-27T08:00:00-08:00`
`end_datetime_raw`	End date and time, unformatted	`2026-11-27T20:00:00-08:00`
`tickets[]`	One row per ticket type	—

Ticket fields (tickets[])

Field	Description	Example
`count`	Number of tickets of this type	`1`
`ticket_type.name`	Ticket type	`Member Adult`
`ticket_type.description`	Ticket type description	—
`ticket_group.name`	Ticket group	`Member Admission`
`ticket_group.description`	Ticket group description	—
`currency`	Currency	`USD`
`single_price` / `single_adjusted_price`	One ticket, before and after discounts	`0.00`
`row_price` / `row_adjusted_price`	All tickets of this type, before and after discounts	`0.00`

Payment fields (payments[])

Field	Description
`action`	`capture` (payment) or `refund`
`amount`	Amount
`identifier`	Card brand and last 4 digits
`method`	Payment method
`name`	Payment method name
`occurred_on`	Payment date and time, formatted
`occurred_on_raw`	Payment date and time, unformatted

Scheduled payment fields (scheduled_payments[])

Field	Description
`amount`	Amount due
`due`	Due date, unformatted. Use it with a date helper
`note`	Note on the scheduled payment

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`

cartmods[] holds changes made to the cart. Its fields are still to be documented.

Best practices

Show the balance with totals.unpaid. Wrap it in {{#if}} so a paid cart doesn't show "0.00 due".
List scheduled payments with {{#each scheduled_payments}}. Each row has its own amount and due date.
Don't copy order fields into a cart template. Names like identity_email and ticket_type_name are blank in the cart context. Use identity.email and ticket_type.name.

Cart Email Data (Cart Context)

This article lists every field in the cart context and how to view them for a real cart.

Where to find it

View a cart's data

Reference

Best practices