Google Places API

Requesting more quota

It is important to Google that developers building great apps using the Places API have access to as much capacity as they need to be successful. However we must also ensure that aggressive use of the service by some developers does not unfairly limit access by others, and that the service is used as intended. To balance these requirements we’ve put in place a daily limit of 100 000 requests per day, and a simple review process for developers that need more.

If you are concerned that your application may use more than 100 000 requests per day, or you are receiving quota exceeded errors from your app, please proceed as follows.

  1. Make sure you are using the right service for your application.
  2. Receive a complimentary quota increase by validating your identity.
  3. Ensure that your application complies with the API Terms of Service.
  4. Help us improve our Places data where possible.
  5. Complete a form requesting additional quota.

Choose the right service for your application

If you are developing a web based application that only needs to search for places, and is not submitting new places or Place Bumps, you should use the Places library of the Maps API rather than using the Places API web service. The Places library assigns a quota to each end user rather than to each key. This means that your available quota increases with your user base rather than being capped at a fixed amount.

Receive a complimentary quota increase by validating your identity

You can increase your available quota to 100 000 requests per day by validating your identity. To validate your identity you must first enabling billing on your Places API project. You will be asked to enter your credit card details, but you will not be charged when you enable billing, or when using the API. We ask for your credit card purely to validate your identity. Once your identity has been validated your quota will be increased to 100 000 requests per day at no charge.

Ensure that your application complies with the API Terms of Service

We recommend that you familiarize yourself with the Google Maps/Google Earth API Terms of Service and the Developer Policies, and ensure that your app complies with them. Some key requirements we will check for include:

  • Make sure your application shows the “Powered by Google logo” above or below Places API search and details results if they are displayed on a screen without a corresponding Google map.
  • Make sure your application shows any data provider attributions returned with search results. Note that attributions are not required in all countries so this can be easy to miss. Try searches in the U.K., Canada, or Australia for examples of countries where attribution is required.
  • Your application should trigger a call to the Places API whenever it needs to execute a place search in response to user activity. If you need offline access to places data, or to pre-cache places data, you must first obtain permission from Google.
  • Your application must be available to the general public for download, use, or purchase. If you wish to use the Places API in an app that is only offered to a limited audience (eg. an intranet application) you will need a Maps API for Business license.
  • Make sure you regularly refresh any places data that you cache on your server or in your app. Store a timestamp with your cached data, and update your cached copy whenever you access that copy more than 30 days since it was last updated.
  • Make sure that any maps used by your application to show the location of places retrieved from the Places API are Google Maps
  • Make sure your application has a published Privacy Policy which:
    • describes your use and retention of privacy sensitive information such as user names and user location
    • notifies users that you are using the Google Maps API and incorporates by reference the Google privacy policy by including a link to

Help us improve our Places data

A great way to ensure that we are excited about your application is to use the Places API in a way that helps us to improve our Places data. For example:

  • If your application allows users to add new Places that they find are missing from results, make sure you submit those new Places to the Places API Report service. This allows us to add the Place to our place database so that everybody can benefit.
  • If your application allows users to identify the Place where they are currently located in order to attach that location to a photo or update, please use the Places API Bump service to let us know. You do not need to provide the identity of the user to do this. By knowing the number of users who have Bumped a Place over time we can improve our ranking of Places both for your app, and across all Google products.

Complete a form requesting additional quota

Once you have completed the above steps you are ready to request more quota. To do so, fill in the Quota Uplift Form (requires a Google login).

One of our Places API support staff will contact you once we receive your review request. They may request additional information, or confirm that your request has been approved. Once approved you will see your available quota increase in the Places API Console.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.