Rate limits

Current throttling headers and video quota behavior

By YT2Text Team • Published February 1, 2025 • Updated March 22, 2026

Rate Limits

YT2Text uses two different controls:

request throttling per API key
plan-based video quotas

Request Throttling

API-key throttling is enforced with Redis-backed sliding-window logic when Redis is available.

Default key creation rate limit:

```
100
```
requests/hour

429 responses include:

```
X-RateLimit-Limit
```
```
X-RateLimit-Used
```
```
X-RateLimit-Remaining
```
```
X-RateLimit-Reset
```
```
Retry-After
```

Implementation notes:

```
X-RateLimit-Reset
```
is currently seconds until reset, not a Unix timestamp
rate-limit headers are only attached on API-key-authenticated requests
if Redis is unavailable, the current backend falls back to allowing requests through

Video Quotas

These quotas are enforced by plan logic during processing requests.

Plan	Daily videos	Monthly videos
free	5	5
plus	40	200
pro	100	1000

API keys: Plus and above
webhooks: Pro and above
custom prompts: Pro and above
batch: Pro and above
infographics: Pro and above
AI chat: Pro and above
PDF export: Pro and above

Practical Advice

Back off on 429 responses using
```
Retry-After
```
.
Track both request throttling and video quotas in your integration.
Do not use the
```
/api/v1/usage/*
```
responses as quota truth today; those endpoints currently return placeholder/mock analytics payloads.