Step 5. Track vehicles and assets.

Plan a dispatch by tracking vehicles and assets. In this step, use GET calls to retrieve vehicle locations and then asset locations.

Having completed setup, your system is synchronized with KeepTruckin. Beginning with this step, you use the core functions that constitute your day-to-day operations.

To effectively plan a dispatch, you need current information about drivers, vehicles, and assets. KeepTruckin's ELD and mobile app continuously record vehicles’ and drivers’ locations. You can use the ‘_locations’ set of endpoints to get current locations of all company vehicles, a vehicle's location history for a specific day, and current locations of all company drivers and assets. Begin by retrieving information about the vehicles in your fleet.

Track Vehicles: GET https://api.keeptruckin.com/v1/vehicle_locations

This GET call tracks all the vehicles for your fleet, their current location, driver, and other details. Optionally filter the query by the vehicle ID(s) or by vehicle status. The response returns vehicle details such as its number, ID, year, model, make, etc.; its current location including the latitude and longitude, location description, the vehicle’s behavior and state in that location; and its current driver with details such as name, contact information, and status.

Now let’s do the same for the assets in your fleet:

Track Assets: GET https://api.keeptruckin.com/v1/asset_locations

This GET call retrieves details about trailers, cranes, and other hardware that may be attached to a vehicle. The response includes static details about the asset, such as its ID, status, type, model, dimensions, and notes about it. The payload also includes details sent by the asset gateway, such as its last location, ground speed, and battery capacity.

📘

Learn more

Read our reference documentation about the Locations object, the Vehicle Locations endpoint, and the Asset Locations endpoint for details.

Language
Authentication
Header
Click Try It! to start a request and see the response here!