Avoiding U-turns in Route Optimization API

We are using the Route Optimization API with calc_points to order a list of destinations and get an outline of the route path. We’ve noticed a lot of u-turns on the solution.

I know there is a pass_through flag on the Routing API that fixes this perfectly. Is there a way to add the same restriction to a Route Optimization call?

Thanks.

As soon as you use the curbside feature it will also avoid U-turns at the stops. Read more about it here.

If it still does not work please include a small JSON example so that I can take a look.

Thanks. Setting curbside=right does fix it. Does that mean that with curbside=any it’s not possible to avoid the u-turn problem?

At least a single curbside=right or left must be used somewhere in the request (e.g. it should also work to specify this for the vehicle start location only)

I’m getting an error using curbside with tomtom consider_traffic. Are those incompatible?

Yes, unfortunately you can currently only use the curbside feature with OpenStreetMap.