YouTube API

YouTube Video transcript full API

Fetch a YouTube video or Short transcript with timed segments and its provenance: whether the words are creator-written captions or machine speech recognition.

POST/v1/run/youtube.video_transcript_full
Uptime
97.95%
30d · 146 calls
Requests
146
30d · weekly, last 12 wks
Response
17.5s
median · 30d

Try it

Make your first request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `isAiGenerated`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a transcript that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "data": {
    "channel": "example",
    "durationSeconds": 12.5,
    "isAiGenerated": true,
    "isAutoGenerated": true,
    "language": "en",
    "segments": [
      {
        "endSeconds": 180,
        "startSeconds": 180,
        "text": "A short example description of this item."
      }
    ],
    "title": "Example title",
    "transcript": "example"
  },
  "found": true
}
Response interface
interface YoutubeVideoTranscriptFullResponse {
  data: {
    channel?: string;
    durationSeconds?: number;
    isAiGenerated?: boolean | null;
    isAutoGenerated: boolean;
    language: string;
    segments?: {
      endSeconds: number;
      startSeconds: number;
      text: string;
    }[];
    title?: string;
    transcript: string;
  } | null;
  found: boolean;
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

Request, response, and price

Last verified 2026-09-16 · uptime and latency measured over 30d
POST /v1/run/youtube.video_transcript_full
curl -X POST https://api.getanyapi.com/v1/run/youtube.video_transcript_full \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.youtube.com/watch?v=dQw4w9WgXcQ"}'
FieldTypeExample value
Request body
urlstring"https://www.youtube.com/watch?v=dQw4w9WgXcQ"YouTube video or Short URL (e.g. "https://www.youtube.com/watch?v=dQw4w9WgXcQ" or "https://www.youtube.com/shorts/Fir1x9cw2vg").
captionKindenumWhich caption track to accept: "manual" only creator-written captions, "automatic" only YouTube's speech recognition, "any" whichever exists.
languagestringPreferred caption language code (e.g. "en", "es"). Defaults to English.
requireFieldsarrayOptional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `isAiGenerated`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a transcript that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Response
dataobject
data.channelcan requirestringChannel name that published the video.
data.durationSecondscan requirenumberVideo duration in seconds.
data.isAiGeneratedcan requirebooleanTrue when the words were recognized from the audio by the serving lane rather than read from any YouTube caption track, or null when the serving source does not say.
data.isAutoGeneratedbooleanTrue when YouTube generated the caption track by speech recognition rather than the creator supplying it. Automatic captions carry recognition errors, especially on names and jargon. Populated whenever the provider has data for the entity.
data.languagestringCaption language code (e.g. "en"). Populated whenever the provider has data for the entity.
data.segmentsobject[]Timed transcript segments in playback order. Populated whenever the provider has data for the entity.
data.segments[].endSecondscan requirenumberSegment end offset in seconds.
data.segments[].startSecondscan requirenumberSegment start offset in seconds.
data.segments[].textcan requirestringText of this transcript segment.
data.titlecan requirestringVideo title.
data.transcriptstringFull transcript text, segments joined in playback order. Populated whenever the provider has data for the entity.
foundboolean
Price
Price per requestUSD$0.001
Price /1k reqUSD$1.00

FAQ

About the YouTube Video transcript full API

The AnyAPI YouTube Video transcript full API returns YouTube video transcript full data as normalized JSON from one POST call to /v1/run/youtube.video_transcript_full. Fetch a YouTube video or Short transcript with timed segments and its provenance: whether the words are creator-written captions or machine speech recognition. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 97.9% of YouTube video transcript full calls through AnyAPI succeeded, with a median response time of 17.5 seconds across 146 measured calls.

It costs from $1 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

Fetch a YouTube video or Short transcript with timed segments and its provenance: whether the words are creator-written captions or machine speech recognition. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 97.9% of YouTube video transcript full calls through AnyAPI succeeded, with a median response time of 17.5 seconds across 146 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.