Quotas

AI-generated Key Takeaways

• Quotas in the AdMob API protect Google's infrastructure and ensure community stability.

• Quota limits are applied separately to account, inventory, and reporting methods.

• Back-end processing cost caps exist, and addressing errors like 429 RESOURCE_EXHAUSTED may require client-side rate limiting and reducing requested rows.

• Specific quota limits are listed for different read requests per minute and per day per project.

• Additional daily quota can be requested through the AdMob API Developer Forum with a use case description.

Quotas protect Google's infrastructure from processes that use the AdMob API in an inappropriate way. They ensure that individual actions cannot negatively impact the larger community.

Quota limits

The following table outlines each quota limit for the AdMob API. Note that quota limits apply to account, inventory, and reporting methods separately.

Key Point: There are additional back-end processing cost caps. When experiencing quota errors, such as 429 RESOURCE_EXHAUSTED, and your quotas are within the table below, the recommendation is to introduce client-side rate limiting as well as requesting fewer rows per request. The latter can be achieved by reducing the date range of your request and the number of dimensions.

Quota Description	Quota Limit
Account read requests per minute per project	900
Inventory read requests per minute per project	120
Inventory read requests per day per project	172800
Reporting read requests per minute per project	900

Follow the instructions for additional information on your quota limits.

Requests for additional daily quota

If you require more quota than the limit, reach out to us on the AdMob API Developer Forum and describe your use case.