Changelog

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).

The Addresses API now supports external IDs.

We’ve released a new version of the API on 2019-12-12. This should only impact a small set of customers who are currently using our beta endpoint for unassigned driving segments. The updated endpoint now reports composite unassigned driving segments if applicable when querying for an unassigned driving segment by id. The endpoint can now return a new status called 'MULTIPLE', which indicates that the unassigned driving segment has multiple composite segments; composite segments will be returned nested under a new field called 'segments'. Unassigned driving segments will now also return a string representing duty status.

Raw GPS distance is now available in the Vehicle Stats endpoints. This statistic provides the distance the vehicle has traveled based on GPS calculations.

We’ve released a new version of the API on 2019-12-07. This new version adds pagination to the GET /v1/fleet/locations endpoint. This pagination is meant to provide an easy way to increase performance and reliability for existing integrations using the GET /v1/fleet/locations endpoint. However, the new Vehicle Location endpoints are still recommended for new integrations.