Route Optimization API release notes
Stay organized with collections
Save and categorize content based on your preferences.
Subscribe
to these release notes.
This page is updated with each new release of the
Route Optimization API. The changelog lists releases by date and includes
any new features, bug fixes and significant performance improvements.
You can also browse and filter all release notes for all products in the
Google API Console.
See the Overview documentation for information on how to get started
using the Route Optimization API.
May 13, 2025
April 01, 2025
Mitigate an issue where routes occasionally suggest a different arrival and departure location for a visit, even when the user has specified only one location for the visit request. When this issue happens, if the distance between arrival and departure locations is large, it can result in a fragmented route.
This mitigation results in smoother routes and can be visible in the API as reduced gaps in ShipmentRoute and Transition route polylines at Visit locations.
Previously, route polylines could have large gaps at Visit locations even when the VisitRequest arrival and departure locations or waypoints were set to be equal. This would generally happen when the VisitRequest location had multiple nearby roads or entrances as sometimes different navigation points would be chosen for arrival to and departure from the same location. This would result in a gap between the endpoints of incoming and outgoing route polylines for the Visit.
Now, suitable navigation points are chosen for VisitRequest locations before generating route polylines so the endpoints of incoming and outgoing route polylines for Visits (with equal arrival and departure locations) are likely to be closer together.
September 23, 2024
You can now generate route tokens using the Route Optimization API. Pass a route token to the Navigation SDK to guide how it routes your vehicle. For details, see Transition Polylines and Route Tokens.
July 01, 2024
May 15, 2024
Route Optimization API
Announcing the General Availability (GA) release of the Route Optimization API.
The Route Optimization API assigns tasks and routes to a vehicle fleet, optimizing against the objectives and constraints that you supply for your transportation goals.
If you are a new user, see Set up your Google Cloud project to start the development process.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[null,null,["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThis page provides release notes for the Route Optimization API, detailing new features, bug fixes, and performance improvements.\u003c/p\u003e\n"],["\u003cp\u003eThe Route Optimization API has reached General Availability and enables assigning tasks and routes to vehicle fleets with optimization based on user-defined objectives and constraints.\u003c/p\u003e\n"],["\u003cp\u003eA recent update allows route token generation for use with the Navigation SDK, guiding vehicle routing.\u003c/p\u003e\n"],["\u003cp\u003eIssues with duplicate input/output file URIs in BatchOptimizeToursRequest have been addressed for improved API functionality and error handling.\u003c/p\u003e\n"],["\u003cp\u003eUsers can subscribe to an XML feed to stay updated on the latest Route Optimization API releases.\u003c/p\u003e\n"]]],[],null,["# Route Optimization API release notes\n\n[Subscribe](/static/feeds/route-optimization-release-notes.xml)\nto these release notes.\n[](/static/feeds/route-optimization-release-notes.xml)\nThis page is updated with each new release of the Route Optimization API. The changelog lists releases by date and includes any new features, bug fixes and significant performance improvements. You can also browse and filter all release notes for all products in the [Google API Console](https://console.cloud.google.com/release-notes). See the [Overview](/maps/documentation/route-optimization/release-notes/overview) documentation for information on how to get started\nusing the Route Optimization API.\n\nMay 13, 2025\n------------\n\nFour new experimental features are now available.\n\nSee [U-turn Avoidance](https://developers.google.com/maps/tt/route-optimization/experimental/u-turn-avoidance/make-request), [Objectives](https://developers.google.com/maps/tt/route-optimization/experimental/objectives/make-request), [Single Non-Blocking Optimizations](https://developers.google.com/maps/tt/route-optimization/experimental/otlr/make-request) and [Load Costs](https://developers.google.com/maps/tt/route-optimization/experimental/load-cost/make-request).\n\nYou can access these features through our REST and gRPC endpoints. Client libraries are not yet available.\n\nApril 01, 2025\n--------------\n\nMitigate an issue where routes occasionally suggest a different arrival and departure location for a visit, even when the user has specified only one location for the visit request. When this issue happens, if the distance between arrival and departure locations is large, it can result in a fragmented route.\n\nThis mitigation results in smoother routes and can be visible in the API as reduced gaps in [ShipmentRoute](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#shipmentroute) and [Transition](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#transition) route polylines at [Visit](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visit) locations.\n\nPreviously, route polylines could have large gaps at [Visit](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visit) locations even when the [VisitRequest](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visitrequest) arrival and departure locations or waypoints were set to be equal. This would generally happen when the [VisitRequest](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visitrequest) location had multiple nearby roads or entrances as sometimes different navigation points would be chosen for arrival to and departure from the same location. This would result in a gap between the endpoints of incoming and outgoing route polylines for the [Visit](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visit).\n\nNow, suitable navigation points are chosen for [VisitRequest](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visitrequest) locations before generating route polylines so the endpoints of incoming and outgoing route polylines for [Visit](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#visit)s (with equal arrival and departure locations) are likely to be closer together.\n\nSeptember 23, 2024\n------------------\n\nYou can now generate route tokens using the Route Optimization API. Pass a route token to the Navigation SDK to guide how it routes your vehicle. For details, see [Transition Polylines and Route Tokens](https://developers.google.com/maps/documentation/route-optimization/polylines-and-route-tokens).\n\nJuly 01, 2024\n-------------\n\nFixed an issue where duplicate [`GcsSource`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#gcssource) `uri`s (which represent input files for the optimization requests) were accepted in [`BatchOptimizeToursRequest`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#batchoptimizetoursrequest) [`AsyncModelConfig`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#asyncmodelconfig)s for the `BatchOptimizeTours` API. Now [`GcsSource`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#gcssource) `uri`s\nmust be unique across all [`BatchOptimizeToursRequest`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#batchoptimizetoursrequest) [`AsyncModelConfig`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#asyncmodelconfig)s in a single `BatchOptimizeTours` API call. This is desirable behavior to avoid processing the same request twice in case of accidental input duplication. \nFixed an issue where duplicate [`GcsDestination`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#gcsdestination) `uri`s (which represent output files for the optimization responses) were accepted in [`BatchOptimizeToursRequest`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#batchoptimizetoursrequest) [`AsyncModelConfig`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#asyncmodelconfig)s for the `BatchOptimizeTours` API. Now [`GcsDestination`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#gcsdestination) `uri`s\nmust be unique across all [`BatchOptimizeToursRequest`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#batchoptimizetoursrequest) [`AsyncModelConfig`](https://developers.google.com/maps/documentation/route-optimization/reference/rpc/google.maps.routeoptimization.v1#asyncmodelconfig)s in a single `BatchOptimizeTours` API call. This is desirable behavior to fail the `BatchOptimizeTours` call earlier as the call will not be able to complete successfully if enough output files are not provided.\n\nMay 15, 2024\n------------\n\nRoute Optimization API\n\nAnnouncing the General Availability (GA) release of the Route Optimization API.\n\nThe Route Optimization API assigns tasks and routes to a vehicle fleet, optimizing against the objectives and constraints that you supply for your transportation goals.\n\nIf you are a new user, see [Set up your Google Cloud project](https://developers.google.com/maps/documentation/route-optimization/cloud-setup) to start the development process."]]