Step 3. Start tracking the vehicle of your choice by subscribing to its location.

Having received a list of the vehicles best matched to your pickup needs, you can now create a vehicle tracking event. Do this to confirm that the vehicle you’re tracking will arrive in time.

Once again, specify the carrier by providing one of the two types of IDs:

  • company_id: KeepTruckin’s ID for that carrier
  • dot_id: Federal ID(s) for that carrier

Specify which vehicle you’re tracking by providing one of these three parameters:

  • vehicle_id: KeepTruckin’s ID for the vehicle
  • vehicle_name: This may be the fleet’s or the broker’s internal ID for the vehicle
  • driver_id: ID of the driver currently driving the vehicle to be tracked

Provide also a start and end time for tracking, where the start_time is the earliest time that tracking should begin; the end_time is the estimated load completion time.

You can also pass in the load_id for client side tracking; and any notes you want passed through as updates come in, using the load_details parameter.

You can define the initial and final stops, enabling KeepTruckin to calculate ETAs throughout the lifecycle of the load. You can provide optional parameters such as the total distance of the trip for client-side tracking, as well as any kind of trailer ID to track.

The response payload contains a unique ID for your subscription: tracking_subscription_id. You can use this in later steps to modify or stop your tracking.

Note: You can just as easily use this endpoint to track an asset rather than a vehicle. Simply subscribe by providing the asset_id instead of a vehicle_id or vehicle_name.

📘

Learn more

Read our reference documentation about the Subscribe endpoint for details.

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