This API will help you to recognize if two audio files' voices belong to the same person or not. Ideal for security validations.
About the API:
The API will help you to compare two audio files and recognize if the voice present in them, belong to the same person.
What this API receives and what your API provides (input/output)?
Just pass the two audio URLs
IMPORTANT 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
Later you will receive a response either positive or negative.
What are the most common uses cases of this API?
This API is ideal to make security validations on applications. For example, you can store one audio file from your customer, and ask them to send new audio to compare voices and give them access to the features.
Also, it's ideal to create security checkpoints. You can create a voice checkpoint in a building entrance, comparing the two voices to give access.
Those are some use cases, you can use them for the project you want!
Are there any limitations to your plans?
Besides the number of API calls per month, there are no other limitations.
Voice Coincidence 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
Voice Verificator - Endpoint Features
[Required] First audio URL to check.
[Required] Second audio URL to compare.
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 Voice Coincidence Verification API REST API, simply include your bearer token in the Authorization header.
[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.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. 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 with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
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.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]