How to avoid getting a 429 error after several calls, eg using SpatialDataService.GeoDataAPIManager.getBoundary?

Jonathan 0

Hi, I'm trying to get several boundaries using the Bingmaps "Microsoft.Maps.SpatialDataService.GeoDataAPIManager.getBoundary" method. Something like 30/40 calls at the start when you get into the web page. I managed to convert those asynchronous calls into synchronous ones to split the number of calls. It works most of the time but sometimes, it raises a 429 GET error even at the first call that only gets boundaries of one country. When the page is right loaded then, I use layers and don't need to make those 30/40 calls again. I'm currently thinking that saving those results would be a possible solution. Is there a way to save those getboundaries results and load them at the start or any other solution?

rbrundritt 15,231 Reputation points Microsoft Employee

2023-03-08T15:36:25.19+00:00

Right error, wrong service. It looks like they are using Bing Maps which has different QPS limits.
QuantumCache 20,031 Reputation points

2023-03-08T16:16:22.8233333+00:00
Hi @Jonathan,

Yes, you are right about the 429 error!

Azure Maps QPS rate limits

When QPS limits are reached, an HTTP 429 error will be returned. If you are using the Gen 2 or Gen 1 S1 pricing tiers, you can create an Azure Maps Technical Support Request in the Azure portal to increase a specific QPS limit if needed. QPS limits for the Gen 1 S0 pricing tier cannot be increased.

"I'm currently thinking that saving those results would be a possible solution."

To reduce the number of requests you make to Azure Maps and help you stay within the rate limit.

If you receive a 429 error, you can retry the request after a certain amount of time has passed, as part of backoff mechanism!!!

You can try batching the requests together.

Upgrade your subscription to increase your rate limit.

I may suggest to try different possible ways!!

In a previous QnA post, we saw few suggestions from the Community Subject Leaders as below,

Customer may not cache or store information delivered by the Azure Maps API including but not limited to geocodes and reverse geocodes, map data tiles and route information (the “Results”) for the purpose of scaling such Results to serve multiple users, or to circumvent any functionality in Azure Maps.

Caching and storing Results is permitted where the purpose of caching is to reduce latency times of Customer’s application. Results may not be stored for longer than: (i) the validity period indicated in returned headers; or (ii) 6 months, whichever is the shorter. Notwithstanding the foregoing, Customer may retain continual access to geocodes as long as Customer maintains an active Azure account. Reference

If this answers your query, do click Accept Answer and Yes for this answer as helpful. And, if you have any further query do let us know by commenting in the below section.
QuantumCache 20,031 Reputation points

2023-03-08T16:18:04.4033333+00:00

Hi @Jonathan, Can you please confirm on the service being used,

rbrundritt is right about the service and the below rate limits.
rbrundritt 15,231 Reputation points Microsoft Employee

2023-03-08T16:34:08.56+00:00

They mentioned in their post Microsoft.Maps.SpatialDataService.GeoDataAPIManager.getBoundary which is exposed by Bing Maps in Bing Maps V8 SDK through the Spatial Data Services module: https://learn.microsoft.com/en-us/bingmaps/v8-web-control/modules/spatial-data-service-module/geodataapimanager-class This module is a JavaScript client library that wraps this service: https://learn.microsoft.com/en-us/bingmaps/spatial-data-services/geodata-api Note that Bing Maps is managed by the Azure Maps team, thus why Bing Maps questions appear under the "Azure-Maps" tag.

1 answer

rbrundritt 15,231 Reputation points Microsoft Employee

2023-03-08T15:40:28.26+00:00

A 429 error is related to rate limiting/throttling (queries per second/QPS). It looks like you are using Bing maps, not Azure Maps so the limits work a bit differently. In Bing Maps, all non-production keys are throttled at around 5 QPS, and the default for production keys is around 50 QPS. If using a production key (e.g. are paying for the service) you can contact the Bing Maps Enterprise Support team (https://www.microsoft.com/en-us/maps/support) and request the limit be raised on your account.
Please sign in to rate this answer.

2 people found this answer helpful.
IoTGirl 2,976 Reputation points Microsoft Employee

2023-03-10T21:10:19.4133333+00:00

I have given the same answer many times. "429" is telling you to dial back on your calls, It is not unique to maps, any REST service can provide you the same. Both Satish & Ricky have given the correct answer but because it is so in the news right now, I thought I would ask #newbing... Bing's response is follows:

The HTTP 429 - Too Many Requests response status code indicates that the user has sent too many requests in a given amount of time (rate limit) to a given endpoint (API or web service)<sup>1</sup>. When you receive this error, normally a Retry-After header might be included to this response indicating how long to wait before making a new request<sup>1 2</sup>.

You can implement retry logic by checking for the presence of this header and waiting for the specified time before making a new request. If this header is not present, you can implement an exponential backoff strategy where you increase the wait time between retries until you stop receiving 429 responses.

Is there anything else I can help with?

Received message. The HTTP 429 - Too Many Requests response status code indicates that the user has sent too many requests in a given amount of time (rate limit) to a given endpoint (API or web service). When you receive this error, normally a Retry-After header might be included to this response indicating how long to wait before making a new request . You can implement retry logic by checking for the presence of this header and waiting for the specified time before making a new request. If this header is not present, you can implement an exponential backoff strategy where you increase the wait time between retries until you stop receiving 429 responses. Is there anything else I can help with?

Learn more:

demiliani.com**[2. developer.mozilla.org](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429"429 Too Many Requests - HTTP | MDN - Mozilla")[3. bing.com](https://bing.com/search?q=retry+logic+HTTP+REST+request+429+response"Handling the “HTTP 429 – Too Many Requests” error when calling external ...")[4. developer.mozilla.org](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After"Retry-After - HTTP | MDN - Mozilla")[5. learn.microsoft.com](https://learn.microsoft.com/en-us/azure/logic-apps/handle-throttling-problems-429-errors"Handle throttling problems, or '429 - Too many requests' errors - Azure ...")**
Sign in to comment