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.
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:
67%
Response Time:
1,057ms
Service Level:
100%
Response Time:
1,148ms
Service Level:
100%
Response Time:
3,940ms
Service Level:
100%
Response Time:
4,645ms
Service Level:
100%
Response Time:
7,634ms
Service Level:
96%
Response Time:
735ms
Service Level:
100%
Response Time:
13,953ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
64ms
Service Level:
100%
Response Time:
646ms