The GET fleet/documents endpoint is now generally available and fully supported for production 🎉! Check it out and happy coding 💻

The GET fleet/document-types endpoint is now generally available and fully supported for production 🎉! Check it out and happy coding 💻

The new implementations of the Documents APIs will move from Beta to General Availability soon! These new implementations follow Samsara's updated REST API standards. The endpoints moving into General Availability include: List document types, Create a document, Retrieve a document, Delete a document, and List documents. When these endpoints move into General Availability, the endpoint URLs will no longer be prefixed with /beta, so make sure to update any code you've written accordingly! The new Generally Available endpoints will be fully supported for production integrations and any changes to them will be subject to Samsara's Versioning policy. Another changelog entry will be posted when these endpoints are moved into General Availability. You can read more about Samsara's API release process here.

The Drivers APIs now support driver-specific ELD ruleset overrides. (This is only relevant to US customers). A driver's usDriverRuleSetOverride will contain the ELD ruleset that overrides the organization's default ruleset. This field will be omitted from the driver if no override is set. You can read this field via the list and retrieve drivers APIs. You can set this field upon creation of a driver or update the field of an existing driver. To unset the field, set usDriverRulesetOverride to null in your update request. Check out the docs for full details 👀

The Drivers APIs now support two new fields: carrierSettings.homeTerminalName and carrierSettings.homeTerminalAddress. Check out the docs for full details 👀

❗️

TLS 1.1 and TLS 1.0 is Now Deprecated

TLS 1.0 and 1.1 was deprecated on 9/29/21 at 10 AM PST. If your integration started receiving errors starting around this time, refer to the guidance below on how to troubleshoot and upgrade to TLS 1.2 or above.

If additional assistance is needed, reach out to Samsara Support.

The Vehicle Stats APIs will now include Address/Geofence information when you query for gps data. If the gps ping occurred within a known Address/Geofence, the ping will include an address field, returning the ID and name of the Address.

The gps stat type for the Vehicle Stats APIs now includes an isEcuSpeed field to indicate whether the speedMilePerHour field was generated by the ECU or has been calculated based on GPS data.

All the new Routes API endpoints are now generally available (GA). These are new implementations of the legacy v1 Routing APIs. You can view the complete list in the Routes Reference Section. These new implementations of the Routing APIs follow Samsara's latest REST API standards and patterns for pagination and update feeds. An exciting new feature of the Get route updates endpoint is that the audit log of stop updates includes details about whether the stop update was triggered through the driver app, through the admin dashboard, or automatically. Updates are also triggered when an admin manually updates a stop's arrival or departure time (a highly requested feature 🎉). Check out the newly updated Routing Use Case guide as well 👀

Three new Beta APIs are now available: Get trailer stats snapshot, Get trailer stats feed, and Get trailer stats history. These APIs allow you to request telematics data for Trailers, using the same query patterns as the Vehicle Stats APIs (see this guide for an overview). These Beta APIs are available to give you an opportunity to test and provide feedback, but should not be used in production applications. See the API Release Cycle for more details.