Integrate your data with the Samsara API, customize the Samsara experience, and join a community of developers building with Samsara.
All API endpoints now support a parentTagIds query parameter. This parameter allows you to filter the data to a list of parent tag IDs and automatically includes the data in the descendants of those tags.
The Vehicles APIs now automatically support VIN as an external ID using the pattern: samsara.vin:1HGBH41JXMN109186. Read more about external IDs on developers.samsara.com.
The PATCH /fleet/drivers/{id} endpoint now allows you to deactivate drivers by setting the driverActivationStatus field to deactivated. Additionally the Drivers API endpoints now support querying by this driverActivationStatus field.
The Drivers API now provides timestamps for when Drivers where created and updated, as well as filtering the list of drivers by those timestamps in the GET /fleet/drivers endpoint.
All tag fields will now include the ID of the parent tag. This means that whenever an object is part of a given tag, it will include the parent tag ID as well.
The GET /v1/fleet/assets/locations and the legacy GET /v1/fleet/locations endpoints now support filtering by tags.
The machine vision APIs will now include a URL to the image.
The machine vision APIs now provide two new fields regarding threshold:
The Vehicle Locations endpoints now include a reverse geocoded street address with each location.
The GET /v1/fleet/assets/locations endpoint now supports optional pagination for increased performance and reliability. You may provide an optional “limit” parameter to request only a certain number of location records per response. Including a “limit” parameter will provide a “pagination” object in the response to allow you to paginate through data using a cursor. If a “limit” parameter is not provided, the response will not be paginated (original behavior).