The GET places endpoint is now in the Beta stage. Feel free to send in your comments via our feedback form. (Note this endpoint should not be used in production until it is made generally available).
The DELETE places endpoint is now in the Beta stage. Feel free to send in your comments via our feedback form. (Note this endpoint should not be used in production until it is made generally available).
The PATCH places endpoint is now in the Beta stage. Feel free to send in your comments via our feedback form. (Note this endpoint should not be used in production until it is made generally available).
The POST places endpoint is now in the Beta stage. Feel free to send in your comments via our feedback form. (Note this endpoint should not be used in production until it is made generally available).
The GET maintenance/work-orders endpoint has some new features! Added a new optional timeEntries array to each service task instance on a work order. Each entry represents a technician work session clocked in against that service task, with the following fields:
The GET maintenance/work-orders/stream endpoint has some new features! Added a new optional timeEntries array to each service task instance on a work order. Each entry represents a technician work session clocked in against that service task, with the following fields:
We've released a new version of the API. This version updates the behavior of the GET fleet/equipment/stats endpoint: Previous API versions surfaced J1939 engine seconds under gatewayEngineSeconds. Starting in this version, J1939 values are returned only in gatewayJ1939EngineSeconds.
The GET alerts/incidents/stream endpoint has some new features! The following options have been added to the details field:
The GET assets endpoint has some new features! Added an optional includeAttributes query parameter that, when set to true, returns the list of attributes associated with each asset in the response.
The GET ridership/route-setups/.routeId endpoint has some new features! The routeId path parameter now accepts either a Samsara ID or an external ID in key:value format (e.g. extRoute:WB-12). Existing callers using numeric IDs are unaffected.
