v2.102.0 - Load Driver & Vehicle TSP Identifiers

Released 16th October 2026 This release updates the driver and vehicle objects on POST /v2/visibility/loads. The eld_id field has been replaced by tsp_id and tsp_source_name, aligning load identifiers with the TSP-aware identifier model used across the rest of the API.

Breaking Change: eld_id has been removed from both the driver and vehicle objects in the request body and the 201 response. Replace it with tsp_id and, where known, tsp_source_name.

Breaking Changes

eld_id replaced by tsp_id and tsp_source_name on driver and vehicle

Updated endpoint:

POST /v2/visibility/loads

What changed:The eld_id field on both the driver and vehicle objects has been removed. In its place, two new fields are available:

tsp_id — the driver’s or vehicle’s ID as it appears in the TSP portal
tsp_source_name — the TSP source name (e.g. motive, samsara) that the ID belongs to

Request body — before:

{
  "load_ref": "BOL-482910",
  "driver": {
    "eld_id": "DRV-2087",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "phone_number": "+1 614-555-0142"
  },
  "vehicle": {
    "eld_id": "TRUCK-1042",
    "license_plate_number": "HMT-3570",
    "license_plate_region": "OH",
    "vin": "1FUJGLDR7CSBF1234"
  },
  "origin": { "latitude": 39.9612, "longitude": -82.9988, "name": "Columbus, OH" },
  "destination": { "latitude": 40.7357, "longitude": -74.1724, "name": "Newark, NJ" },
  "estimated_departure_at": "2026-08-14T12:00:00Z",
  "estimated_arrival_at": "2026-08-16T08:00:00Z"
}

Request body — after:

{
  "load_ref": "BOL-482910",
  "driver": {
    "tsp_id": "DRV-2087",
    "tsp_source_name": "motive",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "phone_number": "+1 614-555-0142"
  },
  "vehicle": {
    "tsp_id": "TRUCK-1042",
    "tsp_source_name": "motive",
    "license_plate_number": "HMT-3570",
    "license_plate_region": "OH",
    "vin": "1FUJGLDR7CSBF1234"
  },
  "origin": { "latitude": 39.9612, "longitude": -82.9988, "name": "Columbus, OH" },
  "destination": { "latitude": 40.7357, "longitude": -74.1724, "name": "Newark, NJ" },
  "estimated_departure_at": "2026-08-14T12:00:00Z",
  "estimated_arrival_at": "2026-08-16T08:00:00Z"
}

The same change applies to the 201 response — eld_id is no longer returned on driver or vehicle; tsp_id and tsp_source_name appear in its place.Impact:

Any integration that sends driver.eld_id or vehicle.eld_id must rename the field to tsp_id
tsp_source_name is optional but recommended — include it when you know which TSP the ID belongs to
Any integration that reads eld_id from the 201 response must be updated to read tsp_id

Migration Guide

Rename eld_id to tsp_id in your request body

In both the driver and vehicle objects, rename eld_id to tsp_id:

{
  "driver": {
    "tsp_id": "DRV-2087"
  },
  "vehicle": {
    "tsp_id": "TRUCK-1042"
  }
}

Add tsp_source_name where known

If you know which TSP the ID belongs to, include tsp_source_name alongside tsp_id:

{
  "driver": {
    "tsp_id": "DRV-2087",
    "tsp_source_name": "motive"
  },
  "vehicle": {
    "tsp_id": "TRUCK-1042",
    "tsp_source_name": "motive"
  }
}

Update response parsing

If your integration reads eld_id from the 201 response on driver or vehicle, update your parser to read tsp_id instead.

Overview

Authentication

Telematics

Organizations

Integrations

Notifications

Intelligence

v2.102.0 - Load Driver & Vehicle TSP Identifiers

Breaking Changes

Migration Guide

Need Help?

API Reference

Contact Support

​Breaking Changes

​Migration Guide

​Need Help?

API Reference

Contact Support

Breaking Changes

Migration Guide

Need Help?