The tour and booking ETA notifications now arrive when there is something new to tell. Every notification your integration receives carries estimates that differ from the previous one, so there is less traffic to process and every delivery is worth acting on.
What changes
While a tour is on its way, the platform recalculates its ETAs every few minutes.
Until now, each of these periodic recalculations sent
tour.etas_recalculated1 and
booking.etas_recalculated2, even when every expected
arrival time came out exactly as before.
From this release, a periodic recalculation only sends the notifications when the estimates actually changed:
- the expected arrival time of at least one stop moved, compared to the minute, or
- the stops still expecting an arrival are different: added, removed or reordered.
When a driver keeps to the predicted pace, the estimates stay put and no notifications go out until they move again.
What stays the same
Recalculations caused by a change to the tour itself still send the notifications every time: a stop being completed, stops being added, removed or reordered, or the tour setting off or being cancelled.
The payloads are unchanged: the tour notification carries route_estimates and
the booking notification its unfinished_stops_info, exactly as before.
Please check your integration
If your integration treats the ETA notifications as a regular heartbeat, for example to decide that estimates are stale when no notification arrived for a while, please adjust it: a quiet period now means the estimates have not changed. The latest estimates remain available at any time from Fetch estimated arrival times for stops3 (or Fetch estimated arrival times for multiple bookings at once4 for several records at once).