Docs
Rate limits and quotas
Understand response headers and 429 behavior.
Open →YouTube API Quota Exceeded Guide
Troubleshoot quota exceeded errors, distinguish Google quota from Scority quota_exceeded, and plan safe retries and caching.
Direct answer
Quota exceeded means usage crossed a configured limit
Quota wording appears in both official YouTube API workflows and transcript API products. The fix depends on which system returned the error.
- For Google's official APIs, check the current Google Cloud quota and project settings.
- For Scority, quota_exceeded means the API key reached its configured monthly product quota.
- quota_exceeded is different from rate_limited, even though both use HTTP 429 in Scority.
- Do not retry quota_exceeded in a tight loop; it usually needs quota planning or a usage change.
Scority
Scority quota_exceeded vs rate_limited
Scority uses monthly quota for product usage and short-window rate limits for burst protection.
- quota_exceeded: monthly quota has been reached for the key.
- rate_limited: too many requests were sent in a short window.
- Retry-After is useful for rate_limited responses.
- Monthly quota issues should be handled through usage review or support.
Reduce pressure
How to avoid unnecessary quota use
A transcript workflow can often reduce repeated requests without weakening the product experience.
- Cache transcript results in your own application when the same video is requested repeatedly.
- Deduplicate jobs before calling the API.
- Avoid retrying transcript_not_available as if it were a transient outage.
- Queue bulk work instead of running bursts from multiple workers at once.
- Track cache hits, misses, 429s and upstream failures separately.
Debug checklist
What to check before asking for more quota
- Are repeated requests hitting the same video_id or video_url?
- Are failed jobs retrying immediately instead of backing off?
- Are users triggering duplicate transcript jobs from the UI?
- Are you separating test, staging and production keys?
- Do logs show quota_exceeded, rate_limited or an upstream transcript error?