Skip to main content
Released 19th October 2026 This release adds a new required stops field to the response schemas for both load tracking endpoints. The field lists the load’s stops in travel order. Estimated and actual arrival and departure times are not yet populated and are always null.
Minor Release: Backward-compatible addition. The stops field is new and required in the response schema; existing integrations that do not read it are unaffected.

​
Schema Changes

Updated endpoints:
  • GET /v2/visibility/loads/tracking
  • GET /v2/visibility/loads/{load_id}/tracking
What changed:Both load tracking response schemas now include a required stops field. The field lists the load’s stops in travel order. The endpoint descriptions have been updated to reflect this: “Each load also lists its stops in travel order. Their estimated and actual arrival and departure times are not populated yet, so they are always null.”Before:
After:
Impact:
  • stops is a new required field in the response schema for both endpoints
  • Stops are listed in travel order
  • estimated_arrival_at, actual_arrival_at, estimated_departure_at, and actual_departure_at are always null at this time
  • Integrations that do not read stops require no changes

​
Integration Notes

1

Read stops alongside other load tracking fields

The stops array is present on every load tracking response. Each entry represents a stop in travel order:
2

No action required for existing integrations

The stops field is additive. If your integration does not read it, no changes are needed.

​
Need Help?

API Reference

View complete endpoint documentation for the Visibility API

Contact Support

Questions about your integration? Our team is here to help