API reference
See language parameters, response fields and current endpoint behavior.
Open →Understand YouTube captions, subtitles and transcript access. Learn how Scority returns caption text and timestamped transcript segments.
For many YouTube transcript workflows, the useful data comes from caption or subtitle tracks. A transcript API turns those tracks into normalized text and timestamped segments that server-side apps can use.
The terms overlap in everyday use, but they matter when you build an API integration.
The official YouTube APIs are the right starting point for many platform workflows, but transcript access is a narrower problem. Before publishing exact claims about official caption APIs, check current Google documentation and record the access date.
Scority works with many public YouTube videos that have accessible captions. The current API does not guarantee transcripts for every public video.
Send language or lang to request a caption language. Do not send both. The response language reflects the selected caption track when available.
Segments let AI and search workflows connect text back to time ranges in the video.
This request asks for the English caption track and returns text, segments, source and language when a transcript is available.
curl "https://api.scority.ai/v1/youtube/transcript?video_id=dQw4w9WgXcQ&language=en" \
-H "x-api-key: YOUR_API_KEY"Caption-derived transcripts are useful when an AI workflow needs source text from video without storing or processing the media file.
See language parameters, response fields and current endpoint behavior.
Open →Understand transcript_not_available, upstream_transcript_failed and language errors.
Open →Compare transcript-specific API access with broader YouTube API intent.
Open →