added

Daily Driver Activity API

The new Get all driver HOS daily logs API endpoint allows you to get a daily summary of activity for each driver. Check out the Daily Duty Status Summaries API Guide for more details and sample code.

added

Driver deactivatedAtTime

The Drivers APIs now support a deactivatedAtTime field that indicates when a driver was deactivated.

added

External IDs in Routes and Route Stops

External IDs are now supported for both the top-level Route object as well as each route stop in the dispatch_jobs array. See the Routing Guide for some example code.

Rate Limit Updates

We've updated the API rate limit policy. We will now enforce rate limits on a per-endpoint basis, in addition to the existing global rate limits. For example, the global rate limit is 200 requests per second, but the /fleet/hos/logs endpoint is rate-limited at 30 requests per second. See the Rate Limits page for full details.

added

Driver ID Card Code in Drivers APIs

The Drivers APIs will now return a currentIdCardCode string field that contains the NFC ID card code for each driver. This card code also shows up in the Vehicles Stats APIs when you query for types= nfcCardScans.

added

Tag Name as Automatic External ID

Tag names can now function as automatic external IDs. For example, you can retrieve a tag by its name:

added

More vehicle diagnostics available via API

The following vehicle diagnostic types are now available via API. See the Telematics guide for full details.

added

Camera Media Endpoint

The GET /fleet/vehicles/cameras/media/history endpoint has been officially released. It allows you to get images from all dashcams in your fleet. Only images are currently available.

added

Driver ↔️ Vehicle Assignments

There are two new API endpoints that allow you to retrieve the driver(s) of each vehicle for a given time period and vice versa.:

added

Synthetic Engine Hours in Vehicle Stats

Synthetic engine hours are now available from the Vehicles Stats API endpoints. You can include the query parameter types=syntheticEngineSeconds to get synthetic engine runtime if engine runtime from the ECU is unavailable. This value is approximated by the time the vehicle gateway receives power from the vehicle. See this article for details on synthetic engine runtime. See the Telematics API guide for how to use the types=syntheticEngineSeconds query parameter and details on the telematics API endpoints.