API Access Notice

API Resources

Note: The Google Search and Language APIs shown to the right have been officially deprecated. They will continue to work as per our deprecation policy, but the number of requests you may make per day will be limited. Please visit the documentation for each API for further details and alternatives.

Note: The Google Local Search API is no longer available. Please migrate to the Google Places API.

You received this notice because Google has blocked or throttled this website's access to the Google API.

  • If you are a user of this website, please forward the URL of this error document (http://developers.google.com/errors/) to the site administrator.
  • If you are a developer, please keep reading to diagnose the problem and reinstate the API.

We blocked your website from using the API due to one of the reasons cited below. To reinstate your account, you need to take action so your site complies with the Terms of Use.

How to reinstate the API

  1. Please review the Terms of Use for the API(s) you are using (linked in the right sidebar) and ensure compliance. It is likely that we blocked you for one of the following Terms of Use violations:
    • We received automated requests, such as scraping and prefetching. Automated requests are prohibited; all requests must be made as a result of an end-user action.
    • Your website charges users. All websites or apps which use Google APIs must be free of charge.
    • Your website caches or stores results. Caching or storing results is allowed in some APIs. Please review the Terms of Use for the API(s) you are using for specific caching policies.
    • Your website does not supply a proper attribution. The Terms of Use require all users to supply the proper attribution with all search results.
    • Your website uses the RESTful interface, but does not include a valid HTTP referer. The API requires a valid referer.
  2. Once you've made sure that you're complying with the Terms of Use, here are some additional steps you can take that will help solve some common problems:
    • Make sure that you're not sending any requests with a blank query. This is a common programming error, and often results in developers sending many more requests than they mean to (sometimes in an infinite loop!), which can also cause their traffic to appear abusive without providing any value to you (since we can't return results for a blank query anyway).
    • If you're using the RESTful interface, consider using the optional userip parameter. This parameter supplies the IP address of the end-user who made the request and validates that you are not making automated requests in violation of the Terms of Use.
    • Sometimes, requests made on behalf of search engine crawlers, as they visit your pages, can result in blocks. To bring your site in line with the Terms (which prohibit automated queries), please utilize a robots.txt or otherwise prevent crawlers' requests from triggering API requests.

In most cases, confirming compliance with the Terms of Use and performing the above steps will result in an automatic unblock within a short period of time.