List items for a particular or all events, showing the timeslots available for each item.
The 'Bearer' token can be obtained from the token management interface or via the login endpoint using your admin user credentials.
The inventory item ID you wish to retrieve sale items for.
The event ID you wish to retrieve tickets for. If both eventID and shopID are omitted, all sale items will be returned based on whether the user can view events and/or shops. Where event related sale items are returned, timeslots will be filtered to those associated with the tickets returned on the current page.
The shop ID you wish to retrieve products for. If both eventID and shopID are omitted, all sale items will be returned based on whether the user can view events and/or shops. Where event related sale items are returned, timeslots will be filtered to those associated with the tickets returned on the current page.
The types of sale item to return.
ticket, product, guest_list, charity, season_ticket, cashless_product, cashless_topup The page you wish to retrieve sale items items. If not specified, by default pagination is handled by offset.
The offset - e.g 2 for listing sale items starting with the 2nd sale item. Offset will always take precedence over page.
The number of sale items to retrieve per page. The maximum (and default) is 25 per page.
Date/Time for retrieving sale items who's associated database records (sale items, inventory item and pricing) have been updated after the given lastUpdated time. Accepted formats:
Controls records returned depending on their deletedAt status. This is a global flag, so will apply to all resources, including relationships such as resources returned under the included attribute.
true to include deleted recordsfalse to exclude deleted records (or leave blank)true, false A list of attributes that you wish to be returned in the payload. When empty or omitted, all fields will be included by default. Use dot-notation for both top-level resources and child resources, i.e. saleItems.type,eventTimeslots.name. Can be used in conjunction with except providing both parameters don't reference the same resource.
A list of attributes that you wish to exclude from the payload. When empty or omitted, all fields will be included by default. Use dot-notation for both top-level resources and child resources, i.e. saleItems.type,eventTimeslots.name. Can be used in conjunction with only providing both parameters don't reference the same resource.