Limits and quotas on API requests

  • Google Analytics APIs enforce limits and quotas to manage system resources and ensure equitable distribution among users.

  • Usage limits include 50,000 requests per project per day and 10 queries per second per IP address.

  • Specific APIs may have additional restrictions, detailed on separate pages.

  • Exceeding quotas results in an API error code 403 or 429 with a message indicating the quota has been exceeded.

To ensure the Google Analytics system doesn't receive more data than it can handle, and to ensure equitable distribution of the system's resources across users, Google Analytics APIs enfore some limits and quotas on your usage.

The following limits and quotas apply to your overall Google Analytics API usage (excluding Data API calls) at the Google Cloud project level:

  • 50,000 requests per project per day.
  • 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. But the number of requests to the API is restricted to a maximum of 10 requests per second per user.
    • If your application makes all API requests from a single IP address (for example, on behalf of your users), use the userIP or quotaUser parameter with each request to get full QPS quota for each user. See The standard query parameters summary for details.

Some APIs have additional restrictions. For details on API-specific limits and quotas, see the following pages:

Errors related to limits and quotas

If the quota of requesting a Google Analytics API is exceeded, the API returns an error code 403 or 429 and a message that the account has exceeded the quota. See the terms of service for more information.

For more information on quota management and how to fine-tune your application for quota usage, see Monitoring APIs and capping usage.