Quotas protect Google's infrastructure from automated processes that use the Google Bid Manager API in an inappropriate way. They ensure that one developer's actions cannot negatively impact the larger community.

## Quota limits

The following default quota limits are shared by all Bid Manager API resources and methods.

- 2,000 requests per project per day - [can be increased](https://developers.google.com/bid-manager/quotas#additional_quota).
- 4 queries per second (QPS) per project.
  - In the Google API Console this quota is referred to as **Queries per minute per user**, and is set to 240.

> [!NOTE]
> **Note:** Daily quotas refresh at midnight PST.

## Exceeding quota limits

In the unlikely event that your request fails due to exceeding a quota limit, the API returns an HTTP status code and reason for the error. Additionally, the body of the response contains a detailed description of what caused the error. See the [Error Messages](https://developers.google.com/bid-manager/guides/general/errors) guide for an example error response.

The following list shows the possible errors and recommended actions for request failures caused by exceeding quota limits.

| Code | Reason | Message | Recommended Action |
|---|---|---|---|
| 403 | dailyLimitExceeded | Daily Limit Exceeded | Do not retry without fixing the problem. [Examine your usage](https://console.developers.google.com/project/_/apiui/apiview/doubleclickbidmanager/metrics) from the Google API Console and modify your workflow to make fewer requests. You can [request additional quota](https://developers.google.com/bid-manager/quotas#additional_quota) if you believe your usage is reasonable. |
| 403 | userRateLimitExceeded | User Rate Limit Exceeded | Slow down the rate at which you are sending requests using [exponential backoff](https://developers.google.com/bid-manager/quotas#exponential_backoff). |

#### What is exponential backoff?

Exponential backoff is a standard error handling strategy for network applications in which the client periodically retries a failed request over an increasing amount of time. If a high volume of requests or heavy network traffic causes the server to return errors, exponential backoff may be a good strategy for handling those errors. Conversely, it is not a relevant strategy for dealing with errors unrelated to network volume or response times, such as invalid authorization credentials or file not found errors.

Used properly, exponential backoff increases the efficiency of bandwidth usage, reduces the number of requests required to get a successful response, and maximizes the throughput of requests in concurrent environments.

The flow for implementing simple exponential backoff is as follows:

1. Make a request to the API.
2. Receive an `HTTP 503` response, which indicates you should retry the request.
3. Wait 1 second + random_number_milliseconds and retry the request.
4. Receive an `HTTP 503` response, which indicates you should retry the request.
5. Wait 2 seconds + random_number_milliseconds, and retry the request.
6. Receive an `HTTP 503` response, which indicates you should retry the request.
7. Wait 4 seconds + random_number_milliseconds, and retry the request.
8. Receive an `HTTP 503` response, which indicates you should retry the request.
9. Wait 8 seconds + random_number_milliseconds, and retry the request.
10. Receive an `HTTP 503` response, which indicates you should retry the request.
11. Wait 16 seconds + random_number_milliseconds, and retry the request.
12. Stop. Report or log an error.

In the above flow, random_number_milliseconds is a random number of milliseconds less than or equal to 1000. This is necessary, since introducing a small random delay helps distribute the load more evenly and avoid the possibility of stampeding the server. The value of random_number_milliseconds must be redefined after each wait.

**Note:**The wait is always (2 \^ n) + random_number_milliseconds, where n is a monotonically increasing integer initially defined as 0. The integer n is incremented by 1 for each iteration (each request).

The algorithm is set to terminate when n is 5. This ceiling prevents clients from retrying infinitely, and results in a total delay of around 32 seconds before a request is deemed "an unrecoverable error." A larger maximum number of retries is fine, especially if a long upload is in progress; just be sure to cap the retry delay at something reasonable, say, less than one minute.

## Requesting additional daily quota

If you think that your application requires additional daily quota, you can request more by following the instructions below.

The following instructions only apply to projects that have encountered a `dailyLimitExceeded` error. Recommended actions for other quota errors are covered in the [table above](https://developers.google.com/bid-manager/quotas#exceeding_limits).

1. Navigate to the [Bid Manager API](https://console.developers.google.com/project/_/apiui/apiview/doubleclickbidmanager/quotas) in the Google API Console.
2. Review your usage statistics from the **Metrics** page to ensure your application is behaving as expected. Pay close attention to the methods that have been called and address any unexpected or excessive usage before proceeding.
3. If usage looks normal, navigate to the **Quotas** page, click the edit icon next to **Queries per day** and click the link to "Apply for higher quota".

Make sure to review the information and follow the instructions included in the quota request form before submitting an increase request.

> [!NOTE]
> **Note:** The email address you provide must be one that you actively monitor, as a representative may reach out to gather additional information.