Skip to main content
Changes to the API will be documented below in reverse chronological order. Refer to the official release notes for the wider system updates (and API changes pre-2022).
​
27th January 2026
  • GET /resale-listings and GET /resale-listing:
    • Added new filtering options: eventId, customerId, createdAfter, createdBefore, status, and withTrashed.
    • Added new attributes to resale listing responses: eventId, orderId, createdAt, closedAt, onSaleFrom, and onSaleUntil.
    • Added new attributes to resale contract responses: currencyId, price, totalPrice, displayTotal, and soldAt.
    • Added ability to include events, orders, resaleContracts.replacingOrderItem, and resaleContracts.payoutTransaction.
  • GET /resale-listings and GET /resale-listing: Added ability to include resaleContracts.payoutWalletTransaction to retrieve wallet transaction details for sold resale contracts.
  • Added bundledItems (id + quantity) to GET /sale-items and GET /sale-item when bundle data is present.
​
20th January 2026
  • Added support for all item types in the GET /order-items type filter parameter. Previously only ticket, product, and guestList were accepted. Now accepts all 14 item types including season_ticket, fee, bundle, gift_voucher, and more. Refer to the endpoint documentation for the full list.
​
6th January 2026
  • Breaking: GET /wallets and GET /wallet endpoints now return customerId instead of userId in the response attributes. This is consistent with all other API endpoints that provide customerIds instead of userIds.
​
22nd December 2025
  • Updated DELETE /resale-listings to properly cancel resale listings with validation. Response now includes contractsCancelled, contractsSold, and contractsFrozen counts. Sold and frozen contracts are preserved; only unsold, unfrozen contracts are cancelled.
​
19th December 2025
  • Added eventId as a filter to the GET /orders endpoint to retrieve only orders that contain items from the given event ID.
  • Added a new orderItemId filter to GET /v1/wallets/transactions endpoint.
  • Added a new source attribute to the WalletTransactions entity from GET /v1/wallets/transactions to detail the source of the wallet transaction.
​
17th December 2025
  • Added new GET /wallets and GET /wallet endpoints to retrieve wallets registered within a company (NB: wallets power our account balance functionality).
  • Added a new GET /v1/wallets/transactions endpoint to list all recent transactions across wallets (or for a specific wallet)
  • Added POST /v1/wallets/transactions/confirm to allow confirmation of pending transactions. Pending transactions are typically used for resale, order modifications, and other internal processes that deposit money into wallets.
  • Added POST /v1/wallets/payouts/initiate to allow initiation of an external payout from a wallet. Unlike cashouts, payouts are not capped at the mount of topups purchased. This endpoint allows for a full payout of the account balance, regardless of source of funds.
  • Added POST /v1/wallets/payouts/confirm to confirm when an initiated payout has been completed. This is an important step where external parties need to also verify that the payout was handled correctly.
  • Removed deprecated endpoints POST /v1/wallets/nfc-download and POST /v1/wallets/nfc-download/confirm as these are no longer in use or supported.
  • Add GET /v1/resale/listings index endpoint to return all available resale listings
  • Payload updats to POST /v1/resale/listings to support creation of multiple item listings
  • Added a new authenticationProviders relationship that can be included on both GET /customers and GET /customer to determine the related customer SSO IDs.
​
3rd December 2025
  • Added a new orderColumn attribute to GET /sale-items endpoint, which reflects the sort order defined in admin, and used in the ticket shop.
​
20th November 2025
  • Added a new DELETE /customers endpoint to support customer data deletion requests & accommodate data retention policies.
​
11th November 2025
  • On GET /events and GET /event we now return the isCancelled attribute to indicate that an event has been marked as cancelled.
