With advance speech-to-text algorithms, this API will retrieve the data from audio as text.
Just pass the audio URL and receive the text as a response.
This API is ideal for those users that need to solve audio captchas on the fly. Be able to verify accounts that need audio captcha solving with this API.
Besides API call limitations per month, there is a limitation of 5 API calls per day on a free plan.
To use this endpoint, you must specify the URL of an MP3 audio file in the parameter. You will also have a parameter in which you must indicate the language code of the audio.
Audio Transcription - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"data": "hello world"}
curl --location --request POST 'https://zylalabs.com/api/500/audio+captcha+solver+api/14544/audio+transcription' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"audioUrl": "https://s31.aconvert.com/convert/p3r68-cdx67/6inu9-m9nff.mp3",
"language": "en-US"
}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The API returns text data extracted from audio captcha inputs. The output is a string that represents the decoded information from the audio file.
The primary field in the response is the decoded text string, which contains the characters or words represented in the audio captcha.
The response is structured as a JSON object containing the decoded text. For example, a typical response might look like: `{"result": "1I8I8I"}`.
The API specifically retrieves and converts audio captcha data into readable text, enabling automated verification processes for user accounts.
Users can customize requests by providing different audio URLs to the API. Each URL should point to a valid audio captcha file for processing.
The data is sourced from audio captcha files provided by users through the API. The accuracy of the output relies on the quality of the audio input.
The API employs advanced speech-to-text algorithms to enhance accuracy. Continuous improvements and updates to these algorithms help maintain high-quality results.
Common use cases include automating the solving of audio captchas for account verification, enhancing user experience, and integrating captcha solving into applications that require user authentication.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
2,570ms
Service Level:
100%
Response Time:
235ms
Service Level:
100%
Response Time:
13,953ms
Service Level:
100%
Response Time:
4,790ms
Service Level:
100%
Response Time:
731ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
84ms
Service Level:
100%
Response Time:
691ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
711ms
Service Level:
100%
Response Time:
3,147ms
Service Level:
97%
Response Time:
2,966ms
Service Level:
100%
Response Time:
1,414ms
Service Level:
100%
Response Time:
1,779ms
Service Level:
100%
Response Time:
1,409ms
Service Level:
100%
Response Time:
1,948ms
Service Level:
100%
Response Time:
199ms
Service Level:
100%
Response Time:
3,531ms
Service Level:
100%
Response Time:
324ms
Service Level:
100%
Response Time:
521ms