Documentation Index
Fetch the complete documentation index at: https://docs.gu1.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The transaction_time_zone enum is used as the optionaltimeZone field on Create Transaction and Create Batch. It indicates which IANA time zone applies when interpreting transaction-local timestamps (for example alongside transactedAt). If omitted, the column stays null (including all existing transactions). The field is optional so current integrations keep working unchanged.
This is separate from deviceDetails.timezone (device-reported zone) and from the organization default timezone in workspace settings.
Allowed values
| Value | Region (summary) |
|---|---|
UTC | Coordinated Universal Time |
America/Sao_Paulo | Brazil (SΓ£o Paulo) |
America/Argentina/Buenos_Aires | Argentina |
America/New_York | US Eastern |
America/Los_Angeles | US Pacific |
America/Mexico_City | Mexico |
America/Bogota | Colombia |
America/Lima | Peru |
Europe/London | United Kingdom |
Europe/Madrid | Spain |
Europe/Paris | France |
Europe/Berlin | Germany |
Europe/Rome | Italy |
Europe/Lisbon | Portugal |
Asia/Tokyo | Japan |
Asia/Shanghai | China |
Asia/Dubai | UAE |
Asia/Kolkata | India |
Australia/Sydney | Australia (Sydney) |
Africa/Johannesburg | South Africa |
Usage
- Create Transaction: Optional
timeZonein the JSON body. Omit fornull. - Create Batch: Each transaction object may include
timeZone; same validation as single create. - Get Transaction: Response includes
timeZone(string | null).