As the Google Drive API is a shared service, we apply quotas and limitations to make sure it's used fairly by all users and to protect the overall performance of the Google Workspace system.
If you exceed a quota, you'll receive a
403: User rate limit exceeded
HTTP status code response. Additional rate limit checks on the Drive backend might also generate a
429: Too many requests response. If this happens, you should use an
exponential backoff algorithm and try again
later. Provided you stay within the per-minute quotas below, there's no
limit to the number of requests you can make per day.
The following table details the query limits:
Resolve time-based quota errors
For all time-based errors (maximum of N requests per X minutes), we recommend your code catches the exception and, using an exponential backoff algorithm, implement a small delay before trying again. If requests are still unsuccessful, it's important the delays between requests increase over time until the request is successful. Generally, you should use a truncated exponential backoff. To learn how to use exponential backoff, go to Retry strategy.
All use of the Drive API is available at no additional cost. Exceeding the quota request limits doesn't incur extra charges and your account is not billed.
Request a quota increase
Depending on your project's resource usage, you might want to request a quota increase. API calls by a service account are considered to be utilizing a single account, so you might need a higher per-user, per-project quota in that scenario. Applying for an increased quota doesn't guarantee approval. Large quota increases can take longer to be approved.
To learn more, see the resources below: