Developers | Samsara

The documents endpoint now includes an optional query parameter to allow users to query documents by either their updatedAt value or createdAt value. This endpoint also now returns a serverCreatedAt and serverUpdatedAt timestamp. Documents that were created prior to tracking serverUpdatedAtMs will have a value of 0ms.

All sensor endpoints now include timestamps for the time that the value was read.

Now, you can find the automatic associations between vehicles and asset gateways within the API. You can find the current association on the assets endpoint and any historical associations on the trips endpoint.

The /v1/fleet/list endpoint now returns a list of tags that each vehicle is associated with.

You can now create, update, and delete contacts using the new contacts APIs.

We've corrected a developer experience issue in the document submission alert webhook. Previously we returned the driverCreatedAtMs field, but now we will return a driverId_driverCreatedAtMs field so that the webhook field matches the API-consumable field.

We've released a new API to fetch individual documents submitted by a given driver.

We've released a new set of APIs for user management within Samsara. Create, update, and delete users in your Samsara organization. This can be integrated with your identity provider platforms to manage account provisioning and permissions.

We've released a new set of APIs around driver messaging. Now you can send and retrieve messages to a driver or set of drivers using the new messages API.

The routes API now includes a document array that shows all documents that are submitted for a given route.