​
4th November 2025
  • Added a new DELETE /customers endpoint to support customer data deletion requests & accommodate data retention policies.
  • We now return all fees, resale fees, fulfilment fees, and protection fees via the GET /v1/order-items endpoint
  • When returning fees via the GET /v1/order-items endpoint we also provide access to the producingOrderItemId field which allows consumers to reference the order item that generated that specific fee. Where this is null the fee applies to the whole basket.
  • Added the ability to retrieve orders from the GET /v1/order endpoint using the reference, rather than the ID.
​
16th October 2025
  • Introduced access control scanning / pairing restrictions to items that belong to an order which is currently being modified, or resold.
  • GET /v1/entry/tickets receives a new status (variable.status) option locked, which indicates that the order is currently being modified. Items with this status should be considered temporarily invalid for scanning. The status of these items could return to sold or refunded in the future.
  • Added POST /v1/resale-contracts to create a resale contract, which allows an order item to be resold
  • Added GET /v1/resale-contract to get a resale contract for an order item or by ID
  • Added POST /v1/resale-contracts/delete to delete a resale contract for an order item or a resale contract ID
  • Added replacedOrderItem to GET v1/order-items, GET v1/order-item and GET v1/order to return the original order item for resold and modified order items.
​
2nd October 2025
  • Added a new cancelExistingBasket parameter to POST /v1/basket-items which allows expiring a basket and adding items to a new basket in a single request.
  • Added a new endpoint DELETE /v1/baskets for expiring baskets.
  • Added parentSaleItemId to GET /v1/sale-items for identifying add-ons.
  • Added a new unformatted property to the GET /v1/event-statistics endpoint to prevent humanizing/formatting numerical statistics.
​
12th September 2025
​
14th August 2025
  • POST /v1/basket-items now accepts order item ID as well as sale item ID to add a resale item to basket. The resaleFeeSellerContribution has also been added and can be pasesed in pointOfSaleData
​
21st July 2025
  • Updated POST /tickets/pair to accept an event-id property in order to scope the possible list of matching order items. This is particularly useful for any users that re-use barcodes across events or schedules.
​
30th June 2025
​
5th June 2025
  • Update POST /basket-items to return a startBasketUrl link to enter checkout for the basket, if generateBasketUrl is set to true on the request
​
2nd June 2025
​
19th May 2025
​
14th April 2025
  • Updated POST /zones/check and POST /zones/scan to return a statusDetail field to embelish a denied response. Currently this only returns historicBarcode in the event a barcode has been scanned that has since been superceded by a new barcode following a transfer.
  • Updated GET /entry/tickets to return a historicBarcodes list within the variable portion of a ticket, which lists all previous barcodes of the ticket, in order to determine whether the customer is attempting to scan an old (possibly resold) ticket.
​
31st January 2025
​
6th January 2025
​
18th December 2024
  • GET /order-items now correctly returns items from fully cancelled/refunded orders. Previously it would include refunded items if the order was only partially refunded.
​
13th December 2024
  • The customer update endpoint will now preserve existing customer address fields as long as no new address data is provided. Prior to this change, customer address fields would be cleared if no address data was provided within the payload.
​
3rd October 2024
  • Added minPrice and maxPrice to GET /events and GET /event as additional opt-in attributes
  • Updated the lastUpdated filter on GET /events so that it now considers pricing, venue & item updates.
​
5th September 2024
​
29th August 2024
​
24th July 2024
  • Added the scheduleId to the returned fields on GET /events and GET /event endpoints
  • Added eventSchedules as a possible include on GET /events and GET /event endpoints
  • Added a new filter to GET /events to allow filtering by scheduleId. Providing a null, zero, or empty value will return events that are outside of a schedule.
  • Added a new filter to GET /events to allow grouping of events by their respective schedule (groupScheduledEvents). Events without a schedule continue to be returned individually.
