Waypoint timestamps in Azure Maps "Post Route Directions Batch" endpoint

Hello @Jeff Haacke

Thank you for reaching out to Microsoft Q&A.

Based on the current Azure Maps Route Directions Batch API behavior and documentation, waypoint arrival timestamps are not returned as standalone properties on the waypoint objects themselves. Instead, Azure Maps provides timing information at the route leg level, and waypoint arrival times must be derived from those leg timestamps.

How Azure Maps Represents Waypoint Timing

When you submit a route containing multiple waypoints, the service breaks the route into a series of legs, where each leg represents the segment between two consecutive waypoints.

For each leg, the response can include timing information such as:

"legs": [
  {
    "departureAt": "2026-06-19T10:00:00Z",
    "arrivalAt": "2026-06-19T10:15:00Z"
  },
  {
    "departureAt": "2026-06-19T10:15:00Z",
    "arrivalAt": "2026-06-19T10:30:00Z"
  }
]

In this example:

Therefore:

• The arrivalAt/arrivalTime value of a leg corresponds to the arrival time at the destination waypoint of that leg.
• The departureAt/departureTime value corresponds to the departure from the starting waypoint of that leg.
• There is currently no dedicated waypoint timestamp field returned in the response payload.

If You're Not Seeing Arrival/Departure Times

To receive time-based routing information, ensure your request includes appropriate time-calculation parameters, such as:

• departAt
• arriveAt
• computeTravelTimeFor=all
• Traffic-aware routing options when applicable

These parameters allow the service to calculate ETA-related values and populate the leg timing information.

Recommended Approach

If your application requires explicit timestamps for each waypoint:

1. Request route details that include route legs.
2. Read the legs[] collection in the response.
3. Map each leg's arrivalAt (or arrivalTime) to the destination waypoint of that leg.

For example:

Based on the current Azure Maps Route Directions Batch API schema, there is no documented parameter that adds standalone timestamps directly to waypoint objects. The supported method is to derive waypoint arrival times from the route leg timing information.

If you're not seeing a legs collection or any arrival/departure timestamps in your response, please share a sanitized sample request (including any route output options being used), and we can help verify whether additional route output settings are required.

Please refer this Azure Maps Route Directions Batch API Documentation

I Hope this helps. Do let me know if you have any further queries.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thank you!

Hello Jeff Haacke,

Greetings! Thanks for raising this question in Q&A forum.

The reason you cannot find a "waypoint timestamp" is that Azure Maps does not return them as a separate field. Instead, the route response is broken into legs, and each waypoint you add in your request automatically creates a new leg in the response. The arrival time at a waypoint is simply the arrivalTime found inside that leg's summary, and the departure time from that waypoint is the departureTime of the next leg.

Here is how you can get those timestamps.

Check your request has multiple points In your "query" parameter, make sure you are passing the waypoints in order, for example start:waypoint1:waypoint2:end. Each colon separated point becomes a leg boundary.

Look inside "legs" not "summary" In the response, ignore the top level "summary" block (that one only covers the full route). Instead open the "legs" array. You will see one leg object per waypoint to waypoint segment.

Read the arrival and departure time per leg Each leg has its own: "summary": { "departureTime": "...", "arrivalTime": "..." } The arrivalTime of leg 1 tells you when you arrive at waypoint 1, the arrivalTime of leg 2 tells you when you arrive at waypoint 2, and so on. The arrivalTime of the last leg is your arrival at the final destination.

Make sure timestamps are being calculated If departureTime and arrivalTime are missing even inside legs, add the parameter computeTravelTimeFor=all and optionally traffic=true to your request, and also pass a valid departAt or arriveAt value so the service knows the time base to calculate from.

Double check this in the Batch response Since "Post Route Directions Batch" just wraps multiple individual route responses, the same structure applies. Open batchItems[i].response.routes[0].legs, and read the summary inside each leg the same way as above.

You can see a sample response with this leg structure here: https://learn.microsoft.com/en-us/rest/api/maps/route/post-route-directions-batch-sync

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.