Integrate your data with the Samsara API, customize the Samsara experience, and join a community of developers building with Samsara.
The Drivers APIs now support a deactivatedAtTime field that indicates when a driver was deactivated.
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.
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.
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.
Tag names can now function as automatic external IDs. For example, you can retrieve a tag by its name:
The following vehicle diagnostic types are now available via API. See the Telematics guide for full details.
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.
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.:
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.
We've released a new beta API endpoint that returns all vehicles' driver assignments for a given time period. You can view the reference documentation here. Note: This API is in beta and is likely to change before it enters a broader release. This beta release gives you the opportunity to experiment and provide feedback – before the final release. The final release will be announced via another changelog entry.