​
19th June 2024
  • Added historicalBarcodes to the include parameter for the below endpoints. New barcodes are generated when an order item is transfered or a barcode change is manually performed. This will return all historical barcodes associated with the order item.
  • Added variablePriceEnabled, variablePriceMin, and variablePriceMax to GET /sale-item and GET /sale-items endpoints to indicate whether pricing is a customer selection.
  • Added customPriceEnabled and customPriceRequired to the documentation for GET /sale-item and GET /sale-items to indicate whether prices can be defined by staff users in mobile applications.
  • Marked the GET /entry-tickets, POST /orders/upload, POST /wallets/nfc-download, and POST /wallets/nfc-download/confirm endpoints as deprecated and likely to be removed in a future version of the API. Anyone using these endpoints should review the documentation to understand alternative provisions for the functionality being removed.
  • A display issue with the related space data for order items has been updated to return the seat/space name correctly, rather than the fully formatted string. This is a breaking change for anyone relying on the broken data previously being returned.
  • Resolved an issue with access to tickets that were sold by a parent company for a child company event on GET /zones/items, GET /order-item and GET /order-items.
​
20th May 2024
  • Ignore empty data capture responses on the v1/data-capture-responses endpoint
​
15th May 2024
​
5th April 2024
The following endpoints now accept a decimal percentage for the discount amount value.
​
6th March 2024
​
12th February 2024
  • The GET /orders endpoint now allows for the retrieval of orders in failed reservation states (cancelled, expired, failed, and rejected), through the use of the withReservations query parameter.
  • The GET /order endpoint now allows for the retrieval of orders in failed reservation reservation states as above.
​
1st February 2024
  • The GET /order endpoint now allows for the retrieval of orders in reservation state.
  • The GET /orders endpoint now allows for the retrieval of orders in reservation state, through the use of the withReservations query parameter.
​
23rd January 2024
  • The GET /sale-items and GET /event-tickets endpoints now include the following attributes for timeslots:
    • hasUnlimitedStock
    • totalStock
    • currentStock
    • hideWhenOffSale
    • hideWhenOutOfStock
    • onSaleFrom
    • onSaleUntil
  • The Order Item (GET /v1/order-item) and Order Items (GET /v1/order-items) endpoints now allow for retrieving order items using a specific order ID
  • The Sale Items (GET /v1/sale-items) endpoint now allows for retrieving sale items using a specific inventory item ID
  • The Order Item (GET /v1/order-item) and Order Items (GET /v1/order-items) endpoints now allow for dataCaptureFields to be included alonside dataCaptureResponses
​
22nd January 2024
  • The add to basket (POST v1/basket-items) endpoint now accepts the spaceId to which a sale item should be associated on a seated event.
  • The add to basket (POST v1/basket-items) endpoint now permits you to provide the same sale item ID in multiple basket items, allowing each to utilise different item settings.
​
21st January 2024
  • The v1/zones/scan and v1/zones/check endpoints now return the order reference in the responseg
  • Prices are now returned in all available currencies on the get event tickets (GET v1/event-tickets) endpoint
  • The default event currency is now returned on the get events (v1/events) endpoint
​
8th January 2024
  • The Add to basket endpoint (POST /v1/basket-items) received an update in error response status code from 403 to 422 when attempting to add a child company sale item to a parent company basket without global transactions enabled.
​
3rd January 2024
​
21st November 2023
  • The POST /v1/guestdata endpoint now contains the email and order reference for each entry in content.guests
  • The GET /v1/entry/tickets now has the email in each stable object
  • The GET /v1/zones/items now returns the order reference in each element, and the query now searches the barcode and order reference, as well as customer name and email
​
3rd November 2023
​
30th October 2023
  • Added new seatingPlan property to the Retrieve Events and Retrieve Event endpoints. This currently includes a single bestAvailableSeatsEnabled option.
​
10th October 2023
  • The GET /v1/events endpoint now surfaces the owning company’s live_mode in relationship data.
  • A new filter (hideDemoMode) has been added to GET /v1/events which allows consumers to exclude any events belonging to demo companies from the response.
  • A new filter (hideChildEvents) has been added to GET /v1/events which allows consumer to exclude child company events from the response.
