Formats

Keep it consistent

General Data Guidelines

• Character Set: All data should be in the UTF-8 character set to ensure consistency and compatibility.

• Currency Codes: Currency codes must be in the ISO-4217 format.

• Language: Language must be specified using the ISO-639-1 format.

• Amounts and Values: Follow international standards for amounts and values. Rounding may be required to adhere to these standards.

• Case Sensitivity: All data fields are case-sensitive, meaning that capitalization matters.

• Optional Parameters: If optional parameters are not set or are left empty, they will not be included in the response. These parameters are nullable to support serialization.

---

Date / Time Guidelines

Points in time are expressed as strings using the RFC 3339 datetime format. We always expect the local time with its UTC offset.

Example:

Burj Khalifa entrance Ticket in Dubai for 12th of May 2016 at 14:00 (local time).

👍 Expected	👎 Not expected
2020-05-12T14:00:00+04:00	2020-05-12T10:00:00+08:00
	2020-05-12T18:00:00+00:00

Notes

Note 1: Although the above examples express the same point in time, we consider only the first one as valid because we always require the date and time in reference to the location of the activity. Note 2: Although mentioned in RFC 3339, due to technical restrictions we do not support the Z suffix. Please send +00:00 to denote a zero UTC offset instead. Note 3: All offsets are automatically adjusted based on daylight saving time (DST).