YouTube音频转录API提供了一个强大且高效的解决方案,用于获取任何兼容YouTube视频的详细转录。通过提供对口语内容的直接访问,API交付的结构化数据包括完整文本、时间戳、自动划分的段落,以及基本视频元数据,如标题、时长、检测到的语言和作者。每个响应都经过优化,确保清晰、一致且易于集成,使大量内容能够无缝处理。
该系统分析请求的视频,并返回组织好的文本块,附带各自的开始和结束区间,确保每个片段的跟踪准确。此外,API自动识别YouTube生成的字幕、自动字幕,并在适用的情况下,提供自定义转录。所有信息以标准化格式交付,便于在应用程序、插件、仪表板或自动化流程中使用。
该API旨在提供性能和可靠性,快速且稳定地处理请求,即使在长视频中也能保持一致的响应时间。
简而言之,YouTube音频转录API是一个专业工具,使您能够获得完整、同步的转录,随时可以使用。
要使用此端点,您必须指定视频的URL
获取转录 - 端点功能
| 对象 | 描述 |
|---|---|
请求体 |
[必需] Json |
{"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]"}
curl --location --request POST 'https://zylalabs.com/api/11456/youtube%e9%9f%b3%e9%a2%91%e8%bd%ac%e5%bd%95+api/21616/%e8%8e%b7%e5%8f%96%e8%bd%ac%e5%bd%95' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"url": "https://www.youtube.com/watch?v=N7ZmPYaXoic"
}'
| 标头 | 描述 |
|---|---|
授权
|
[必需] 应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。 |
无长期承诺。随时升级、降级或取消。 免费试用包括最多 50 个请求。
API返回YouTube视频的详细转录,包括同步文本,每个片段的时间戳,以及一些基本视频元数据如标题、时长、作者和检测到的语言
响应中的关键字段包括 `videoId` `videoTitle` `duration` `author` 以及一个包含每个转录段的 `start` `end` 和 `text` 属性的 `caption` 对象
响应是以JSON格式构建的,顶层对象包含一个状态标志、视频元数据和一个嵌套的`caption`对象,该对象包含一个转录片段数组,每个片段都有自己的时间和文本
API提供信息如完整的文本抄本、每个片段的时间戳、视频标题、时长、作者以及视频的检测语言,允许进行全面分析
用户可以通过指定他们想要转录的YouTube视频的`videoId`来自定义请求。未来的更新中可能会包含其他参数以优化输出,但目前主要关注的是视频ID
通过利用YouTube自己的字幕系统来保持数据准确性,该系统包括自动字幕和自定义转录。API处理这些数据以确保可靠和同步的输出
典型的用例包括为视频创建字幕 进行内容分析 开发教育工具 和自动化需要从视频内容中提取文本的工作流程
用户可以通过将返回的数据集成到应用程序中用于搜索功能 创建视频分析的仪表板 或根据转录文本和元数据自动生成内容
Zyla API Hub 就像一个大型 API 商店,您可以在一个地方找到数千个 API。我们还为所有 API 提供专门支持和实时监控。注册后,您可以选择要使用的 API。请记住,每个 API 都需要自己的订阅。但如果您订阅多个 API,您将为所有这些 API 使用相同的密钥,使事情变得更简单。
价格以 USD(美元)、EUR(欧元)、CAD(加元)、AUD(澳元)和 GBP(英镑)列出。我们接受所有主要的借记卡和信用卡。我们的支付系统使用最新的安全技术,由 Stripe 提供支持,Stripe 是世界上最可靠的支付公司之一。如果您在使用卡片付款时遇到任何问题,请通过 [email protected]
此外,如果您已经以这些货币中的任何一种(USD、EUR、CAD、AUD、GBP)拥有有效订阅,该货币将保留用于后续订阅。只要您没有任何有效订阅,您可以随时更改货币。
定价页面上显示的本地货币基于您 IP 地址的国家/地区,仅供参考。实际价格以 USD(美元)为单位。当您付款时,即使您在我们的网站上看到以本地货币显示的等值金额,您的卡片对账单上也会以美元显示费用。这意味着您不能直接使用本地货币付款。
有时,银行可能会因其欺诈保护设置而拒绝收费。我们建议您首先联系您的银行,检查他们是否阻止了我们的收费。此外,您可以访问账单门户并更改关联的卡片以进行付款。如果这些方法不起作用并且您需要进一步帮助,请通过 [email protected]
价格由月度或年度订阅决定,具体取决于所选计划。
API 调用根据成功请求从您的计划中扣除。每个计划都包含您每月可以进行的特定数量的调用。只有成功的调用(由状态 200 响应指示)才会计入您的总数。这确保失败或不完整的请求不会影响您的月度配额。
Zyla API Hub 采用月度订阅系统。您的计费周期将从您购买付费计划的那一天开始,并在下个月的同一日期续订。因此,如果您想避免未来的费用,请提前取消订阅。
要升级您当前的订阅计划,只需转到 API 的定价页面并选择您要升级到的计划。升级将立即生效,让您立即享受新计划的功能。请注意,您之前计划中的任何剩余调用都不会转移到新计划,因此在升级时请注意这一点。您将被收取新计划的全部金额。
要检查您本月剩余多少 API 调用,请参考响应标头中的 "X-Zyla-API-Calls-Monthly-Remaining" 字段。例如,如果您的计划允许每月 1,000 个请求,而您已使用 100 个,则响应标头中的此字段将显示 900 个剩余调用。
要查看您的计划允许的最大 API 请求数,请检查 "X-Zyla-RateLimit-Limit" 响应标头。例如,如果您的计划包括每月 1,000 个请求,此标头将显示 1,000。
"X-Zyla-RateLimit-Reset" 标头显示您的速率限制重置之前的秒数。这告诉您何时您的请求计数将重新开始。例如,如果它显示 3,600,则意味着还有 3,600 秒直到限制重置。
是的,您可以随时通过访问您的账户并在账单页面上选择取消选项来取消您的计划。请注意,升级、降级和取消会立即生效。此外,取消后,您将不再有权访问该服务,即使您的配额中还有剩余调用。
您可以通过我们的聊天渠道联系我们以获得即时帮助。我们始终在线,时间为上午 8 点至下午 5 点(EST)。如果您在该时间之后联系我们,我们将尽快回复您。此外,您可以通过 [email protected]
为了让您有机会在没有任何承诺的情况下体验我们的 API,我们提供 7 天免费试用,允许您免费进行最多 50 次 API 调用。此试用只能使用一次,因此我们建议将其应用于您最感兴趣的 API。虽然我们的大多数 API 都提供免费试用,但有些可能不提供。试用在 7 天后或您进行了 50 次请求后结束,以先发生者为准。如果您在试用期间达到 50 次请求限制,您需要"开始您的付费计划"以继续发出请求。您可以在个人资料中的订阅 -> 选择您订阅的 API -> 定价标签下找到"开始您的付费计划"按钮。或者,如果您在第 7 天之前不取消订阅,您的免费试用将结束,您的计划将自动计费,授予您访问计划中指定的所有 API 调用的权限。请记住这一点以避免不必要的费用。
7 天后,您将被收取试用期间订阅的计划的全额费用。因此,在试用期结束前取消很重要。因忘记及时取消而提出的退款请求不被接受。
当您订阅 API 免费试用时,您可以进行最多 50 次 API 调用。如果您希望超出此限制进行额外的 API 调用,API 将提示您执行"开始您的付费计划"。您可以在个人资料中的订阅 -> 选择您订阅的 API -> 定价标签下找到"开始您的付费计划"按钮。
付款订单在每月 20 日至 30 日之间处理。如果您在 20 日之前提交请求,您的付款将在此时间范围内处理。
服务级别:
100%
响应时间:
1,157ms
服务级别:
100%
响应时间:
444ms
服务级别:
100%
响应时间:
641ms
服务级别:
100%
响应时间:
1,153ms
服务级别:
100%
响应时间:
522ms
服务级别:
100%
响应时间:
968ms
服务级别:
100%
响应时间:
2,278ms
服务级别:
100%
响应时间:
778ms
服务级别:
100%
响应时间:
576ms
服务级别:
100%
响应时间:
1,153ms
服务级别:
100%
响应时间:
2,958ms
服务级别:
100%
响应时间:
360ms
服务级别:
100%
响应时间:
393ms
服务级别:
100%
响应时间:
1,354ms
服务级别:
100%
响应时间:
358ms
服务级别:
100%
响应时间:
567ms
服务级别:
100%
响应时间:
1,654ms
服务级别:
100%
响应时间:
2,585ms
服务级别:
100%
响应时间:
370ms
服务级别:
100%
响应时间:
453ms