​
9th October 2023
  • The GET /v1/orders and GET /v1/order endpoint can now return a full customer object. This value will be included in the response when customers is given as an include parameter.
​
6th October 2023
  • The GET /v1/events endpoint now surfaces the organiserName, organiserEmail and organiserPhone attributes.
​
4th October 2023
  • The GET /v1/event-tickets endpoint added a new tickets.*.seatingPlanAreas array, which includes seating plan area ID’s for which that sale item can be bought. This new property was added to facilitate the ability to book best available seats for specific areas via the API.
  • Additionally, the tickets.*.seatingPlanAreas property can be filtered to only include areas with availability by passing an additional query param checkAreaAvailability=true.
​
26th September 2023
  • Breaking Removed the token param from GET /customer as we’ve since replaced the SESScustomertoken cookie with a customer_id cookie.
​
14th September 2023
  • Added new GET /venues endpoint to retrieve a list of venues.
  • Added a new POST /venues endpoint to allow venues to be created.
  • Added a new venue parameter to the event create/update payloads, allowing event venues to be created on the fly at the point of event creation/update.
​
12th September 2023
  • Added multi language support. Clients can now optionally specify a preferred language for the request using the Accept-Language header.
    • If the given language is enabled against the company, the request payload and respective response data will be treated as local to the specified language.
    • If the given language is not enabled against the company, or is otherwise invalid, the companies fallback language will be used.
    • Responses will also now include the Content-Language header, which indicates the language of the response.
​
4th September 2023
  • Added a new /event-statistics endpoint for retrieving real-time event sales data for a single event.
​
1st September 2023
  • Added a new offline parameter to POST /orders/complete endpoint to facilitate offline e-wallet top-ups.
​
7th August 2023
  • Added a new GET /companies endpoint to retrieve companies the authenticated user is associated to.
​
11th July 2023
​
6th July 2023
  • Added only_on_sale flag to the events endpoint to return only events that can be sold via the current sales channel (box office, or kiosk).
​
18th May 2023
​
10th May 2023
  • Updated GET /entry-tickets to also return season tickets for the given event.
​
9th March 2023
​
1st February 2023
​
12th December 2022
  • Following the introduction of tax breakdowns in shop orders, the tax breakdown details are now provided via GET /order-items and GET /orders.
  • The currency ID of any collected fees is now included in GET /order-items for use when any transactions take place in custom currencies.
  • It is now possible to retrieve topup and cashless product purchases via GET /order-items.
  • When retrieving cashless product purchases via GET /order-items it’s possible to specify that the shop should be included in the response.
​
6th December 2022
  • Removed the sku parameter from the POST /basket-items endpoint, in favour of using topup IDs directly (as returned by GET /sale-items)
  • Added a currencyId parameter to the POST /basket-items endpoint to specify the basket currency, rather than relying on the customer’s previously selected currency or the company default.
  • Added a global X-NU-CURRENCY-ID header that will change the selected currency for that request only. This is useful for retrieving sale items with the correct pricing.
  • Added a new feeCurrencyId value to any order responses via GET /orders, which represents the currency any fees should be displayed in. This is significant with cashless products as the fees will be in a companies default currency when cashless is setup to use a token currency.
​
5th December 2022
  • Added the bundledWith array on GET /sale-items to return the list of sale item IDs that come bundled with an item.
  • Added the bundleLeadOrderItemId to the GET /orders and GET /orders/:id endpoints, to highlight where an order item is being purchased as part of a bundle.
​
28th November 2022
  • Added isCustom to the currencies returned from GET /currencies, to identify which currencies are custom token currencies.
  • Added topupTokenAmount to the sale item details returned from GET /sale-items, and GET /items to detail how many tokens a topup will add to a users basket. This value will be null if cashless settings do not use a custom token currenciy.
​
4th November 2022
  • Added subunit to GET /currencies to complement our new support for non-2DP currencies.
​
28th October 2022
  • Added UUID to the initiate wallet download endpoint to ensure idempotency between requests.
​
19th October 2022
  • Allowed the transaction source to be recorded for cashouts via the POST /wallets/cashouts endpoint.
  • Allowed the transaction source to be recorded for topups and cashouts via the POST /orders/upload endpoint.
​
22nd September 2022
​
19th September 2022
  • Added a global response header to all requests: X-Runtime which returns the total execution time, in seconds, for any given API in call. This value can be observed to adjust the rate of API calls according to performance degradation over a period of time.
​
7th September 2022
​
11th August 2022
  • Added thumbnailImage, pageHeaderImage, and metaImage Media Resources to the following endpoints in our Events API:
    • GET /activated-events - This endpoint does currently have media.header-image, media.list-thumbnail, and media.meta-image attributes, but these are now considered deprecated. For backwards compatibility these attributes will remain in the response.
    • GET /events
    • GET /future-events - This endpoint does currently have media.header-image, media.list-thumbnail, and media.meta-image attributes, but these are now considered deprecated. For backwards compatibility these attributes will remain in the response.
  • Added the ability to include event media by passing images in the include parameter of the GET /event endpoint.
  • Added include to the /basket-items endpoint to allow the inclusion of a user’s wallet info, after a cashless transaction has completed automatically.
  • Added GET /countries for retrieving country IDs and metadata.
​
21st July 2022
  • Fixed an issue where events could be created without a timezone. If no timezone is specified, it now falls back to the timezone stored against the current company.
  • Added itemName and itemId to the /order endpoint’s order item response data.
  • Added refundedAmount, isValid, requiresApproval, approvedAt, rejectedAt, and cancelledAt to any order item response data inside orders.
  • Added cursor pagination to the /orders endpoint, allowing for a streamed pagination approach, based on the lastUpdated timestamp provided.
  • Added a contains parameter to the /orders endpoint, allowing you to filter orders that contain only the specified item types.
  • Added customerSsoId parameter to POST /basket-items and POST /orders/complete
  • Improved feedback & error handling on POST /order-item/approve
  • Allow disabling both the order confirmation AND the guest list approved confirmation in POST /basket-items
​
30th June 2022
  • Added uuid parameter to the POST /basket-items endpoint to provide idempotency functionality when auto completing orders.
  • Added the image property to all sale items returned via the /sale-items endpoint.
  • Added itemNotes and orderNotes to the GET /entry/tickets endpoint.
  • Added orderNotes to the POST /guestdata response.
  • Added the ability to include order item notes in the GET /order-items and GET /order-item endpoints
  • Added orders.*.notes and orders.*.items.*.notes to the GET /orders endpoint.
  • Added notes and items.*.notes to the GET /order endpoint.
  • The Events API now respects the Visibility Groups & Permissions of the API user & applies the correct filtering.
  • Changed content.const.type in GET /entry/tickets to be the current item name and added content.const.typeDuringSale which contains the item name at point-of-sale.
  • Updated the /customers/get endpoint to return the refundable_balance_online and refundable_balance_offline in any included wallets.
