Skip to main content

​
Overview

The transaction_time_zone PostgreSQL enum is the allowlist for: If omitted on transactions, time_zone stays null. For entities, operational_hours stays null when the whole operationalHours object is omitted. This is separate from deviceDetails.timezone (device-reported zone) and from the organization default timezone in workspace settings.

​
Allowed values

ValueRegion (summary)
UTCCoordinated Universal Time
America/NoronhaBrazil (Fernando de Noronha)
America/Argentina/Buenos_AiresArgentina
America/MontevideoUruguay
America/Sao_PauloBrazil (São Paulo)
America/AsuncionParaguay
America/SantiagoChile
America/CaracasVenezuela
America/ManausBrazil (Amazonas)
America/CuiabaBrazil (Mato Grosso)
America/BogotaColombia
America/LimaPeru
America/Rio_BrancoBrazil (Acre)
America/New_YorkUS Eastern
America/ChicagoUS Central
America/Mexico_CityMexico
America/Los_AngelesUS Pacific
Europe/LondonUnited Kingdom
Europe/LisbonPortugal
Europe/MadridSpain
Europe/ParisFrance
Europe/BerlinGermany
Europe/RomeItaly
Asia/DubaiUAE
Asia/KolkataIndia
Asia/ShanghaiChina
Asia/TokyoJapan
Australia/SydneyAustralia (Sydney)
Africa/JohannesburgSouth Africa
Send the string value exactly as shown (case-sensitive). Do not send TypeScript enum key names.

​
Usage

  • Transactions: Optional timeZone (metadata; omit = null). Not required for create when transactedAt uses Z. When both a local datetime and timeZone are provided, the API can store the equivalent UTC instant. Independent of entity operationalHours for operational-hours rules.
  • Entities (person or company): Optional root operationalHours with required timezone when the object is sent. See Create entity.
  • Get Transaction / Get entity: Response includes timeZone or operationalHours respectively (string | null / object | null).

​
See Also