It is important to Google that developers building great apps using the Google Places API Web Service 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 150 000 requests per day, and a simple review process for developers that need more.
Optimising your usage of the Google Places API Web Service service
If you are concerned that your application requires more than 150 000 requests per day, or you are receiving quota exceeded errors from your app, please follow these steps:
- Make sure you are using the right service for your application.
- Receive a complimentary quota increase by validating your identity.
Choose the right service for your application
Receive a complimentary quota increase by validating your identity
You can increase your available quota to 150 000 requests per day by validating your identity. To validate your identity you must first enable billing on your Google Places API Web Service 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 150 000 requests per day at no charge.
Requesting additional quota
If you wish to ask for more than 150 000 requests per day, please follow these steps:
- Ensure that your application complies with the API Terms of Service.
- Help us improve our places data.
- Complete a form requesting additional quota.
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 Google Places API Web Service 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 must be available to the general public for download, use, or purchase. If you wish to use the Google Places API Web Service in an app that is only offered to a limited audience (eg. an intranet application) you will need a Google Maps API for Work license.
- Your application should trigger a call to the Google Places API Web Service 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.
- 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.
- Note that the place ID, used to uniquely identify a place, is exempt
from the caching restriction. You can therefore store place ID values
indefinitely. The place ID is returned in the
place_idfield in Google Places API Web Service responses.
- Make sure that any maps used by your application to show the location of places retrieved from the Google Places API Web Service are Google Maps
- describes your use and retention of privacy sensitive information such as user names and user location
Help us improve our places data
A great way to ensure that we are excited about your application is to use the Google Places API Web Servicein a manner that helps us to improve our places data. More specifically, we look for applications that allow users to add new places that they find are missing from results and that send those added places to Google via the Add Places service. This allows us to add the place to our places database so that everybody can benefit.
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 Google Places API Web Service 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 Google Developers Console.