​
27th May 2022
  • Added GET /currencies to retrieve all company currencies.
  • Added GET /shops to retrieve all cashless shops for a company, that this user has access to.
  • Added GET /shop to retrieve a single cashless shop, if the user has access to it.
  • Added cashless_product as a permitted type for GET /sale-items.
  • Added shopId parameter to the GET /sale-items endpoint, allowing for the items relating to a specific shop to be retrieved.
  • Updated GET /sale-items to return all inventory sale items across events and shops, when no types are explicitly provided.
  • Added categories as a new relationship for responses via GET /sale-items.
  • Added the following new fields to the GET /sale-items response:
  • shopId
  • categories
  • customPriceEnabled
  • customPriceRequired
  • Added support for retrieving customers using an nfcId via GET /customers.
  • Added support for retrieving order items using an nfcId via GET /order-items.
  • As a side effect, the nfcId is now surfaced in the order item response.
  • Added ewallet-online as a permitted payment method when auto completing a basket via POST /basket-items.
  • Added nfcId as a permitted parameter when completing a basket via POST /basket-items allowing the order to be linked to an NFC tag.
  • Added POST /wallets/cashout to create a cash-out from a cashless wallet, for a user.
  • Added POST /wallets/nfc-download and POST /wallets/nfc-download/confirm endpoints to handle the 2-step process of downloading wallet balances to an NFC media item.
  • Added POST /orders/upload endpoint to allow for bulk uploading offline orders for reconciliation.
  • Added support for offline zone entry controls with the following new additions to the API:
    • Added includeZones flag to the GET /entry/tickets endpoint, which returns a new zoneData key including zone IDs each item is eligible for entry, as well as any previous scans associated with the order item.
    • Updated POST /entry/tickets endpoint to accept uuid, zoneId, latitude, longitude, scan as optional extra keys per item
  • Added companies to GET /event and GET /events as an optional relationship include.
  • Added latitude and longitude to GET /event and GET /events when including the venues relationship.
  • Added GET /basket/data-capture endpoint for retrieving data capture questions for a given basket.
  • Added the following attributes to DataCaptureField JSON:API Resource:
    • assignedToEntity
    • assignedToId
    • questionId
    • sourceEntityType
    • sourceEntityId
    • orderColumn
    • createdAt
    • updatedAt
    • deletedAt These attributes will appear on GET /event and GET/basket/data-capture
  • Added customerId, customerName and customerEmail to GET /basket-items as an optional alternative to basketId
  • New endpoint POST /order-item/approve will allow you to approve or reject existing order items
​
28th February 2022
  • Added includeProducts as an option to GET /entry/tickets to include product barcodes in the valid tickets list.
  • Automatically include valid addon tickets in GET /entry/tickets.
  • Accept product/addon product/addon ticket barcodes in POST /entry/tickets.
  • Added the interacPresent option to POST /checkout/create-payment-intent to support Interac payments in Canada.
  • Added a dataLastSynchronised attribute to GET /report to signify when the report data was generated.
  • Added a refresh query parameter to GET /report to clear any cached report data and regenerate the report.
  • Added a headers attribute to GET /report
  • Added tags and tagCategories to GET /event as data that can be included
  • Added tagCategories to GET /events as data that can be included
