Event Dates API

Read a single event date, list the orders placed against it, and get a one-row sales-and-attendance summary so dashboards don't have to total every order themselves.

An event date is a single performance or session. From a date you reach the orders placed against it, and a ready-made summary of its sales and attendance. All endpoints require the read scope and are scoped to your organisation.

Method	Path	Returns
GET	`/v1/dates/{id}`	A single event date, with its event name and information text.
GET	`/v1/dates/{id}/orders`	A paginated list of orders for the date, with money totals.
GET	`/v1/dates/{id}/summary`	A single rollup row of sales and attendance for the date.

Get one date

curl "https://developer.seaty.co.uk/v1/dates/5567" \
  -H "Authorization: Bearer sk_live_your_key_here"

Field	Type	Description
`id`	integer	The date id.
`event_id`	integer	The parent event.
`date`	string	Start date and time (ISO 8601).
`end_date`	string \| null	End date and time, if set.
`time_type`	integer	How the time is interpreted.
`name`	string \| null	An optional performance name.
`sold_out`	boolean \| null	Whether the date is sold out.
`suspend`	boolean \| null	Whether sales are suspended.
`event_tag`	string \| null	The parent event's slug.
`event_name`	string \| null	The parent event's name.
`information_header`	string \| null	Optional information header shown to buyers.
`information`	string \| null	Optional information body shown to buyers.

List a date's orders

curl "https://developer.seaty.co.uk/v1/dates/5567/orders?per_page=50" \
  -H "Authorization: Bearer sk_live_your_key_here"

Each order carries the buyer details and the full money breakdown:

Field	Type	Description
`id`	integer	The order id. Use it with the Orders endpoints.
`order_guid`	string \| null	The order's public reference.
`date`	string	When the order was placed (ISO 8601).
`email`	string \| null	The buyer's email.
`attendee_name`	string \| null	The attendee name on the order.
`event_date_id`	integer	This date's id.
`allow_marketing`	boolean \| null	Whether the buyer consented to marketing.
`ticket_count`	integer	Number of tickets on the order.
`tickets_subtotal`	integer	Sum of ticket prices, in pence.
`discount_total`	integer	Sum of order discounts, in pence.
`total`	integer	`tickets_subtotal` minus `discount_total`, in pence.
`amount_paid`	integer	Total recorded as paid (excludes refunds), in pence.
`amount_refunded`	integer	Total refunded, in pence.
`balance`	integer	`total` minus net paid. Positive means still owed; negative means overpaid.

Date summary

A single rollup row so a dashboard does not have to page through every order to total things up.

curl "https://developer.seaty.co.uk/v1/dates/5567/summary" \
  -H "Authorization: Bearer sk_live_your_key_here"

{
  "event_date_id": 5567,
  "orders_count": 142,
  "tickets_sold": 380,
  "gross": 456000,
  "discounts": 12000,
  "net": 444000,
  "amount_paid": 430000,
  "amount_refunded": 6000,
  "checked_in_count": 312
}

Field	Type	Description
`event_date_id`	integer	The date this summary is for.
`orders_count`	integer	Number of orders on the date.
`tickets_sold`	integer	Number of tickets sold.
`gross`	integer	Sum of ticket prices, in pence.
`discounts`	integer	Sum of order discounts, in pence.
`net`	integer	`gross` minus `discounts`, in pence.
`amount_paid`	integer	Total recorded as paid on order-linked payments, in pence.
`amount_refunded`	integer	Total refunded on order-linked payments, in pence.
`checked_in_count`	integer	Number of tickets scanned in for the date.

Note on amount_paid: it counts payments linked to specific orders. Event-level balance payments recorded against a payee email (rather than a single order) are not attributed to a date in this figure.

Orders: the tickets, payments and discounts on a single order.

Need help? Email support@seaty.co.uk.

Get one date

List a date's orders

Date summary

Next