Conventions and Standards
Documents the data formats and conventions used throughout the Tiqets Distributor API
All API responses are returned in JSON format.
Some text fields may include basic HTML markup, such as the following tags: <br>, <p>, <b>, <strong>, <em>, <i>, <ul>, and <li>.
🗓️ Dates and times
Generally speaking, date and time are returned in this format:
datefields follow the ISO 8601 format:YYYY-MM-DD(e.g.,2025-04-25).timefields follow the ISO 8601 as 24-hour clock:HH:MM(e.g.,17:30).
All date and time fields related to availability or visit times are provided in the local time zone of the experience. The time zone is returned in the tz format, e.g.:
"timezone": "Europe/Paris"Please be aware that products in time zones behind your local time zone can be available and accept orders for 'yesterday' according to your own time zone.
In some cases, such as for the order creation timestamp, a full ISO 8601 timestamp is used. This includes seconds, microseconds, and a time zone offset.
"2025-04-14T11:37:50.194835+00:00"This format represents a precise point in time, including:
Tseparator between date and timemicroseconds:
.194835timezone offset:
+00:00(UTC)
💶 Currency and amount format
Currency amounts are represented as decimal numbers using a dot (
.) as the decimal separator (e.g.,22.00).In some cases, amounts are nested inside an object with a currency code:
This structure is used for values such as prices, commissions, fees, and totals.
The currency is typically consistent across all products in a single API request, but it is good practice always to read it from the response.
Languages
Many endpoints accept a language parameter as input or include a language in the output. These are the languages currently supported by Tiqets. If omitted, the default language is always English.
ca
Catalan
cs
Czech
da
Danish
de
German
el
Greek
en
English (Default)
es
Spanish
fr
French
it
Italian
ja
Japanese
ko
Korean
nl
Dutch
pl
Polish
pt
Portuguese
ru
Russian
sv
Swedish
zh
Chinese
Last updated
Was this helpful?

