Drive time and on-duty time
The /v1/fleet/drivers/{driver_id}/hos_daily_logs endpoint now includes drive time and on-duty time in daily logs. Additionally, pending carrier edits to daily logs are also now available.
The /v1/fleet/drivers/{driver_id}/hos_daily_logs endpoint now includes drive time and on-duty time in daily logs. Additionally, pending carrier edits to daily logs are also now available.
We’ve launched a new and improved API, featuring standardized pagination, human-readable timestamps, nested objects, and more! Check out this FAQ to find out more. The resources available from this new API include Addresses, Contacts, Drivers, Tags, Users, and Vehicles - with more to come!
We've released a new version of the API on 2019-09-13: The HOS authentication log endpoint has been updated to reflect the Driver Hours of Service Audit Report in the dashboard. This removes potentially duplicate sign-out events.
We've released a new version of the API on 2019-08-21: On the HOS audit logs event, the logStartMs value for the "Driver Signout" event now reflects the time a vehicle assignment ended, rather than the time a vehicle assignment started, to more clearly reflect the driver's signout time.
We've released a new version of the API on 2019-07-30: The HOS logs summary endpoint now leverages pagination on drivers for a more performant call.
There will now be color data available in the machine vision APIs.
We've released a new version of the API on 2019-07-17: This should only impact a small set of customers who are currently using our beta endpoint for HOS audit logs. This endpoint now uses the log's createdAtMs timestamp rather than the logStartMs to determine the time range of logs to fetch.
The documents endpoint now includes an optional query parameter to allow users to query documents by either their updatedAt value or createdAt value. This endpoint also now returns a serverCreatedAt and serverUpdatedAt timestamp. Documents that were created prior to tracking serverUpdatedAtMs will have a value of 0ms.
Now, you can find the automatic associations between vehicles and asset gateways within the API. You can find the current association on the assets endpoint and any historical associations on the trips endpoint.
All sensor endpoints now include timestamps for the time that the value was read.