Verify API

Protect user accounts and valuable data with seamless OTP verification over SMS or voice calls.

SMS API Platform
Simplified secure user authentication
SMS Verification and Voice Verification
Quick SMS verification and voice verification
Plivo’s Verify API reduces the implementation time by 90% or more. Verification is added to your app in three easy steps: create an application, send an OTP, and validate it.
Lower total cost for verification
Only pay for messages sent and calls made — no added validation or phone rental fees. Working directly in the Plivo console eliminates costly operating and maintenance costs.
Lower Cost for Verification
Hassle-free OTP Verification Codes
Hassle-free OTP verification codes
No compliance issues or number rentals to worry about — Plivo takes care of required compliance registrations and uses the best phone sender IDs and templates for your use case on your behalf.
Easy to set up and use
Choose from a variety of predefined message templates and instantaneously change OTP code configurations and enable supported channels as needed, all within Plivo’s console — no coding required after the initial configuration.
Easy to Setup and Use
Effective verification with no downtime
Add Plivo Verify to your cloud communications stack to ensure critical SMS and voice OTPs reach your customers without fail.
Prevent SMS pumping before it starts
Verify’s built-in fraud protection features prevent traffic pumping attacks that cost you money.
  • Geo permission management
    Control the destination list for SMS and voice calls and disable communications to high-risk countries.
  • Pattern-based alerts
    Trigger unusual usage alerts based on historical account usage and our proprietary AI models.
  • Number validation
    Validate phone numbers before sending SMS, reducing the risk of sending messages to fraudulent numbers.
Prevent SMS Pumping before it starts
Why trust Plivo’s verification API to protect user accounts?
Plivo is the best enterprise-grade alternative to Twilio
Tens of billions of API events
Tens of billions of API events
190+ countries
190+ countries
Premium 24-hour support
Premium 24-hour support
HIPAA, SOC 2, and PCI DSS certification
HIPAA, SOC 2, and PCI DSS certification
7 global points of presence
7 global points of presence
Billions of voice calls and messages
Billions of voice calls and messages
99.99% uptime SLAs available
99.99% uptime SLAs available
Tens of billions of API events
Tens of billions of API events
190+ countries
190+ countries
Premium 24-hour support
Premium 24-hour support
HIPAA, SOC 2, and PCI DSS certification
HIPAA, SOC 2, and PCI DSS certification
7 global points of presence
7 global points of presence
Billions of voice calls and messages
Billions of voice calls and messages
99.99% uptime SLAs available
99.99% uptime SLAs available
How different industries use Verify API

Ensure online purchases are secure and made by verified customers.

Allow secure home entry and resident access via OTP.

Prevent fraudulent activity by securing account access.

Require two-factor authentication for web portal and other secure resources.

Keep patient data safe and ensure patient portal security.

Verify user details for secure app and website logins.

Verify API FAQs
 
 

Verification and authentication are typically used interchangeably, but the major distinction is that verification occurs at signup, or when you’re first ensuring that a user is who they say they are, and authentication occurs every time a user logs on in the future. Plivo Verify can be used for both use cases.

Both are great options, but they have different benefits.

  • SMS verification is fast and easy for users to complete.
  • SMS verification has great reach as almost all mobile devices support SMS functionality.
  • Voice verification provides an accessible alternative for individuals who may have visual impairments or challenges with reading.
  • Voice verification can be used for users who only have access to a landline, as landlines don’t support SMS.
  • Voice verification can be a reliable alternative or fallback in cases of delays or failures in SMS delivery, as Voice is prioritized on carrier networks, resulting in higher delivery rates compared to SMS
  • Voice offers significantly richer data points for analytics, enabling users to gain deeper insights in the event of conversion failures.

2FA refers to the use of two different types of authentication factors to verify a user’s identity. These factors can come from any of the following three categories:

  • Something you know: This could be a password, PIN, or the answer to a security question.
  • Something you have: This could be a smartphone (to receive an SMS or use an authenticator app), a smart card, or a hardware token.
  • Something you are: This refers to biometric data, like a fingerprint, facial recognition, or retina scans.
An OTP is valid for only one login session or transaction, and it relies on something you have. After entering a password (something you know), you might be sent an OTP via SMS to your phone (something you have), which you must then enter to gain access.

SMS verification is a common method used for 2FA to add an extra layer of security when verifying users’ identities. SMS verification helps ensure that the person trying to access the account or register for the service has the mobile device tied to that account. This can help prevent unauthorized access, even if someone gains access to the user's username and password.

Here are the steps in the SMS verification process:

  1. A user tries to log in to an account or register for a service and provides their mobile number to the system.
  2. The system then sends a request to the Plivo to initiate the SMS verification process for that mobile number.
  3. Plivo generates an OTP — a unique code that can be used for this one instance of verification.
  4. This OTP is sent via SMS to the user’s mobile number. Plivo also keeps a copy of this OTP to check it against the user’s input later.
  5. The user receives the OTP in an SMS message on their phone and enters the OTP into the website or application on which they’re trying to log in or sign up.
  6. The entered OTP is sent back to Plivo, which checks whether it matches the OTP that was originally generated and sent to the user.
  7. If the OTPs match, Plivo confirms that the user is verified. If not, Plivo may resend the OTP or the user may have to initiate the process again.
  8. If the user is verified, they can proceed with their intended activity, such as logging in to their account or completing their registration for a service.

Experience the power of Plivo Verify today