Quotas and limits  |  API Keys API Documentation  |  Google Cloud (2024)

FAQs

What is the quota limit for Google Cloud API? ›

The API limits the number of requests for your Google Cloud project. The default value set in the Google Cloud console is 2,400 queries per minute per user per Google Cloud project.

50,000 requests per project per day, which can be increased. 10 queries per second (QPS) per IP address. In the API Console, there is a similar quota referred to as Requests per 100 seconds per user. By default, it is set to 100 requests per 100 seconds per user and can be adjusted to a maximum value of 1,000.

120 API calls per minute. To request an increase to these quotas: In the Google Cloud console, go to the IAM & admin > Quotas page. Select the API Keys API quota that you want to increase: Read requests per minute and/or Write requests per minute.

Quotas are defined by a Google Cloud service to specify the amount of a countable, shared resource that you can use. System limits are fixed values that cannot be changed. Google Cloud provides tools so that you can monitor your usage of these resources, create alerts, and request adjustments.

Please navigate to the Cloud Console and select the resources you want to modify. Then click Edit Quotas at the top of the page to start the Quota Increase process.

You can use the same API key for multiple websites or generate a new one for each site. You can generate up to 500 unique API keys. Using a different API key for each site allows you to disable it if you no longer use it on an active website or have stopped supporting the project.

API key restrictions ensure that only your apps and websites can use your keys. For security reasons, we recommend that you add restrictions that specify: Which clients or websites can use your API keys. The Google Cloud APIs that your application can call using your API keys.

Where is the best place to store API keys? ›

Keep API keys isolated from the main code and away from the public eye by storing them in environmental variables. Always keep API keys in safe key management solutions for storage. Make sure that the keys are encrypted both in transit and at rest. Alternate your API keys regularly to minimize exposure concerns.

To view detailed quota information for a particular API, including usage over time, visit the quota page for the API in the Google Cloud console. Depending on the API, these limits can include requests per day, requests per minute, and requests per minute per user.

The API limits the number of requests for your APIs Console project. The API project's maximum number of requests per second (project QPS) is 1000. And, the maximum number of requests per user per second (user QPS) is 150. If these limits are exceeded, the server returns an HTTP 503 status code.

The default limits are 500 requests per 100 seconds per project, and 100 requests per 100 seconds per user. Because this add-on's requests are all performed by a single user, the 100 requests per 100 seconds per user limit is more often the problem.

API Gateway enforces the following limits on APIs, API configs, and gateways: APIs - 50 total. API Configs - 100 per API. Gateways - 5 per region.

Using the Directory API, you can perform up to: 20 action requests per second. 20 delete requests per second. 10 get requests per second.

The Google Places API has the following query limits:

Users with an API key are allowed 1 000 requests per 24 hour period. Users who have also verified their identity through the APIs console are allowed 100 000 requests per 24 hour period. A credit card is required for verification, by enabling billing in the console.