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.
The GET /addresses endpoint now allows you to filter by tags.
The Documents API now supports date-time fields in custom document templates.
Two new fields have been added to the machine vision APIs:
New vehicle location API endpoints are available that provide three ways of getting location data:
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.
