stop_type field to intermediate stops on the POST /v2/visibility/loads endpoint, allowing callers to indicate the purpose of each stop along a load’s route.
Minor Release: Backward-compatible addition. Existing integrations that omit
stop_type are unaffected.New Features
stop_type on intermediate load stops
stop_type on intermediate load stops
Updated endpoint:Request body — after:The
POST /v2/visibility/loads
stops array in both the request body and the 201 response now supports an optional stop_type field on each intermediate stop. This lets you describe what a stop is for — for example, a fuel stop or a rest break.Request body — before:stop_type field is also returned on each stop object in the 201 response, so callers can confirm the value was recorded.Impact:stop_typeis optional — omitting it behaves exactly as before- No changes to required fields or existing response structure
Integration Notes
1
Add stop_type to intermediate stops (optional)
If you want to label what each stop is for, include
stop_type in the stop object when creating a load:2
No action required for existing integrations
The
stop_type field is fully optional. Loads created without it continue to work without any changes.Need Help?
API Reference
View complete endpoint documentation for the Visibility API
Contact Support
Questions about your integration? Our team is here to help