LocalInsights endpoint removal

Stopped workingSeptember 30, 2024Subscribe to Bing Maps APIShare

On September 30, 2024, the GET /REST/v1/Routes/LocalInsights endpoint was retired. Calls to /REST/v1/Routes/LocalInsights fail after that date. The retired endpoint previously allowed users to retrieve local entities within a specified driving time or distance from a given point.

Calls it hits

/REST/v1/Routes/LocalInsights

What to use instead of these calls

Because the API has no direct replacement, you must choose an alternative approach. Combine an isochrone via GET /REST/v1/Routes/Isochrones with a Local Search query, or move to Azure Maps Search.

The API has no direct replacement.

In Bing Maps API's words

API which allows you to get a list of local entities within the specified maximum driving time or distance traveled from a specified point will be retired on September 30, 2024.

Bing Maps API, Announcement

Facts

API: Bing Maps API dev.virtualearth.net
Kind: Endpoint removal
Announced: September 30, 2023
Takes effect: September 30, 2024
Calls after that day: Fail
Source: Announcement
Last updated: October 25, 2026
Verified: November 6, 2026, against Bing Maps API's own pages

Questions

When does this change take effect?

Calls to /REST/v1/Routes/LocalInsights 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.

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub