PresentID Speaker verification API checks whether two voices belong to the same person or not. This capability is potentially useful in call centers.
We have proposed a deep learning-based method for speaker verification. Our team worked on this project for more than 1 year and the accuracy has passed over benchmarks such as the accuracy of the paper by Andrew Zisserman Group at Oxford University. In contrast with other methods that are text-dependent, our model is text and language-independent. On the other hand, the processing speed of our model is less than 1 sec and the model verifies a person by just two voices with a length of 4 secs. We have trained the model on tracks with English, French, Spanish, German, Persian, and Arabic languages. Our model is robust to the environment and virtual noises.
**Input:**
- Voice file
- Voice URL link
- Base64 Voice
**Output:**
- Result index
- Result message
**Features:**
- Accuracy over 90%.
- Less than 1 second processing time.
- No need for GPU.
- Language & text-independent.
- Easy integration with your app.
- Support IOS, Android, Windows, and Mac devices.
- Easy integration with your app.
**Use Cases:**
- Call center
**Rules & Restrictions:**
- Send data via Base64 or a voice URL or voice file.
- The voice must be between three seconds and one minute.
- The voices must not exceed 5 MB.
- Supported file types: WAV, MP3, M4A, FLAC, AAC, OGG.
Speaker verification API checks whether two voices belong to one person or not
The voice must be between three seconds and one minute
The voices must not exceed 5 MB
Supported file types: wav, mp3, m4a, FLAC, aac, ogg
Send voice with voice file - Endpoint Features
| Object | Description |
|---|
{
"data": {
"resultIndex": 0,
"resultMessage": "The two voices don't belong to the same person."
},
"hasError": false,
"statusCode": 200,
"statusMessage": "Login Successfull"
}
curl --location --request POST 'https://zylalabs.com/api/4004/speaker+verification/4784/send+voice+with+voice+file' --header 'Authorization: Bearer YOUR_API_KEY'
Speaker verification API checks whether two voices belong to one person or not
The voice must be between three seconds and one minute
The voices must not exceed 5 MB
Supported file types: wav, mp3, m4a, FLAC, aac, ogg
Send voice with Base64 - Endpoint Features
| Object | Description |
|---|
{"statusCode":400,"statusMessage":"You must upload a sound file.","hasError":true,"features":null}
curl --location --request POST 'https://zylalabs.com/api/4004/speaker+verification/4785/send+voice+with+base64' --header 'Authorization: Bearer YOUR_API_KEY'
Speaker verification API checks whether two voices belong to one person or not.
The voice must be between three seconds and one minute
The voices must not exceed 5 MB
Supported file types: wav, mp3, m4a, FLAC, aac, ogg
Send voice with Voice URL - Endpoint Features
| Object | Description |
|---|
{"statusCode":400,"statusMessage":"You must upload a sound file.","hasError":true,"features":null}
curl --location --request POST 'https://zylalabs.com/api/4004/speaker+verification/4786/send+voice+with+voice+url' --header 'Authorization: Bearer YOUR_API_KEY'
| 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 PresentID Speaker Verification API is designed to confirm whether two voice samples originate from the same person. This functionality is essential for applications requiring secure identity verification through voice, such as in banking, access control, and remote authentication scenarios.
To use the API, you will need to submit two separate audio clips via a POST request. The API analyzes the voice characteristics of both samples, comparing features such as pitch, tone, and modulation to determine if they match. It then returns a confidence score or a binary result indicating whether the voices are from the same individual.
The API accepts common audio file formats, including WAV, MP3, and AAC. For best results, ensure that the recordings are clear, with minimal background noise, and that the spoken content is similar in both samples.
Yes, the API has limitations that vary depending on the subscription plan you select. These limitations may involve the size of the audio files you can upload and the number of verification requests you can make per day or month. For specific details, please refer to the pricing page or your user dashboard.
You might encounter several common errors: 400 Bad Request: This error often occurs if the audio files are too large, corrupted, or in an incorrect format. Ensure your files are within the required size limits and properly formatted. 401 Unauthorized: This happens if your API key is missing, incorrect, or expired. Make sure your API key is valid and included correctly in your request headers. 429 Too Many Requests: This indicates that you have exceeded the API usage limits set by your subscription plan. Consider upgrading your plan or managing your request rate more effectively.
Each endpoint returns a JSON response containing a `data` object with a `resultIndex` and `resultMessage`. The `resultIndex` indicates whether the voices match (0 for no match, 1 for match), while the `resultMessage` provides a descriptive outcome of the verification process.
The key fields in the response data include `resultIndex`, which indicates the match status, `resultMessage`, which describes the outcome, `hasError`, indicating if an error occurred, and `statusCode` and `statusMessage` for overall request status.
The endpoints accept parameters such as the audio file (voice file, Base64, or voice URL). The audio must be between 3 seconds and 1 minute long, not exceed 5 MB, and be in supported formats like WAV, MP3, or AAC.
The response data is organized in a JSON format. It includes a `data` object with verification results and additional fields for error handling and status. This structure allows easy parsing and integration into applications.
Typical use cases include identity verification in call centers, fraud prevention in banking, and secure access control systems. The API can enhance security by confirming the identity of users based on voice samples.
Users can utilize the returned data by checking the `resultIndex` to determine if the voices match and using the `resultMessage` for detailed feedback. This information can guide further actions, such as allowing access or flagging potential fraud.
The API employs a deep learning model trained on diverse voice samples across multiple languages, ensuring high accuracy and robustness against environmental noise. Continuous testing against benchmarks helps maintain data quality.
If the API returns an error or empty results, check the audio file's format, size, and length. Ensure the input meets the specified requirements. Implement error handling in your application to manage these scenarios gracefully.
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.
Service Level:
55%
Response Time:
1,071ms
Service Level:
100%
Response Time:
1,148ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
7,343ms
Service Level:
100%
Response Time:
871ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
94%
Response Time:
659ms
Service Level:
100%
Response Time:
7,590ms
Service Level:
100%
Response Time:
1,812ms
Service Level:
100%
Response Time:
2,741ms
Service Level:
100%
Response Time:
1,356ms
Service Level:
100%
Response Time:
1,764ms
Service Level:
100%
Response Time:
1,356ms
Service Level:
100%
Response Time:
1,356ms
Service Level:
100%
Response Time:
1,356ms
Service Level:
100%
Response Time:
10,041ms
Service Level:
100%
Response Time:
787ms
Service Level:
100%
Response Time:
220ms