Upcoming changes to Bing Maps Calculate a Route API Parameter on 7/20/2025

Question

Upcoming changes to Bing Maps Calculate a Route API Parameter on 7/20/2025

Srijit Lahiri 20

Hi,

We have received communications on upcoming changes to the Bing Places Calculate a Route API and being an existing subscriber to the API would like to regression test our code for the Bing changes in a test/sandbox environment different from production before the Bing production change on 7/20. Please let us to know the access details(e.g. different URL, keys, etc. if any).

Thanks.

VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-06-25T12:44:06.7833333+00:00
Hello Srijit Lahiri,

It seems you're gearing up for some important changes with the Bing Maps Calculate a Route API and want to ensure a smooth transition by regression testing in a sandbox environment before the official changes on 7/20/2025.

To help you with this, here’s what you need to know:

Microsoft is transitioning routing services by proxying Bing Maps requests to TomTom’s Routing API, while maintaining the existing Bing request/response structure. This ensures backward compatibility for your current integrations.

At this time, there is no separate sandbox or test environment (such as a different endpoint or key) provided. However, you can use your existing Bing Maps API keys to perform regression testing against the production endpoint. This will allow you to validate your application’s behavior under the new routing logic.

Please take care of the below info:

Deprecation Dates:

Basic keys will retire on June 30, 2025

Enterprise keys will retire on June 30, 2028

Proxy Behavior: The Bing API will continue to function, but behind the scenes, requests will be routed through TomTom’s API. This may affect:

Supported travel modes (e.g., transit is not supported)

Waypoint limits (TomTom allows fewer) Traffic optimization parameters

Testing Recommendation: Begin testing now using your current keys to observe any changes in route behavior or response structure.

Ref. Document: official Bing Maps Routes API documentation

Hope this helps!
Thank you!
VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-06-26T10:42:13.5+00:00

Hello Srijit Lahiri,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Please let us know if you need any further assistance.

Thank you!
VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-06-27T05:40:23.8566667+00:00

Hello Srijit Lahiri,

Following up again to see if the above response was helpful in fixing your issue. Please let us know if you need any further assistance.

Thank you!

Srijit Lahiri 20

Hi , We attempted this request through the Insomnia client and recived the following error, please confirm what might be going wrong.

Request:

https://dev.virtualearth.net/REST/V1/Routes/Driving?wp.0=555%2BW%2BImperial%2BHwy%2BBrea%2BCA%2B92821&wp.1=12%2BAtherton%2BIrvine%2BCA%2B92620&key=xxxxxxxx&distanceUnit=mi

Response:

{

"authenticationResultCode": "ValidCredentials",

"brandLogoUri": "https://dev.virtualearth.net/Branding/logo_powered_by.png",

"copyright": "Copyright © 2025 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.",

"errorDetails": [

	"One or more parameters are not valid.",

	"waypoint: This parameter value has an invalid format."

],

"resourceSets": [],

"statusCode": 400,

"statusDescription": "Bad Request",

"traceId": "3a40a4c96218974303cf32790b528128"

}

Manas Mohanty 6,370 Reputation points Microsoft External Staff Moderator

2025-07-01T11:49:50.7766667+00:00

Hi Srijit Lahiri

"errorDetails": [ "One or more parameters are not valid.", "waypoint: This parameter value has an invalid format." ],

Above error suggest to validate format of way points used.

wp.0 and wp.1 should be wp1 and wp0 as special characters are not allowed in variable

Thank you.
Srijit Lahiri 20 Reputation points

2025-07-01T15:55:52.5833333+00:00

Hi @Manas Mohanty

We are receive the same error after modifying the request keys to wp0 and wp1, commenting the API key on the screen capture.

Thanks.

Accepted answer

0 additional answers

Your answer

VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-06-25T12:44:06.7833333+00:00

Hello Srijit Lahiri,

It seems you're gearing up for some important changes with the Bing Maps Calculate a Route API and want to ensure a smooth transition by regression testing in a sandbox environment before the official changes on 7/20/2025.

To help you with this, here’s what you need to know:

