SMS OTP Verification API

Send OTP to your clients to verify their accounts or for whatever use you want. Implement MFA or send promo codes with this API.

About the API:

This API will allow you to send OTP (One-time Passwords) to your users. It's ideal to improve security and have Multiple Factor Authentication on your sites/apps.  

 

What this API receives and what your API provides (input/output)?

You will pass the receiver's phone number and the API will automatically send a code to the user. You later will have the opportunity to verify the sent code and authenticate the login or whatever you need to authenticate. 

 

What are the most common uses cases of this API?

Prevent online identity theft

One of the great advantages of using one-time passwords to secure access is that they become invalid within a few seconds, which prevents hackers from retrieving the secret codes and reusing them.

Reduce support from IT team

When choosing an MFA solution that is natively 2-factor, and therefore where along with the OTP there is no need to require the user to enter the combination login & password (passwordless MFA solution) - then and again only then - IT support teams are less likely to be solicited from end-users for password resets. For sure, end-users are unlikely to make a mistake with a simple knowledge factor such as a PIN code to be remembered. It’s a win-win for users and support teams.

Overcome password security issues

Once again, this is the case only when going for a passwordless authentication that is natively 2-factor. IT administrators and CISOs can avoid the common issues encountered when it comes to password security (weak passwords, sharing credentials, reusing the same password across multiple accounts and systems, etc.).

Improves user experience

While some MFA solutions will send OTP by push notification or SMS to users, asking them to retype and enter it in their login window. MFA generates and validates OTPs in a way that improves the user's login experience. Indeed, the solution will silently generate and validate the OTP, in a transparent way for the user, allowing him/her to have a simple and passwordless login experience.

 

Are there any limitations with your plans?

Besides the number of API calls per month, there are no other limitations. 

API Documentation

Endpoints


Generate and send OTP to Mobile number. An otp_id will be returned for successful submission and it is required for OTP Verification.

{code} needs to be always present as it will be in charge of automatically generating your OTP codes. 



                                                                            
POST https://www.zylalabs.com/api/136/sms+otp+verification+api/176/send+otp
                                                                            
                                                                        

Send OTP - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"Example Response":"No response example available for now."}
                                                                                                                                                                                                                    
                                                                                                    

Send OTP - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/136/sms+otp+verification+api/176/send+otp' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "expiry": 900,
    "message": "Your otp code is {code}",
    "mobile": 19259532799,
    "sender_id": "SMSInfo"
}'

    

Use this endpoint to validate the OTP that was sent to the user. 

You need to pass the OTP code that was sent (this will be inserted by the user). 

Also, you need to pass the otp_id (that was generated on Send OTP endpoint, this will be inserted by the developer). 



                                                                            
POST https://www.zylalabs.com/api/136/sms+otp+verification+api/177/validate+otp
                                                                            
                                                                        

Validate OTP - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"Example Response":"No response example available for now."}
                                                                                                                                                                                                                    
                                                                                                    

Validate OTP - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/136/sms+otp+verification+api/177/validate+otp' --header 'Authorization: Bearer YOUR_API_KEY' 
--data-raw '{
    "otp_code": "the code that was sent to the user",
    "otp_id": "the ID that was provided in SEND OTP endpoint"
}'

    

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 SMS OTP Verification API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [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.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

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, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.


Related APIs