Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.everflow.io/llms.txt

Use this file to discover all available pages before exploring further.

Three rules cover most timezone questions:
  • *_unix_timestamp fields are always UTC seconds. Never shifted by request parameters or network configuration.
  • Date-string fields and date bucketing use the timezone_id on the request (or the network default if omitted).
  • timezone_id shifts where date buckets begin and end. It does not transform individual event timestamps.

​
timezone_id in reporting requests

Reporting endpoints accept timezone_id in the request body to bucket events into days, hours, months, etc. 
{
  "from": "2026-04-01",
  "to": "2026-04-30",
  "timezone_id": 67,
  "columns": [{ "column": "date" }]
}

timezone_id: 67 (UTC)

Event at 2026-04-01 23:30 UTC → April 1 bucket.

timezone_id: 80 (America/New_York)

Same UTC timestamp (19:30 EST) → April 1.Event at 2026-04-02 03:30 UTC (23:30 EST) → April 1 under EST, April 2 under UTC.
from and to values are interpreted as 00:00:00 in the requested timezone_id — not midnight UTC. The same date-range string returns different totals depending on which timezone_id you pass.
No timezone_id? Reports fall back to the network default (reporting_timezone_id on GET /v1/networks/info). Pass it explicitly for predictable totals.

​
Finding the timezone ID

Pick your timezone from the full reference below, or fetch the live list from GET /v1/meta/timezones.
Timezonetimezone_idUTC offset
Pacific/Kiritimati1UTC+14:00
Pacific/Enderbury2UTC+13:00
Pacific/Tongatapu3UTC+13:00
Pacific/Chatham4UTC+12:45
Pacific/Auckland5UTC+12:00
Pacific/Fiji6UTC+12:00
Asia/Kamchatka7UTC+12:00
Pacific/Norfolk8UTC+11:30
Australia/Lord_Howe9UTC+11:00
Pacific/Guadalcanal10UTC+11:00
Australia/Adelaide11UTC+10:30
Australia/Sydney12UTC+10:00
Australia/Brisbane13UTC+10:00
Australia/Darwin14UTC+09:30
Asia/Seoul15UTC+09:00
Asia/Tokyo16UTC+09:00
Asia/Hong_Kong17UTC+08:00
Asia/Kuala_Lumpur18UTC+08:00
Asia/Manila19UTC+08:00
Asia/Shanghai20UTC+08:00
Asia/Singapore21UTC+08:00
Asia/Taipei22UTC+08:00
Australia/Perth23UTC+08:00
Asia/Bangkok24UTC+07:00
Asia/Ho_Chi_Minh25UTC+07:00
Asia/Jakarta26UTC+07:00
Asia/Rangoon27UTC+06:30
Asia/Dhaka28UTC+06:00
Asia/Kathmandu29UTC+05:45
Asia/Colombo30UTC+05:30
Asia/Kolkata31UTC+05:30
Asia/Karachi32UTC+05:00
Asia/Tashkent33UTC+05:00
Asia/Yekaterinburg34UTC+05:00
Asia/Kabul35UTC+04:30
Asia/Baku36UTC+04:00
Asia/Dubai37UTC+04:00
Asia/Tbilisi38UTC+04:00
Asia/Yerevan39UTC+04:00
Asia/Tehran40UTC+03:30
Africa/Nairobi41UTC+03:00
Asia/Baghdad42UTC+03:00
Asia/Kuwait43UTC+03:00
Asia/Riyadh44UTC+03:00
Europe/Minsk45UTC+03:00
Europe/Moscow46UTC+03:00
Africa/Cairo47UTC+03:00
Asia/Beirut48UTC+03:00
Asia/Jerusalem49UTC+03:00
Europe/Athens50UTC+03:00
Europe/Bucharest51UTC+03:00
Europe/Helsinki52UTC+03:00
Europe/Istanbul53UTC+03:00
Africa/Johannesburg54UTC+02:00
Europe/Amsterdam55UTC+02:00
Europe/Berlin56UTC+02:00
Europe/Brussels57UTC+02:00
Europe/Paris58UTC+02:00
Europe/Prague59UTC+02:00
Europe/Rome60UTC+02:00
Europe/Lisbon61UTC+01:00
Africa/Algiers62UTC+01:00
Europe/London63UTC+01:00
Atlantic/Cape_Verde64UTC-01:00
Africa/Casablanca65UTC+00:00
Europe/Dublin66UTC+00:00
UTC67UTC+00:00
America/Scoresbysund68UTC+00:00
Atlantic/Azores69UTC+00:00
Atlantic/South_Georgia70UTC-02:00
America/St_Johns71UTC-02:30
America/Sao_Paulo72UTC-03:00
America/Argentina/Buenos_Aires73UTC-03:00
America/Santiago74UTC-03:00
America/Halifax75UTC-03:00
America/Puerto_Rico76UTC-04:00
Atlantic/Bermuda77UTC-04:00
America/Caracas78UTC-04:30
America/Indiana/Indianapolis79UTC-04:00
America/New_York80UTC-04:00
America/Bogota81UTC-05:00
America/Lima82UTC-05:00
America/Panama83UTC-05:00
America/Mexico_City84UTC-05:00
America/Chicago85UTC-05:00
America/El_Salvador86UTC-06:00
America/Denver87UTC-06:00
America/Mazatlan88UTC-06:00
America/Phoenix89UTC-07:00
America/Los_Angeles90UTC-07:00
America/Tijuana91UTC-07:00
Pacific/Pitcairn92UTC-08:00
America/Anchorage93UTC-08:00
Pacific/Gambier94UTC-09:00
America/Adak95UTC-09:00
Pacific/Marquesas96UTC-09:30
Pacific/Honolulu97UTC-10:00
Pacific/Niue98UTC-11:00
Pacific/Pago_Pago99UTC-11:00
UTC offsets reflect each zone’s currently-effective offset and shift with DST. Use the offset as a hint, not a contract — fetch live values from GET /v1/meta/timezones if your application depends on the offset.
To fetch programmatically, call GET /v1/meta/timezones — the response is { "timezones": [...] }. Match on the timezone field (IANA identifier) — never timezone_name, which is a display string that shifts with DST. 
curl -H "X-Eflow-API-Key: <key>" "https://api.eflow.team/v1/meta/timezones" \
  | jq '.timezones[] | select(.timezone == "America/New_York")'

​
Response timestamps

All response timestamp fields are Unix epoch integers in UTC — regardless of the timezone_id in the request. 
{
  "time_created": 1709500000,
  "conversion_unix_timestamp": 1771455532
}

​
Date strings in responses

Date strings appear in two specific places, both in YYYY-MM-DD HH:MM:SS format (no offset, no T separator): 1. Aggregated reports grouped by a time column — the string lives inside the columns array, bucketed by the request’s timezone_id: 
{
  "columns": [{ "column_type": "date", "id": "2026-04-15", "label": "2026-04-15" }],
  "reporting": { "total_click": 1200, "cv": 45, "revenue": 4500.00 }
}
2. Firehose stream — top-level date / click_date strings alongside Unix timestamps, in the network’s reporting timezone: 
{
  "transaction_id": "890c3d5...",
  "unix_timestamp": 1715788261,
  "date": "2024-05-15 15:53:19",
  "click_date": "2024-05-15 15:51:01"
}
Conversion list endpoints (/networks/reporting/conversions and peers) and conversion/event webhooks include Unix timestamps only — no date string.

​
Daylight saving time

Queries spanning a DST transition are bucketed correctly (pre-transition hours as standard time, post-transition as daylight time). date and hour strings reflect local wall-clock time across the shift. Unix timestamps remain UTC and are immune.