Microsoft is transitioning routing services by proxying Bing Maps requests to TomTom’s Routing API, while maintaining the existing Bing request/response structure. This ensures backward compatibility for your current integrations.

At this time, there is no separate sandbox or test environment (such as a different endpoint or key) provided. However, you can use your existing Bing Maps API keys to perform regression testing against the production endpoint. This will allow you to validate your application’s behavior under the new routing logic.

Please take care of the below info:

Deprecation Dates:

Basic keys will retire on June 30, 2025

Enterprise keys will retire on June 30, 2028

Proxy Behavior: The Bing API will continue to function, but behind the scenes, requests will be routed through TomTom’s API. This may affect:

Supported travel modes (e.g., transit is not supported)

Waypoint limits (TomTom allows fewer) Traffic optimization parameters

Testing Recommendation: Begin testing now using your current keys to observe any changes in route behavior or response structure.

Ref. Document: official Bing Maps Routes API documentation

Hope this helps!
Thank you!
VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-06-26T10:42:13.5+00:00

Hello Srijit Lahiri,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Please let us know if you need any further assistance.

Thank you!
VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-06-27T05:40:23.8566667+00:00

Hello Srijit Lahiri,

Following up again to see if the above response was helpful in fixing your issue. Please let us know if you need any further assistance.

Thank you!
Srijit Lahiri 20 Reputation points

2025-06-27T15:09:58.0966667+00:00

Hi , We attempted this request through the Insomnia client and recived the following error, please confirm what might be going wrong.

Request:

https://dev.virtualearth.net/REST/V1/Routes/Driving?wp.0=555%2BW%2BImperial%2BHwy%2BBrea%2BCA%2B92821&wp.1=12%2BAtherton%2BIrvine%2BCA%2B92620&key=xxxxxxxx&distanceUnit=mi

Response:

{

"authenticationResultCode": "ValidCredentials", "brandLogoUri": "https://dev.virtualearth.net/Branding/logo_powered_by.png", "copyright": "Copyright © 2025 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.", "errorDetails": [ "One or more parameters are not valid.", "waypoint: This parameter value has an invalid format." ], "resourceSets": [], "statusCode": 400, "statusDescription": "Bad Request", "traceId": "3a40a4c96218974303cf32790b528128"

}
Manas Mohanty 6,370 Reputation points Microsoft External Staff Moderator

2025-07-01T11:49:50.7766667+00:00

Hi Srijit Lahiri

"errorDetails": [ "One or more parameters are not valid.", "waypoint: This parameter value has an invalid format." ],

Above error suggest to validate format of way points used.

wp.0 and wp.1 should be wp1 and wp0 as special characters are not allowed in variable

Thank you.
Srijit Lahiri 20 Reputation points

2025-07-01T15:55:52.5833333+00:00

Hi @Manas Mohanty

We are receive the same error after modifying the request keys to wp0 and wp1, commenting the API key on the screen capture.

Thanks.

Answer 1

Manas Mohanty 6,370 Microsoft External Staff Moderator

Hi Srijit Lahiri

Appreciate the screenshot. Went through the documentation.

wp.n is supported format for as per this document. https://learn.microsoft.com/en-us/bingmaps/rest-services/routes/calculate-a-route

Was not sure on syntax issue on input used in wp.0, confirmed from screenshot.

You are using plus signs in waypoint inputs.

wp.0=555+Imperial+BH+BBrea+CA+92821

It should be

wp.0=555 Imperial Hwy Brea CA 92821 (spacing and commas allowed does not mention using plus signs)

Could you use it like wp.1 and wp.2 instead of wp.0 and wp.1

Reference used: https://learn.microsoft.com/en-us/bingmaps/rest-services/routes/calculate-a-route#template-parameters

Requesting to accept this answer if it fixes the issue with above pointers.

Thank you for understanding.

Srijit Lahiri 20 Reputation points

2025-07-03T17:59:29.98+00:00

Hi @Manas Mohanty

That worked, thank you for the follow up.

Thanks

Srijit

Share via

Upcoming changes to Bing Maps Calculate a Route API Parameter on 7/20/2025

0 additional answers

Your answer