Reporting endpoint - Full tickets list

Overview

Organizers can now easily extract all ticket data, including ownership, for a specific event. This report is generated for a single event and aims to provide a detailed list of tickets along with comprehensive wallet owner information, including opt-in statuses.

Some business logic has been applied to the report:

Each valid ticket will correspond to one row in the report, excluding tickets with the status of 'DELETED'.
For tickets that are only INJECTED:
- If an owner account exists, full owner details are included.
- If an owner account does not exist, the report will include the email, first name, and last name from the ticket's initial owner fields.

Endpoints

The full ticket list is so crucial that we actually provide several endpoints to fetch the data in a comprehensive yet efficient manner, depending on your data analysis needs.

Multiple events - light version (default)

By default, this endpoint should be used. It returns all tickets of events happening within a given date range, but with only the common information useful to perform global analysis.

The URL of this endpoint is:

/organizer/report/events/tickets-light

Multiple events - detailed version

If you absolutely need the full ticket details with complete owner data, seating details, and metadata, for all tickets of events happening within a given date range, then the following endpoint can be used:

/organizer/report/events/tickets

The volume of data can be massive, especially if a high number of tickets are exported and if they carry several metadata (for instance when using the Custom Flow for all tickets). In those cases, please load the data incrementally using the lastUpdated* parameters.

Single event

To target tickets of a single event, use this reporting endpoint:

/organizer/report/events/{eventId}/tickets

This endpoint also returns all ticket details.

Parameters

Common parameters to all endpoints

mobileAppId (required): specify the applicable application identifier.

Where to find the Mobile App ID in Backoffice

excludeDeleted : true/false, false by default.
limit (required): maximum number of results to extract (max allowed 50’000, 100’000 for tickets-light).
lastUpdatedSince : filter data updated since the given timestamp (in UTC).
lastUpdatedBefore : filter data updated before the given timestamp (in UTC).

Multiple events - light & detailed

eventStartSince (required): list tickets of events starting from this timestamp (in UTC).
eventStartBefore (required): list tickets of events starting up to this timestamp (in UTC).
paginationKey (optional): If not provided, the first page of results is returned. Use the nextPageKey from the previous response to get the next page.

Single event

offset (required): skip the first N results (pagination).

Data returned

total

(for single event)

integer

Total number of ticket available (for pagination if needed)

pagination

(for multi-event)

pageSize

integer

Number of items returned in this page

nextPageKey

string

Key to fetch next page

result

List of tickets (less fields in the default light endpoint)

ticketId	string Ticket ID
eventId	string Event ID
organizerId	string Organizer ID
eventName	string Event Name
eventCode	string Organizer event ID
eventStartDate	string($date-time) Start date and time of the event
ownerId	string ID of the current ticket owner
ownerEmail	string Email address of the current ticket owner
ownerFirstName¹	string First name of the ticket owner
ownerLastName¹	string Last name of the ticket owner
ownerPhone¹	string Phone number of the ticket owner
ownerBirthDate¹	string($date) Birth date of the ticket owner
ownerIdNumber¹	string Identity number of the ticket owner
ownerResidenceCountry	string Country of residence of the ticket owner
ownerAllowPromoEmail¹	[...]
ownerAllowPromoThirdPartyEmail¹	boolean Indicates if the owner allows third-party promo emails
ownerAllowTracking¹	boolean Indicates if the owner consents to tracking
ticketNumber	string Ticket number
ticketBarcode¹	string Barcode of the ticket
organizerTicketId¹	string Organizer ticket ID
ticketHolder¹	{ description: Ticket holder details }
previousOwnerId	string ID of the previous owner
initialOwnerId	string ID of the initial owner
status	string Current status of the ticket
activated	boolean Indicates if the ticket has been activated
activatedDate	string The time the ticket was activated
checked	boolean Indicates if the ticket has been checked
checkedDate	string The time the ticket was checked
assigned	boolean Indicates if the ticket has been assigned
assignedDate	string The time the ticket was assigned
controlled	boolean Indicates if the ticket has been controlled
controlledDate	string The time the ticket was controlled
keptByOwnerDate	string The time the ticket was kept by owner
deliveryDate	string The time the ticket was delivered
purchaseFile¹	string Purchase file
purchaseDate¹	string Purchase date
purchasePrice¹	string Purchase price
purchaseCurrency¹	string Currency used in the ticket purchase
purchaseContingentId	string Purchase contingent ID
purchaseContingentName:	string Purchase contingent name
purchaseSeatCategoryId¹	string Purchase seat category ID
purchaseSeatCategoryName	string Purchase seat category name
purchaseTariffId¹	string Purchase tariff ID
purchaseTariffName	string Purchase tariff name
seatingSeated	boolean Indicates if this ticket has an assigned seat
seatingNumbered	boolean Indicates if the seat is numbered
seatingExternalEntrance¹	string External entrance information
seatingGate¹	string Gate information
seatingArea¹	string Area information
seatingLevel¹	string Level information
seatingBlock¹	string Block information
seatingRow¹	string Row information
seatingSeat¹	string Seat information
ticketMetadata¹	{ description: Extra metadata related to the ticket }
activationRuleId¹	string Activation rule ID
activationRuleName	string Activation rule name
usageRuleId¹	string Usage rule ID
usageRuleName	string Usage rule name
designRuleId¹	string Design rule ID
designRuleName	string Design rule name
dataCollectionRuleId¹	string Data collection rule ID
dataCollectionRuleName	string Data collection rule name
emailRuleId¹	string Email rule ID
emailRuleName	string Email rule name
devicesMap	{ description: Device information mapped to the ticket }
activationDetails¹	[ Ticket activation details {...}]
deletionDate	string($date-time) Date the ticket was marked as deleted
deletionReason	string Reason the ticket was deleted
transferForwardCount	integer Number of times the ticket was transferred forward
transferBackwardCount	integer Number of times the ticket was returned to a previous owner

¹ These fields are only returned when a detailed endpoint is used. In other words, they are excluded from the default light endpoint.