Live
Transcript API
Fetch transcript text and timestamped segments from public YouTube videos through the API.
Open →YouTube Transcript API Documentation
Developer documentation for the Scority YouTube Transcript API: authentication, errors, quotas, language options and JSON responses.
Auth
Authentication
Use the x-api-key header. API keys are provided by the Scority team and must stay server-side.
Open →Reference
Errors
Normalized JSON errors for invalid input, quota, rate limits, missing captions, and upstream failures.
Open →Quotas
Rate limits and quotas
Requests are rate limited and counted toward the quota configured for your API key.
Open →Languages
Language options
Understand language and lang, response language fields, language-aware cache buckets and related errors.
Open →OpenAPI
OpenAPI specification
Import the machine-readable API contract into Postman, Insomnia, Scalar or a codegen workflow.
Open →Examples
SDK examples
Server-side Node and Python examples for calling the HTTP API today.
Open →Workflows
Integrations
Use the HTTP API and OpenAPI contract in MCP-style tools, custom GPT actions and internal automations.
Open →Transcript availability
Scority first uses accessible caption tracks. For harder videos, supported accounts can use server-side fallback processing. When a transcript still cannot be retrieved, the API returns normalized errors so your client can skip the video, retry later, or route it to another workflow.
- Use API keys only from trusted server-side code.
- Fallback infrastructure can include proxy/captcha routing and GPU-capable processing capacity.
- Handle transcript_not_available and upstream_transcript_failed as expected production outcomes.
- Use the OpenAPI spec to keep generated clients aligned with the current endpoint.
- The public web route at /api/transcript stays disabled; production requests use api.scority.ai.