​
24th January 2022
  • Added country, city, and region to our Customer Resource, meaning this information is available directly via the GET /customers and GET /customer, and any other endpoint in which customers can be include via a resource relationship.
  • Standardised date formats across the entire API. The following dates have been changed:
    • GET /activated-events
      • *.start from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.end from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /discount-codes/buy-x-get-y
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /discount-codes/buy-x-get-y/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /company/users
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.acceptedTermsAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedPrivacyAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedEmailOptInAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
    • POST /company/users/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.acceptedTermsAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedPrivacyAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedEmailOptInAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
    • GET /company/users
      • data.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.acceptedTermsAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedPrivacyAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedEmailOptInAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
    • GET /company/user
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers, visibilityGroups and roles)
      • included.*.attributes.acceptedTermsAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedPrivacyAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
      • included.*.attributes.acceptedEmailOptInAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companyUsers)
    • POST /orders/complete
      • date from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • items.*.eventStartDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • items.*.eventEndDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /customers
      • data.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.meta.lastUpdated from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companies and dataCaptureResponses)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companies and dataCaptureResponses)
    • POST /customers/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /customers
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /customer
      • data.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.meta.lastUpdated from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companies and dataCaptureResponses)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (companies and dataCaptureResponses)
    • POST /data-capture-responses
      • data.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /discount-codes
      • data.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /discount-code
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /entry/tickets
      • content.*.stable.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • content.*.stable.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • content.*.variable.scannedOn from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • content.*.variable.scannedOn from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • listEndTime from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /event-tickets
      • tickets.*.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • tickets.*.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • tickets.*.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • tickets.*.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /events
      • events.*.end from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • events.*.start from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • events.*.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • events.*.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • events.*.meta.lastUpdated from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • events.*.tags.*.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • events.*.tags.*.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /event
      • data.attributes.startDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.endDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events
      • data.attributes.startDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.endDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (eventSettings, eventStreams, tags, venues)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (eventSettings, eventStreams, tags, venues)
    • POST /events/update
      • data.attributes.startDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.endDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (eventSettings, eventStreams, tags, venues)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (eventSettings, eventStreams, tags, venues)
    • POST /discount-codes/fixed
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /discount-codes/fixed/update
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /inventory-items
      • data.*.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /order-items
      • data.*.attributes.approvedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.rejectedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.cancelledAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.meta.lastUpdated from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (customers, items, saleItems)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (customers, items, saleItems)
      • included.*.attributes.startDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (events)
      • included.*.attributes.endDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (events)
      • included.*.attributes.expiresAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (orders)
      • included.*.attributes.completedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (orders)
    • GET /order-item
      • data.attributes.approvedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.rejectedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.cancelledAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.meta.lastUpdated from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (customers, items, saleItems)
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (customers, items, saleItems)
      • included.*.attributes.startDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (events)
      • included.*.attributes.endDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (events)
      • included.*.attributes.expiresAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (orders)
      • included.*.attributes.completedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ (orders)
    • GET /orders
      • orders.*.date from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • orders.*.items.*.eventStartDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • orders.*.items.*.eventEndDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /order
      • date from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • items.*.eventStartDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • items.*.eventEndDate from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /discount-codes/percentage
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /discount-codes/percentage/update
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/charities
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/charities/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validUntil from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/guest-lists
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/guest-lists/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validUntil from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/products
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/products/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validUntil from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/tickets
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /events/tickets/update
      • data.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.onSaleTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.attributes.validUntil from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • included.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /sale-items
      • saleItems.*.validFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • saleItems.*.validUntil from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • saleItems.*.onSaleFrom from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • saleItems.*.onSaleTo from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • saleItems.*.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • saleItems.*.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • timeslots.*.startAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • timeslots.*.endAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /transactions
      • data.*.attributes.createdAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • data.*.attributes.updatedAt from YYYY-MM-DD HH:MM:SS to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /zones/all
      • *.openingDate from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.closingDate from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.createdAt from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.updatedAt from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.deletedAt from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /zones/scan
      • lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • lastScannedOut from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /zones/check
      • lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • lastScannedOut from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • POST /tickets/pair
      • lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • lastScannedOut from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
    • GET /zones/items
      • *.lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
      • *.lastScannedIn from YYYY-MM-DDTHH:mm:ss+HH:mm to YYYY-MM-DDTHH:mm:ss.SSSSSSZ
  • Added a withTrashed request parameter along with a deletedAt attribute in the body of responses allowing you to retrieve deleted records from the following endpoints:
  • This withTrashed parameter acts as a global setting, meaning that all deleted resources will be returned, including any related resources appearing in the included attribute in the response.
​
18th November 2021
  • Added an array of Timeslot data to the GET /activated-events endpoint
  • Improved order search by adding a query parameter to the [GET /orders](/api-reference/orders/retrieve-orders) endpoint, meaning you can now search orders by customer email, customer full name, order reference or event name.
  • New endpoint POST /guestdata added, which allows you to synchronise all guest list data to your access control device
  • New endpoint PUT /guestdata created, which allows you to update the current number of guests that have attended (for a particular guest list order item).
  • Added new permissions attribute to the GET /activated-events endpoint, containing information on whether the authenticated user can or cannot edit the event.
  • Added a new hideAttendees attribute to the GET /zones/all endpoint, allowing for us to control if the attendees tab in the access control app is or is not visible.