Youtube Subtitles Extractor API

The YouTube Subtitles Extractor API allows developers to easily extract subtitles and closed captioning from YouTube videos in multiple languages. It enables users to get subtitles in SRT format, which is widely supported by various platforms and players. The API also supports multiple languages which provide more flexibility and accessibility. This feature enables developers to build a variety of subtitle-based applications like subtitle translation, subtitle download, and captioning tools for hearing-impaired people.

About the API:

The YouTube Subtitles Extractor API allows developers to easily extract subtitles and closed captions from YouTube videos in multiple languages. The API enables users to get subtitles as SRT format which is widely supported by various platforms and players. This feature enables developers to build a variety of subtitle-based applications like subtitle translation, subtitle download and captioning tool for hearing-impaired people.
With the API, developers can extract subtitles and closed captions in real-time, directly from YouTube videos. This eliminates the need for manual data entry and saves time for developers who need to add subtitle functionality to their apps. Additionally, the API support for multiple languages provides more flexibility and accessibility, making it ideal for building multilingual applications.
The API also support for extracting subtitles from any public YouTube video which means, developers can use this API for any YouTube video not just the ones they uploaded. This makes it ideal for building a variety of apps and services, such as language learning apps, subtitle translation tools, and closed captioning services for hearing-impaired users.
One of the great benefit of using this API is that it allows developer to automatically generate subtitles and captions to the videos in an accurate and efficient way, making it a great solution for organizations looking to add subtitles to their videos or improve the accessibility of their videos.
Overall, the YouTube Subtitles Extractor API is a powerful tool for developers looking to add subtitle functionality to their apps and services. It saves time, eliminates the need for manual data entry, and provides support for multiple languages, making it ideal for a wide range of use cases.

 

What this API receives and what your API provides (input/output)?

Pass the Video ID from Youtube and receive the subtitles in SRT format.

 

What are the most common uses cases of this API?

  1. Building a subtitle translation tool that uses the API to extract subtitles from YouTube videos in one language and then automatically translate them to another language.
  2. Creating a subtitle download feature for a media player or streaming service, which uses the API to extract subtitles in SRT format from YouTube videos.
  3. Developing an accessibility tool for hearing-impaired users, which uses the API to extract subtitles and closed captions from YouTube videos and display them on the screen.
  4. Building a language learning app that uses the API to extract subtitles from YouTube videos in a foreign language and provide interactive exercises to help users learn.
  5. Developing a subtitle editor tool that uses the API to extract subtitles from YouTube videos and allow users to edit and make their own subtitles.
  6. Creating a subtitle analytics tool that uses the API to extract subtitles from a large number of YouTube videos and analyze them for various language learning insights,

 

Are there any limitations to your plans?

Besides API call limitations per month, there are no other limitations. 

API Documentation

Endpoints


Pass the Video ID to this endpoint and receive the subtitles in SRT format. 



                                                                            
GET https://zylalabs.com/api/913/youtube+subtitles+extractor+api/726/extract+subtitles
                                                                            
                                                                        

Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            1
00:00:00,0 --> 00:00:07,0
0 --> 7
المترجم: Ali Sumait
المدقّق: Ahmad Altamimi

2
00:00:12,644 --> 00:00:14,15
12.645 --> 14.015
عندما كنت في الجامعة ..

3
00:00:15,349 --> 00:00:16,913
15.349 --> 16.913
كان تخصصي في العمل الحكومي

4
00:00:16,937 --> 00:00:19,399
16.937 --> 19.399
ما يعني أن علي كتابة الكثير من الأوراق،

5
00:00:19,422 --> 00:00:21,471
19.423 --> 21.471
الآن عندما يكتب أي طالب عادي ورقة

6
00:00:21,495 --> 00:00:23,867
21.495 --> 23.868
يبدو جدول عمله هكذا تقريبا..

7
00:00:23,891 --> 00:00:25,42
23.892 --> 25.043
كما ترون..

8
00:00:25,67 --> 00:00:26,724
25.067 --> 26.724
(ضحك)

