Authentication & Security
Authenticate API requests using Bearer tokens, configure key scopes, and understand rate limits.
All requests to the YouTube Transcript Platform API must be authenticated using a valid API key.
Bearer Token Authentication
Include your API key as a Bearer token in the Authorization header:
Authorization: Bearer YOUR_API_KEYKeep your API key secret
Never expose your API key in client-side code, public repositories, or browser network requests. Use environment variables and server-side proxying.
Requests without a valid Authorization header receive a 401 Unauthorized response:
{
"error": "Unauthorized: invalid or missing API key",
"status": 401
}API Key Scopes
Keys can be generated with specific scopes from the Developer Dashboard:
| Scope | Description |
|---|---|
transcripts:read | Extract transcripts in all formats, word-level offsets, and AI Markdown. |
transcripts:stream | Stream real-time transcript chunks via SSE / WebSocket. |
admin | Full programmatic access and team management. |
Rate Limits & Concurrency
API keys have default rate limits based on your account tier:
| Account | Rate Limit | Burst |
|---|---|---|
| Free | 30 RPM (0.5 req/s) | 2 |
| Paid (any pack) | 300 RPM (5 req/s) | 10 |
| Reserved | Above 300 RPM | Dedicated door set |
Rate limit exceeded?
When you exceed your rate limit, the API returns 429 Too Many Requests with a Retry-After header indicating seconds until reset. See Credits & Errors for all error codes.