Timezone Handling
Overview
Our APIs use different date and time formats depending on the context. Understanding these distinctions is crucial for proper integration, or it may lead to incorrect timezone handling.
1. Catalog: UTC
Date-times from the catalog endpoints, both the read endpoints and the Setup APIs (/s360/v3/setup/**),
are returned in UTC, ISO 8601 with a Z offset. This covers event and performance start times,
match start times, timeslot windows, membership validity dates and sales-rule opening times.
YYYY-MM-DDTHH:mm:ssZ — for example 2022-03-10T11:15:50Z. Some values carry fractional seconds
(2026-10-14T22:00:00.666Z), so parse them with an ISO 8601 parser rather than a fixed pattern.
To show a time the way the event is advertised, convert it to the organization's time zone, given as
timeZone on each sales channel by GET /s360/v3/setup/saleschannels (for example Europe/Paris).
Date filters
The catalog search filters — performanceDateFrom / performanceDateTo on events,
matchDateFrom / matchDateTo on competitions, and modifiedAfter on seat queries — are compared as
absolute points in time, so the offset is required. A value without one (2026-01-01T00:00:00) is
rejected with 400. Any offset is accepted: 2026-01-01T00:00:00+01:00 and 2025-12-31T23:00:00Z
select the same performances.
2. Actions: UTC
All API actions and system events are timestamped in UTC, in ISO 8601 format with a Z offset:
YYYY-MM-DDTHH:mm:ssZ (millisecond precision is not guaranteed).
- File creation and last-modification times
- Payment date
- Shipment and collection dates
Examples
Catalog Object (UTC)
{
"performance": {
"id": "123",
"name": "Evening Show",
"startDateTime": "2022-03-10T11:15:50Z"
}
}
Action Object (UTC)
{
"file": {
"id": "file_789",
"creationDateTime": "2024-01-15T19:30:00Z",
"state": "CLOSED"
}
}