Fetch e-tickets

Returns every e-ticket sold for the event, oldest change first.

Page with count (at most 5000) and last_updated_date: read the highest updated_at of a page and send it back as last_updated_date for the next one, until a page comes back short. Records are ordered by updated_at then id, so a seat never moves between pages. A count above the maximum is rejected rather than trimmed, because a trimmed page reads as a short one and would end the import early.

Each record carries:

• id, created_at, updated_at, order_id, event_id, event
• ticket_type — the name of the ticket type the seat was sold under. Replaces the former ticket key. It is the seller's editable label, not a stable identifier: renaming the ticket type changes this value.
• reference — the seat's stable identifier as a string. Survives a barcode change.
• code, barcode — barcode is the string the end devices validate. It is the seat's code, or the short ticket URL when the ticket type encodes its QR code from a URL, so prefer it over code for scanning.
• state — VALID, REDEEMED, EXPIRED, REFUNDED, INVALID or UNKNOWN
• ticket_is_valid — true only for a seat that has not been used yet. A redeemed seat reads false, so re-entry is refused; state says why.
• personalisation_status — unassigned, pending, queued, sent, personalised or transferred. The seat's current state; transferred wins over the stored status once the seat has been handed to someone else.
• personalisation_complete — true once the seat's stored personalisation status is personalised. It reads the stored status, not the derived one above, so a seat that was personalised and then handed on stays true while the status reads transferred.
• ticket_qr_code, ticket_qr_code_short, payer_data
• ticket_attendee — id, first_name, last_name, salutation, email, phone, street, zip_code, city, country_code, country_name, plus the four fields below. Null for a seat that has no attendee yet.

created_at and updated_at are ISO 8601 timestamps carrying microseconds and a time zone. updated_at is the record's update date, not the seat row's: it moves when the seat, its attendee or that attendee's visa data changes, so a renamed attendee brings the record back on the next page. Page on this value and nothing the payload carries is missed.

The attendee fields company, role (the job title; the seller configures this field as "Role"), gender and date_of_birth are always present. Each reads null when the seller's payment page template does not collect it for that ticket, so the record has the same shape whatever the seller configured. gender is one of male, female, other, prefer_not_to_say. date_of_birth is an ISO 8601 date, YYYY-MM-DD.

The attendee visa object — needs_letter, nationality_code, passport_number — requires the visa-data permission, which is held by the seller who owns the event. An API key authenticates as that seller, so a caller reaching this endpoint holds the permission and the object is present. A caller who does not hold it gets no visa key on any record. The key is also absent for a ticket that does not have visa sponsorship enabled. Every response that carries it is recorded in the visa access log against the seller.