The result of an optimization contains a list of deliveries, i.e. shipments that can be deliveries, pickups or directs.

After the route is calculated, it includes the distance of the whole route in meters, the net_duration, which is the total driving time in minutes based on current on current traffic forecast and the gross_duration, meaning the total time needed for the route including the driver's length of stays based on the els (estimated length of stay) from the deliveries.

The routebase_address, set by its routebase_address_id - the starting location of the route, in most cases the depot. The routestring is a GeoJSON LineString that includes a set of geo-coordinates, that can e.g. be used to display the route on a map. The areatext contains a short auto generated description of the route.

The status entry holds information like driverassigned, canceled or finished. There is a list of all route status, which can also be accessed via an API endpoint.

To save some bandwidth, one can get only the route meta data without details.

As you may have already seen on the routing types page, there are a couple of different routing variants. You can find out, which one is suitable for a list of shipments with an API endpoint. If you have an already calculated route, of course you can request the distances between subsequent deliveries.

For time window routing, it's sometimes beneficial to update the estimated time of arrivals so they include the most recent traffic forecasts.
You get more information about the location of routes on a map, e.g. areas of a route.