9
00:00:26,748 --> 00:00:28,574
26.748 --> 28.575
يكون العمل في البداية بطيئاً ،

10
00:00:28,599 --> 00:00:30,567
28.599 --> 30.567
لكنك تنجز خلال الأسبوع الأول بما يكفي

11
00:00:30,591 --> 00:00:32,421
30.591 --> 32.422
لأن يجعلك ترى الأيام الثقيلة القادمة

12
00:00:32,445 --> 00:00:34,603
32.446 --> 34.603
تبدو منتجة و لطيفة ..

13
00:00:34,627 --> 00:00:35,829
34.627 --> 35.829
(ضحك)

14
00:00:35,853 --> 00:00:38,124
35.853 --> 38.124
و أنا أتمنى أن أفعل هذا بالشكل نفسه،

15
00:00:38,148 --> 00:00:39,341
38.148 --> 39.342
هكذا ستكون الخطة..

16
00:00:39,365 --> 00:00:41,856
39.366 --> 41.856
سأبدأ بكتابة الجدول للشروع في العمل،

17
00:00:41,880 --> 00:00:44,374
41.88 --> 44.374
ثم يأتي الوقت للكتابة ..

18
00:00:44,398 --> 00:00:46,338
44.398 --> 46.339
و ينتهي بي الأمر هكذا !

19
00:00:46,362 --> 00:00:48,732
46.363 --> 48.733
(ضحك)

20
00:00:48,756 --> 00:00:50,899
48.757 --> 50.9
و هذا يحدث في كل ورقة أكتبها ..

21
00:00:51,637 --> 00:00:55,520
51.638 --> 55.52
إلى أن طلب مني كتابة أطروحة 
التخرج من 90 صفحة ،

22
00:00:55,543 --> 00:00:57,831
55.544 --> 57.831
ورقة من المفترض أن نعمل عليها طوال العام !

23
00:00:57,854 --> 00:01:01,473
57.855 --> 61.474
و لورقة كهذه ، 
جدول عملي المعتاد لم يكن خيارًا ..

24
00:01:01,497 --> 00:01:02,899
61.498 --> 62.899
لأن المشروع كان ضخماً جداً

25
00:01:02,923 --> 00:01:04,75
62.923 --> 64.076
بدأت التخطيط للمشروع ،

26
00:01:04,99 --> 00:01:07,305
64.1 --> 67.305
و قررت أن الجدول يجب أن يشبه
شيئاً كهذا ..

27
00:01:07,781 --> 00:01:09,233
67.781 --> 69.233
هكذا ستمضي السنة ..

28
00:01:09,257 --> 00:01:11,224
69.257 --> 71.224
سأبدأ بالعمل السهل و الخفيف ،

29
00:01:11,248 --> 00:01:13,566
71.248 --> 73.566
ثم سأزيد الجهد قليلا في منتصف السنة ،

30
00:01:13,590 --> 00:01:16,215
73.59 --> 76.216
و في نهاية العام سأعمل بأقصى جهد لدي ..

31
00:01:16,239 --> 00:01:17,679
76.24 --> 77.679
سيكون سهلًا جداً
كصعود السلم ، درجة درجة .

32
00:01:17,703 --> 00:01:19,765
77.703 --> 79.765
كم يمكن أن يكون صعود الدرج صعبًا ؟

33
00:01:20,233 --> 00:01:21,552
80.233 --> 81.552
ليس بالأمر الكبير ، صحيح ؟

34
00:01:23,90 --> 00:01:24,900
83.09 --> 84.9
لكن حصل لي أطرف شيء ..

35
00:01:24,924 --> 00:01:26,234
84.924 --> 86.235
في الشهور الأولى ،

36
00:01:26,790 --> 00:01:27,957
86.791 --> 87.958
جاءت و مضت بسرعة،

37
00:01:27,981 --> 00:01:29,566
87.982 --> 89.567
و لم أستطع تأدية أي شيء .

38
00:01:29,590 --> 00:01:31,439
89.591 --> 91.44
فقررت أن أغير خطتي قليلا ..

39
00:01:31,463 --> 00:01:32,631
91.464 --> 92.631
(ضحك)

