Fetch YouTube Transcripts API

Easily fetch transcripts from YouTube videos, streamlining content creation and research efforts.
Use this API from your AI agent via MCP
Works with OpenClaw, Claude Code/Desktop, Cursor, Windsurf, Cline and any MCP-compatible AI client.
Docs & setup
Create a skill by wrapping this MCP: https://mcp.zylalabs.com/mcp?apikey=YOUR_ZYLA_API_KEY

The Fetch YouTube Transcripts API offers a robust and efficient solution for obtaining detailed transcripts of any compatible YouTube video. By providing direct access to spoken content, the API delivers structured data that includes the full text, timestamps, automatically divided segments, and essential video metadata such as title, duration, detected language, and author. Each response is optimized to be clear, consistent, and easy to integrate, allowing large amounts of content to be processed seamlessly.

The system analyzes the requested video and returns organized blocks of text accompanied by their respective start and end intervals, ensuring accuracy in tracking each fragment. In addition, the API automatically identifies YouTube-generated captions, automatic subtitles, and, where applicable, custom transcripts. All information is delivered in a standardized format that facilitates its use in applications, plugins, dashboards, or automated flows.

Designed for performance and reliability, this API handles requests quickly and stably, maintaining consistent response times even with long videos.

In short, the Fetch YouTube Transcripts API is a professional tool that allows you to obtain complete, synchronized transcripts that are ready for immediate use.

API Documentation

Endpoints


To use this endpoint, you must specify the URL of a video.



                                                                            
POST https://www.zylalabs.com/api/11460/fetch+youtube+transcripts+api/21620/get+transcription
                                                                            
                                                                        

Get Transcription - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                                                                                                                                        {"transcription":"Writing code is writing a precise set of instructions a computer or device can understand. It's explaining exactly what you want your computer to do at any given moment. Computers need to know exactly how to react to things like the clicking of a mouse or the pushing of a button. And whatever happens ultimately is happening because of lines of code written by a human programmer. Just about anything with a plug or battery uses code. It's keeping our airplanes in the air. It's allowing you to swipe a credit card. And the computer doesn't know what to do in any given situation. It has to be taught everything. So you can think of a computer programmer explaining to a computer what we want it to do as like trying to give someone directions for how to drive somewhere when they don't even know what a car is. So you can see what kind of complications you'd run into. uh you'd have to not only tell them how to get to where they're going, but you'd also have to give them contingency plans for things like what if there's a traffic jam or what if a truck breaks down in the turn lane. And you'd even need to explain precisely how the steering wheel or gas pedal works. So that's kind of like a computer programmer writing code for a computer. They have to basically teach it everything every time. To understand that communication and how this process even started, you have to go back to the industrial revolution where the first computer program was invented in 1801 by a guy named Joseph Jakard. He developed a system of weaving instructions or code for his sewing looms that could be stored on cards with holes. And there was a mechanism that would go along the card and try to push a pin through. And so either the pin would go through or it wouldn't. It's binary. It's either it does or it doesn't. it's a one or it's a zero. And so if the pin goes through the hole, it would allow a rod attached to it to lift, which lifts the string and lifts the associated thread. And if the pin does not go through a hole, the pin doesn't move and the thread doesn't move. So essentially, the card would hold a preset pattern that is read by the loom and serves as a guide, giving the direction to the threads one at a time. And with this contraption, you could create very fancy pieces of weaving. And this idea of there being recorded information read by a machine was quickly borrowed to be applied to mathematical computation. Charles Babage invented the analytical engine in 1837 and it was basically a calculating machine. Eventually transistors are invented which replace punch cards as a way of transferring data. And nowadays, we use computers that have billions and billions of transistors, but still carrying that same basic idea of on and off to carry data. As a way of harnessing these various combinations of transistors, we use code. Computer programmers use different languages, whether it's Python for gaming, Java for desktop applications, or Objective C for an iPhone app. A computer program is only a text file following those rules and it's eventually translated into something the computer can understand. Just like the pins on Jakard's loom, a computer can only understand two things. Think of one and zero as the alphabet of a computer. It's like if you look at the alphabet of the English language, there's only 26 letters and by themselves, they're meaningless. But when you combine them into different ways, you get the Great Gatsby or Romeo and Juliet. In the same way, billions of different combinations of ones and zeros have the potential to give us Microsoft Word or iTunes. And the process goes like this. On the top level, you have a human writing code for a specific computer language. And after this, the code is translated or compiled into a low-level language by a tool called a compiler. And finally, the code is translated into binary or machine language by an assembler. So because we have a way of translating human orders in the form of code into ones and zeros that a computer can understand after that it's really just a matter of what you want the computer to do. And it's like being a chef writing a recipe because both chefs writing recipes and computer programmers writing code both have the ability to create something awesome using the resources and tools available. [Music] [Music]"}
                                                                                                                                                                                                                    
                                                                                                    

Get Transcription - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/11460/fetch+youtube+transcripts+api/21620/get+transcription' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
  "url": "https://www.youtube.com/watch?v=N7ZmPYaXoic"
}'

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Fetch YouTube Transcripts API simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Fetch YouTube Transcripts API FAQs

The API returns detailed transcripts of YouTube videos, including synchronized text, timestamps for each segment, and essential video metadata such as title, duration, author, and detected language.

Key fields in the response include `videoId`, `videoTitle`, `duration`, `author`, and a `caption` object that contains segments with `start`, `end`, and `text` attributes for each transcript segment.

The response is structured in JSON format, with a top-level object containing a status flag, video metadata, and a nested `caption` object that holds an array of transcript segments, each with its own timing and text.

The API provides information such as the full transcript text, timestamps for each segment, video title, duration, author, and the detected language of the video, allowing for comprehensive analysis.

Users can customize requests by specifying the `videoId` of the YouTube video they want to transcribe. Additional parameters may be included in future updates to refine the output, but currently, the primary focus is on the video ID.

Data accuracy is maintained by leveraging YouTube's own captioning system, which includes automatic subtitles and custom transcripts. The API processes this data to ensure reliable and synchronized output.

Typical use cases include creating subtitles for videos, conducting content analysis, developing educational tools, and automating workflows that require text extraction from video content.

Users can utilize the returned data by integrating it into applications for search functionality, creating dashboards for video analytics, or automating content generation based on the transcribed text and metadata.

General FAQs

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]


Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.


Related APIs