added

Delete recurring routes via API

You can now delete recurring routes via the DELETE /v1/fleet/dispatch/routes/{id} endpoint by setting apply_to_future_routes to true in the request body. For example

added

Additional Auxiliary Inputs

The new Auxiliary Input Hub accessory allows you to connect up to eight additional auxiliary inputs to the Samsara Vehicle Gateway. Data from these additional inputs are now available in all three Vehicle Stats endpoints as stat types auxInput3-auxInput10. See the Vehicle Stats reference docs for a full list of stat types.

added

Engine RPM

Engine RPMs are now available in all three Vehicle Stats APIs by including types=engineRpm as a query parameter. See the Vehicle Stats reference documentation for a full list of vehicle stats.

added

GPS in Vehicle Stats APIs

GPS data is now available in the Vehicle Stats APIs. The types=gps query parameter will allow you to request GPS data including lat/long, heading, speed, and reverse geocoded address data. This is available for the snapshot, feed, and history vehicle stats endpoints.

added

Hours of Service Clocks API

A new Hours of Service Clocks endpoint is available that allows you to retrieve the current duty status of all your drivers.

added

Hours of Service API

A new Hours of Service endpoint is now available. This endpoint allows you to retrieve duty status logs for all drivers between a given start time and end time.

added

Safety Events API

A new Safety Events endpoint is now available. This endpoint allows you to query for all safety events over a given time range.

added

ID Card Scans

ID card scan events are now available via the Vehicle Stats endpoints. The types=nfcCardScans query parameter will retrieve ID card scan events for the snapshot, feed, and history Vehicle Stats endpoints.

added

Camera Serial

If a Vehicle has a camera installed, the camera's serial number will be available as the cameraSerial field in the GET /fleet/vehicles and GET /fleet/vehicles/{id} endpoints.

improved

Route Completion

Routes will now automatically complete upon arrival at the last stop. The complete_last_stop_on_arrival field allows you to control this behavior. If set to true (default), the route will complete upon arrival at the last stop. If set to false, the last stop will capture arrival and departure separately (as with other stops) and the route as a whole will complete upon departure from the last stop. See the Routes reference documentation for details.