Time Zone
The date and time specified in either the request parameters or the date or time attributes returned in the API responses are in UTC, unless a time zone is specified in an HTTP header.
| Header Name | Value |
|---|---|
| X-Time-Zone |
We support the following values in the X-Time-Zone header:
| Header Value | UTC OFFSET |
|---|---|
| Atlantic Time (Canada) | UTC -4, uses DST |
| Eastern Time (US & Canada) | UTC -5, uses DST |
| Indiana (East) | UTC -5, uses DST |
| Central Time (US & Canada) | UTC -6, uses DST |
| Saskatchewan | UTC -6, no DST |
| Mountain Time (US & Canada) | UTC -7, uses DST |
| Arizona | UTC -7, no DST |
| Pacific Time (US & Canada) | UTC -8, uses DST |
| Alaska | UTC -9, uses DST |
curl -H 'X-Api-Key: 24eb4181-ee55-446b-a25b-b39777cf4d8d' -H 'X-Time-Zone: Alaska' 'https://api.gomotive.com/v1/users'
IMPORTANT
Some Motive Public API endpoints return pre-aggregated rollup data instead of raw events. For these rollup endpoints, timestamps are computed and returned in the company's configured rollup timezone (for example in PT, MT, ET, and CT), and not in UTC and are not controlled by the X-Time-Zone header. Examples include endpoints such as driver_utilization and vehicle_utilization.
Updated 4 days ago