Updated November 24 2023: To ensure reliable service availability for all users, the current API limit is 1 request per second. Unfortunately, some users are attempting to circumvent rate limits by querying from multiple IP addresses and subnets. In cases where we identify this type of abuse, we may block entire ISPs from accessing this service. Please do not abuse this free service and ruin it for everyone else!
If you need high volume geocoding... Please contact us for pricing details.
If your application exceeds the request limit, requests will be rejected with an HTTP 429 response. Upon receiving an HTTP 429 response, please throttle your application's rate of requests, e.g., by implementing a 1-second pause after each request.
Since HTTP 429 responses will not contain any geocoding results, such queries will need to be performed again after a delay.
During periods of extremely high traffic loads the server may refuse to process your request and instead respond with an HTTP 503. In addition to the HTTP 503, the server may issue a "Retry-After" header indicating the number of seconds to wait before attempting the API query again.
We reserve the right to block clients deemed to be abusing the service, e.g., clients making excessive repeated/duplicate requests (please cache API results), ignoring HTTP response codes that indicate your client should moderate request rates, flooding the API service with requests that consume too many server resources, etc. Blocked clients will receive an HTTP 403 response. If your client receives an HTTP 403, please contact us at the email address above so that we can work with you to resolve the issue.
These limits are subject to change without notice to ensure the stability of our systems. This section will be updated when we change the API limits.