X-RateLimit-Limit
Maximum requests allowed in the current short-window interval.
YouTube Transcript API Rate Limits and Quotas
Understand the difference between short-window rate limits, monthly product quota and the response headers returned by the Scority API.
Two controls
Rate limits are not monthly quota
Scority uses short-window rate limits to protect API reliability and monthly quotas to control product usage for each API key.
- rate_limited means your integration sent too many requests in a short time window.
- quota_exceeded means the API key reached its configured monthly quota.
- Both return HTTP 429, but they require different actions.
- Rate-limit 429 responses include rate-limit headers and usually Retry-After.
X-RateLimit-Remaining
Requests left in the current short-window interval.
X-RateLimit-Reset
Unix timestamp or reset moment for the current rate-limit window.
Retry-After
Seconds to wait before retrying after a 429 response.
Integration guidance
How to reduce 429s
- Cache transcript responses on your side when your workflow repeatedly asks for the same video.
- Queue bulk jobs instead of sending large bursts at once.
- Retry only after the Retry-After interval when it is present.
- Separate customer or environment traffic with separate API keys when usage needs independent quotas.
- Contact Scority before planned high-volume runs so quota and rate-limit expectations are clear.
Guides
Plan quota and cost
The guide pages explain how rate limits and monthly quota affect pricing, retries and product design.
Guide
Quota and rate limits
Understand quota_exceeded, rate_limited and rate-limit headers.
Open →Quota
Quota exceeded
Separate monthly quota exhaustion from short-window throttling.
Open →429
429 troubleshooting
Debug rate_limited, quota_exceeded and retry behavior in production integrations.
Open →Guide
Pricing and cost factors
Estimate transcript API usage without inventing exact vendor costs.
Open →