Timezones
How the API handles dates and timezones.
Dates in local timezone
All dates returned by the API (order_date, created_at) are in the merchant's local timezone, based on their country of registration.
For example, an order created at 15:07 UTC for a merchant in Peru is returned as:
{
"order_date": "2026-02-24T10:07:31.365068-05:00"
}The -05:00 offset indicates Lima timezone (UTC-5).
X-Timezone header
Every orders and products response includes the X-Timezone header with the IANA timezone applied:
X-Timezone: America/LimaTimezones by country
| Country | Timezone |
|---|---|
| Peru | America/Lima |
| Mexico | America/Mexico_City |
| Colombia | America/Bogota |
| Chile | America/Santiago |
| Argentina | America/Argentina/Buenos_Aires |
| Brazil | America/Sao_Paulo |
| Venezuela | America/Caracas |
| Bolivia | America/La_Paz |
| Ecuador | America/Guayaquil |
| Paraguay | America/Asuncion |
| Uruguay | America/Montevideo |
| Panama | America/Panama |
| Costa Rica | America/Costa_Rica |
Format
Dates follow ISO 8601 format with timezone offset:
YYYY-MM-DDThh:mm:ss.ssssss±hh:mmIf the merchant's timezone cannot be determined, dates are returned in UTC (+00:00).
New fields in order items
Order items now include two additional fields:
| Field | Type | Description |
|---|---|---|
variant_id |
integer | null |
Internal variant identifier (null for historical orders) |
sku |
string | null |
Product SKU code (null if not configured) |
Example:
{
"items": [
{
"variant_id": 6110,
"sku": "CAM-AZU-S-001",
"name": "AZUL - S",
"quantity": 1,
"base_price": "205.00"
}
]
}