The Optimization Swimlane API now returns travel distance and duration for each event in the schedule an optimization run proposes.
Each proposed event includes arriving and departing travel time in seconds and travel distance in meters, alongside the existing Job and Activity details. Historical events, which show the schedule before the run, don't include travel.
Why it matters
- Integrations can read a Resource's optimized schedule, travel included, from a single endpoint.
- Travel for each stop comes back with the schedule it belongs to, so there's nothing to match up separately.