Changelog

The /v1/fleet/locations endpoint now returns a list of all active routes that the vehicle is traveling on.

We've released new endpoints to manage driver accounts via API. Now you can programmatically update driver information, such as driver password, in order to keep your driver records up-to-date.

We've released a new version of the API on 2019-02-22: If there is no value for a field in the Drivers object, then the Driver object will not show the given field. Previously, this field would be visible with a null value. You can upgrade your API token on your admin dashboard to receive this change.

The /v1/fleet/locations endpoint now returns information about the vehicle odometer.

Manage your address book using the new addresses APIs.

We have released pagination support for the APIs that provide multiple resources. This is now available on the /v1/fleet/list endpoint, and we will continue to add pagination support to all our long-resourced endpoints.

You can now assign custom external identifiers for drivers and vehicles within Samsara. External IDs are customer-specified key-value pairs that allow you to grab Samsara objects.

With webhooks, developers can now receive and build upon alert notifications via a webhook event. This is particularly useful for building integrations that rely on alerts for special events, like a vehicle arriving at a given location, or temperature exceeding a specified set temperature. For more information on how to create and configure your webhook, check out the documentation here.

The initial release of the Samsara API.