Reputation: 111
When using the geocoding API (server-side), the error Geocoding Service: You have exceeded your rate-limit for this API
is returned in 100% of the cases since the start of this month/year. The data is entered manually by a very small group of users, so the rate of requests per second can not actually be exceeded. Nevertheless, all requests fail, according to the Google dashboard with status 403: "OVER_QUERY_LIMIT"
.
https://maps.googleapis.com/maps/api/geocode/json?address=ADDRESS&key=KEY
, so it's not an SSL issue and the key is includedI've seen people suggest the Geocoding API is just buggy and other services would be preferable, or recommend a switch from server-side to client-side. The API call is made from a third party PHP module, so switching to another service or client-side geocoding would mean rebuilding the functionality from scratch. I'd like to avoid that, especially as we're nowhere near the actual quota. Does anyone have an idea what's going wrong?
Upvotes: 4
Views: 2105
Reputation: 111
The quotas "requests per 100 seconds" and "requests per user per 100 seconds" were too low. Despite them never being reached, the API did not function correctly with the limits set to 50/20. I set both limits to 100, now it works.
Upvotes: 5