40
00:01:32,655 --> 00:01:33,813
92.655 --> 93.814
ثم ...

41
00:01:33,837 --> 00:01:35,719
93.838 --> 95.72
(ضحك)

42
00:01:35,743 --> 00:01:38,528
95.744 --> 98.528
لكن في الحقيقة 
مضى منتصف العام بسرعة،

43
00:01:38,552 --> 00:01:40,733
98.552 --> 100.734
و لم أكتب كلمة واحدة .

44
00:01:40,757 --> 00:01:42,593
100.758 --> 102.593
فأصبحت الآن هنا !

45
00:01:43,500 --> 00:01:46,75
103.5 --> 106.076
تقلص الشهرين لشهر واحد ..

46
00:01:46,99 --> 00:01:47,724
106.1 --> 107.725
ثم إلى أسبوعين ..

47
00:01:47,748 --> 00:01:49,58
107.749 --> 109.058
و في أحد الأيام استيقظت ،

48
00:01:49,724 --> 00:01:52,343
109.724 --> 112.343
و لم يبق إلا ثلاثة أيام على التسليم !!

49
00:01:53,501 --> 00:01:55,433
113.502 --> 115.433
و لم أكتب أي كلمة حتى الآن ،

50
00:01:55,456 --> 00:01:57,516
115.457 --> 117.516
ففعلت الشيء الوحيد الذي يمكنني فعله ،

51
00:01:57,540 --> 00:02:00,147
117.54 --> 120.147
كتبت 90 صفحة في 72 ساعة ،

52
00:02:00,171 --> 00:02:02,447
120.171 --> 122.447
وواصلت يومين كاملين بدون نوم ..

53
00:02:02,471 --> 00:02:05,40
122.471 --> 125.04
و لا يجب على البشر السهر يومين بدون نوم ،

54
00:02:06,373 --> 00:02:08,366
126.373 --> 128.366
هرعت جريًا إلى الجامعة ،

55
00:02:08,389 --> 00:02:09,875
128.39 --> 129.87599999999998
بالحركة البطيئة سلمت الورقة على

56
00:02:09,900 --> 00:02:11,955
129.9 --> 131.956
الموعد المحدد بالضبط !

57
00:02:11,979 --> 00:02:14,3
131.98 --> 134.004
ظننت أنني أنجزت كل شيء .

58
00:02:14,27 --> 00:02:15,586
134.028 --> 135.587
بعد أسبوع ، جائني اتصال ،

59
00:02:15,610 --> 00:02:17,97
135.611 --> 137.097
كان اتصالًا من الجامعة .

60
00:02:17,757 --> 00:02:19,395
137.757 --> 139.396
سألوا: "هل أنت تيم أوربن؟"

61
00:02:19,419 --> 00:02:20,888
139.42 --> 140.888
فجاوبت: "نعم."

62
00:02:20,912 --> 00:02:23,252
140.912 --> 143.252
قالوا: "يجب أن نتناقش 
معك بخصوص أطروحتك" ..

63
00:02:23,276 --> 00:02:24,531
143.276 --> 144.531
قلت : "حسنًا."

64
00:02:25,467 --> 00:02:26,689
145.468 --> 146.69
فقالوا ..

65
00:02:27,229 --> 00:02:29,126
147.23 --> 149.126
"إنها أفضل أطروحة رأيناها في حياتنا" !

66
00:02:29,150 --> 00:02:30,854
149.15 --> 150.855
(ضحك)

67
00:02:32,14 --> 00:02:34,704
152.014 --> 154.704
(تصفيق)

68
00:02:36,944 --> 00:02:38,247
156.945 --> 158.247
هذا لم يحصل في الحقيقة ،

69
00:02:38,270 --> 00:02:40,408
158.271 --> 160.409
(ضحك)

70
00:02:40,432 --> 00:02:43,56
160.433 --> 163.056
كانت أطروحة سيئة إلى أبعد الحدود ..

71
00:02:43,80 --> 00:02:45,354
163.08 --> 165.354
(ضحك)

