POST /v2/visibility/loads endpoint. The top-level license_plate_number, license_plate_region, and vin fields have been removed and replaced by a nested vehicle object. A new driver object has also been added, allowing you to associate a driver with a load at creation time.
Breaking Changes
Vehicle fields moved into nested vehicle object
Vehicle fields moved into nested vehicle object
Updated endpoint:Request body — after:The same restructuring applies to the
POST /v2/visibility/loads
license_plate_number, license_plate_region, and vin fields have been removed. These values are now provided inside a vehicle object alongside the existing eld_id field.Request body — before:201 response — license_plate_number, license_plate_region, and vin are no longer returned at the top level; they appear inside the vehicle object.Impact:- Any integration that reads or writes
license_plate_number,license_plate_region, orvinat the top level must be updated - The
vehicleobject is optional — omit it entirely if you have no vehicle details to send
New Features
Driver object on load creation
Driver object on load creation
Updated endpoint:The
POST /v2/visibility/loads
driver object can now be included when creating a load. This lets you associate a driver with the load at creation time using any combination of identifiers you have available.Request body example:driver object is also returned in the 201 response, confirming the values were recorded.Impact:driveris optional — omitting it behaves exactly as before- Send only the driver identifiers you know; all fields within the object are optional
Migration Guide
1
Move vehicle fields into the vehicle object
Replace any top-level If you were also sending an ELD vehicle identifier, include it in the same object:
license_plate_number, license_plate_region, and vin fields with a vehicle object:2
Update response parsing
If your integration reads
license_plate_number, license_plate_region, or vin from the 201 response body, update your parser to read them from response.vehicle.license_plate_number, response.vehicle.license_plate_region, and response.vehicle.vin respectively.3
Optionally add driver details
If you have driver information available at load creation time, you can now include it in the
driver object. This step is optional and does not affect existing integrations.Need Help?
API Reference
View complete endpoint documentation for the Visibility API
Contact Support
Questions about migrating your integration? Our team is here to help