Dates and Timezones

All date handling in the Partner API follows two simple rules.

Rule 1: ISO 8601, always

• Calendar dates — YYYY-MM-DD (e.g. 2026-04-01).
• Instants — full ISO-8601 with a trailing Z (e.g. 2026-04-21T09:47:11.000Z). All instants are UTC.

A date in the wrong format returns 400 INVALID_DATE. A range with from > to returns 400 INVALID_DATE_RANGE.

Rule 2: impressions use the device's local timezone

The impressions endpoints (/v1/partner/assets/:id/impressions/*) bucket data by the device's detected local timezone, not UTC.

This matters most for mobile assets: a truck reporting impressions at 11pm local time on Aug 14 counts toward Aug 14, not Aug 15 UTC. Query from_date=2026-08-14&to_date=2026-08-14 and you get the device's day, wherever it was.

For static assets this is a wash — the device timezone matches whatever region you'd expect.

Ranges

All endpoints accept inclusive from_date and to_date. Both dates are included in the result.

Future dates

We gapfill impressions through the end of the queried range. That means a response may contain dates in the future with impressions: 0. Treat them as "no data yet" and filter client-side if you prefer.