72
00:02:45,377 --> 00:02:49,478
165.378 --> 169.478
أردت فقط أن أستمتع باللحظة عندما ظننتم :

73
00:02:49,502 --> 00:02:51,407
169.502 --> 171.407
"هذا الرجل مذهل"!

74
00:02:51,431 --> 00:02:52,778
171.431 --> 172.779
(ضحك)

75
00:02:52,802 --> 00:02:54,469
172.803 --> 174.47
لا، لا، كانت سيئة جدا

76
00:02:55,342 --> 00:02:58,751
175.343 --> 178.751
على كل حال ،
اليوم أنا كاتب و مدون في الإنترنت ..

77
00:02:58,775 --> 00:03:00,518
178.775 --> 180.518
أكتب في مدونة اسمها "انتظر لكن لماذا؟"

78
00:03:00,542 --> 00:03:04,277
180.542 --> 184.278
قبل سنتين قررت أن أدون عن التسويف والتأجيل

79
00:03:04,301 --> 00:03:07,586
184.302 --> 187.586
كانت تصرفاتي دائمًا تحيِّر 
غير المسوِّفين من حولي ولماذا أؤجل أعمالي

80
00:03:07,610 --> 00:03:11,298
187.61 --> 191.298
فأردت أن أشرح لهؤلاء و للعالم ، ما يجري في

81
00:03:11,322 --> 00:03:13,429
191.322 --> 193.429
رؤوس الذين يسوفون و يؤجلون أعمالهم ،

82
00:03:13,453 --> 00:03:14,893
193.453 --> 194.893
و لماذا نحن هكذا .

83
00:03:14,917 --> 00:03:16,73
194.917 --> 196.073
كانت لدي نظرية تقول

84
00:03:16,97 --> 00:03:18,951
196.097 --> 198.952
أن عقول المسوِّفين حقيقةً

85
00:03:18,975 --> 00:03:20,932
198.976 --> 200.933
تختلف عن الأشخاص الآخرين

86
00:03:21,698 --> 00:03:23,889
201.698 --> 203.889
و لاختبار هذا ، وجدت مختبرًا سمح لي

87
00:03:23,913 --> 00:03:26,344
203.913 --> 206.345
باستخدام جهاز الرنين 
المغناطيسي لتصوير مخي

88
00:03:26,368 --> 00:03:29,24
206.369 --> 209.024
ومخ رجل آخر لايؤجل أعماله

89
00:03:29,48 --> 00:03:30,483
209.048 --> 210.483
لأستطيع المقارنة بينهما ،

90
00:03:30,507 --> 00:03:32,707
210.507 --> 212.708
و أحضرت الصور معي لترونها اليوم بنفسكم ،

91
00:03:32,731 --> 00:03:36,269
212.732 --> 216.269
أريدكم الآن أن تأخذوا نظرة فاحصة
لتلاحظوا إن كان هناك اختلاف ..

92
00:03:36,293 --> 00:03:38,606
216.293 --> 218.607
أنا أعلم أنه ليس كلكم خبراء ،

93
00:03:38,631 --> 00:03:40,894
218.631 --> 220.894
و أنها ليست واضحة و لكن فقط
انظروا ، حسنًا ؟

94
00:03:40,918 --> 00:03:43,45
220.918 --> 223.046
إذًا هنا صورة مخ الذي لا يؤجل ،

95
00:03:43,835 --> 00:03:46,109
223.835 --> 226.109
(ضحك)

96
00:03:46,133 --> 00:03:47,283
226.133 --> 227.284
و الآن ..

97
00:03:48,324 --> 00:03:49,639
228.325 --> 229.639
هنا صورة مخي .

98
00:03:50,280 --> 00:03:53,6
230.28 --> 233.006
(ضحك)

99
00:03:55,712 --> 00:03:57,276
235.713 -->...
                                                                                                                                                                                                                    
                                                                                                    

Extract Subtitles - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/913/youtube+subtitles+extractor+api/726/extract+subtitles&videoId=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

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 Youtube Subtitles Extractor API REST 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • 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

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, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

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

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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
65%
 Response Time
509ms

Category:


Related APIs