# Retrieve valid event tickets Retrieve a detailed list of valid event tickets issued for sections that the authenticated redeemer is authorised to admit patrons to. Endpoint: GET /events/{event}/tickets Version: 3.0.0 Security: SessionKey ## Path parameters: - `event` (integer, required) Unique identifier of the requested event ## Query parameters: - `records` (integer) The number of records per page that should be returned - `page` (integer) The number of the results page to return - `modified_since` (string) Only return tickets that have had a status change after the provided date ## Response 200 fields (application/json): - `total` (integer) The total number of results available - `page` (integer) The number of the results page returned - `records` (integer) The maximum number of results returned per page - `entries` (array) List of tickets matching the given criteria - `entries.serial` (string) Serial number that uniquely identifies the ticket - `entries.status` (string) The ticket's current status - `entries.section` (object) The event section to which this ticket grants access - `entries.section.self` (string) URI of the event section resource - `entries.section.name` (string) Name of the event section - `entries.section.description` (string) Details of the experience customers can expect when purchasing tickets to this event section - `entries.owner` (object) Details of the user account that holds the ticket - `entries.owner.self` (string) URI of the account resource - `entries.owner.number` (string) Immutable identifier attached to the account - `entries.owner.username` (string) Unique username attached to the account - `entries.owner.email` (string) Unique email address attached to the account - `entries.owner.firstName` (string) The account holder's forename - `entries.owner.lastName` (string) The account holder's surname - `entries.issued` (string) The date and time at which the ticket was issued - `entries.redeemed` (string) The date and time at which the ticket was redeemed (or N/A if it has not been) ## Response 403 fields (application/json): - `message` (string) Reason for the given response. ## Response 404 fields (application/json): - `message` (string) Reason for the given response.