Bing Maps API
resolution query parameter removal on /REST/v1/Routes/DistanceMatrix
Stopped workingSubscribe to Bing Maps APIShare
On September 30, 2024, the query parameter resolution on the /REST/v1/Routes/DistanceMatrix endpoint stopped working. Calls to /REST/v1/Routes/DistanceMatrix that continue to use this parameter fail. Bing Maps API retired the parameter alongside endTime.
Calls it hits
/REST/v1/Routes/DistanceMatrixquery parameter resolution
What to use instead of these calls
Drop endTime and resolution from your requests. Instead, request one matrix per departure time using startTime.
In Bing Maps API's words
As part of this deprecation we will also retire the paramaters endTime and resolution.
Facts
- API
- Bing Maps API
dev.virtualearth.net - Kind
- Parameter removal
- Announced
- September 30, 2023
- Takes effect
- September 30, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bing Maps API's own pages
Questions
When does this change take effect?
Calls to /REST/v1/Routes/DistanceMatrix, query parameter resolution on Bing Maps API stopped working on September 30, 2024.
What happens to calls after September 30, 2024?
They have failed since September 30, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Bing Maps API 5
-
/REST/v1/Routes/DistanceMatrixParameter removal Stopped working -
/REST/v1/Routes/FromMajorRoadsEndpoint removal Stopped working -
/REST/v1/Routes/LocalInsightsEndpoint removal Stopped working - Bing Maps for Enterprise stops working on Basic (free) account keys Stopped working
- Bing Maps for Enterprise stops working Stops workingin 602 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.