We've released a new version of the API on 2019-11-19: Trips will now return latitude and longistude if reverse geocoding fails, whereas previously the start and end locations would be empty. This affecte the GET /v1/fleet/trips endpoint.
We've released a new version of the API on 2019-09-30: Messages are now limited to 2500 characters. This affects the POST /v1/fleet/messages endpoint, which creates new messages. Users will now receive a 400 error if they try to create messages over 2500 characters.
We've released a new version of the API on 2019-09-13: The HOS authentication log endpoint has been updated to reflect the Driver Hours of Service Audit Report in the dashboard. This removes potentially duplicate sign-out events.
We've released a new version of the API on 2019-08-21: On the HOS audit logs event, the
logStartMs value for the "Driver Signout" event now reflects the time a vehicle assignment ended, rather than the time a vehicle assignment started, to more clearly reflect the driver's signout time.
We've released a new version of the API on 2019-07-30: The HOS logs summary endpoint now leverages pagination on drivers for a more performant call.
We've released a new version of the API on 2019-07-17: This should only impact a small set of customers who are currently using our beta endpoint for HOS audit logs. This endpoint now uses the log's createdAtMs timestamp rather than the logStartMs to determine the time range of logs to fetch.
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
serverUpdatedAt timestamp. Documents that were created prior to tracking
serverUpdatedAtMs will have a value of 0ms.
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.
You can now create, update, and delete contacts using the new contacts APIs.
The fleet list endpoint now returns a list of tags that each vehicle is associated with.
The routes API now includes a documents array that shows all documents that are submitted for a given route.
The vehicles stats endpoint now returns information on external IDs.
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.
Fetch trailer assignment data using the new trailer assignment API.
The fleet locations endpoint now returns a list of all active routes that the vehicle is traveling on.
The routing APIs now include
odometer_end_meters to give you more visibility into distance traveled by a given vehicle.
The trips API now includes information about co-driving passengers during a given driving segment.
We've released a new endpoint 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 fleet locations endpoint now returns information about the vehicle odometer.
Routes can now be assigned to trailers, alongside vehicles and drivers.
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.
We have released pagination support for the APIs that provide multiple resources. This is now available on the
/fleet/list endpoint, and we will continue to add pagination support to all our long-resourced endpoints.
Manage your address book using the new addresses APIs.
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.