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).
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.
New vehicle stat API endpoints are available that include data about engine states, fuel percents, odometer values, and engine hours. These endpoints provide three ways of getting vehicle stat data:
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.
Group IDs are no longer required by any API endpoint. Note: group IDs are still accepted to maintain support for legacy integrations, but new integrations should not use group IDs. The API token will encapsulate all identifying information about an organization. Tags should be used for organizing data within an organization.
The DVIRs API now supports defect resolution by included resolved by information on DVIR defects and allowing you to include a list of defects to resolve when creating a new DVIR.
