SMS Verify - Overview

Telesign SMS Verify delivers phone-based verification and multi-factor authentication (MFA) using a limited duration, one-time passcode (OTP) sent over SMS.

Common use cases

Multi-factor authentication (MFA) - Send an OTP to a user's phone number, to complete a sign in process after they have entered their password.
Password reset - Send an OTP to a user's phone number to verify their identity before they reset their account password.
Phone number verification - Send an OTP to a phone number provided by a user to verify their ownership of the number.
Account update: Send an OTP to a user's phone number to validate critical interactions such as high-value transactions, account updates, and money transfers.

📘
NOTE:
To send SMS messages for other purposes besides delivering verification codes, use Telesign SMS, not this product.

General requirements

Resource: rest-ww.telesign.com/v1/verify/sms
Protocols: https
Authentication: Basic (easiest to implement) or Digest
Encoding: Accepts only UTF-8 unicode characters as inputs.
Accepts: application/x-www-form-urlencoded
Responds with: application/json
Required headers: Content-Type - application/x-www-form-urlencoded

Documentation by category

Reference:
- POST /v1/verify/sms - Use this action to send an SMS with a verification code to a recipient phone number.
- GET /v1/verify/{reference_id} - Use this action to get the delivery status and other info for a verification transaction you have created.
- PUT /v1/verify/completion/{referenceid} - Use this action to notify Telesign that you have completed verification for an end-user.
- SMS Verify - SMPP TLVs - Lists and describes inputs for our SMPP service that are specific to SMS Verify. For a full explanation of using SMPP with Telesign, first read SMPP protocol.
Docs:

📘
NOTE:
An SMPP implementation may offer better throughput than the REST API, but the integration requires a higher level of technical expertise and may take longer.