Date Formats

Dates in the Oracle Hospitality APIs are expressed in the RFC3339 “full-date” format (that is, date-fullyear "-" date-month "-" date-mday. "T" time-hour ":" time-minute ":" time-second "Z" / ("+" / "-") time-hour ":" time-minute). The following are examples of this format:

• 2023-06-05 for 5th of June 2023

• 2023-06-05T08:43Z or 2023-06-05T09:43+01:00 for 5th of June 2023 at 8:43 AM in the UTC time zone or 9:43 in the local time zone

Most times are expressed in local time zones, not in Coordinated Universal Time (UTC).

Asynchronous APIs return times in Coordinated Universal Time (UTC).

For Profiles APIs, the time depends on where the profile was created. For example:

• If the profile was created at the hub level, then Profiles APIs return times in the hub time zone if the time zone is set. If no hub time zone is set, then for a profile created at the hub level, Profiles APIs return in Coordinated Universal Time (UTC).

• If the profile was created at the property level, then Profiles APIs return times in the property time zone if the time zone is set. If no property time zone is set, then for a profile created at the property level, Profiles APIs return in Coordinated Universal Time (UTC).

Table 8-5 Asynchronous API Times Zones

API	Where was the Profile Created?	Is the Time Zone Set?	Time Zone Returned
Asynchronous APIs	n/a	n/a	Coordinated Universal Time (UTC)
Profiles APIs	Hub	No	Coordinated Universal Time (UTC)
Profiles APIs	Hub	Yes	Hub timezone
Profiles APIs	Property	No	Coordinated Universal Time (UTC)
Profiles APIs	Property	Yes	Property timezone
All other property APIs	n/a	n/a	Property timezone