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.

The GET /hos/daily-logs endpoint has been updated to include an optional parameter expand=vehicle parameter and the following additional response body fields: adverseDrivingClaimed, bigDayClaimed, isUsShortHaulActive, carrierName, carrierFormattedAddress, carrierUsDotNumber, homeTerminalName, homeTerminalFormattedAddress. Details below! 🔎

Three new Routes API endpoints are now generally available (GA). These are new implementations of the legacy v1 Routing APIs. The endpoints that are now generally available are: Create a route, Update a route, and Get route updates. The rest of the latest generation of Routing APIs are still in Beta. They are available for testing and feedback, but they are subject to change before they are made generally available. These endpoints include: [beta] Fetch all routes and [beta] Fetch a route. These new implementations of the Routing APIs follow Samsara's latest REST API standards and patterns for pagination and update feeds.

The gps.speedMilesPerHour vehicle stat endpoints will now display ECU speed if Samsara has the ability to retrieve it from the vehicle. If Samsara cannot retrieve ECU speed, the field will display GPS-calculated speed. Previously, this field displayed GPS-calculated speed even if ECU speed was available.

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.