Developers | Samsara

We've released two new API endpoints for IFTA reports!

You can now preview our designs for a set of /gateways APIs that allow you to list, activate, and deactivate Samsara gateways programmatically. This would allow you to automate gateway installation and management. Check out the preview design, and use the feedback form to send in feedback and express interest in beta-testing.

We've improved the error codes that get returned for a couple of different scenarios in the Documents APIs:

We've released a new version of the API. This version updates the behavior of the Retrieve a unit of equipment API endpoint. Previously, this endpoint worked for any gateway within Samsara. This was not intended behavior. Now the endpoint only works for Equipment: assets connected to a Samsara Asset Gateway (AG) via APWR, CAT, or J1939 cables.

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.

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: