The Backendless Twilio integration plugin enables you to implement a phone number-based login and two-factor authentication for your app. It also provides API for SMS and MMS messaging.
This week, Backendless is releasing two new plugins for the Backendless Marketplace that will give you added capabilities and flexibility when building your app. The first, as indicated above, is our integration with Twilio.
Twilio is a service that facilitates engagement with users through text/SMS/MMS, phone and video, chatbots, and more. With the Twilio Integration Plugin for Backendless, you gain access to all of the powerful Twilio features (Twilio account required). Twilio can further bolster your login process supported by Backendless’ User Service APIs.
Twilio enables two-factor authentication, a valuable security feature for apps that require users to log in. Two-factor authentication (2FA) is an added layer of protection for user accounts beyond just username and password. Anytime you’ve been asked to verify your login with a code texted to you, that was a form of 2FA.
The Twilio plugin allows you to add 2FA functionality to your app. For example, when a user creates an account, before that user is able to login, they will be required to confirm their phone number. A verification code is sent as a text message to the user’s provided phone number. This code must be entered into the app in order for the registration to be authenticated.
In order to achieve 2FA, you must collect the user’s phone number or another form of contact information beyond just email address. With 2FA, you can still require that the user verify his or her email address (user email confirmation is automatically included in Backendless).
To learn how to add the Twilio plugin to your app, follow the steps below. More detailed information about using the plugin can be found in the plugin’s feature listing.
Consider the following scenario: your application’s registration form includes a field for the user’s phone number. When a user creates an account, they provide a phone number that you would like to verify before their account is enabled. They can then log in after the registration process is complete.
The process of user registration with phone number confirmation consists of the following steps:
password– user’s password
transactionId– this is the value from step 1.
transactionCode– this is the code sent to the user’s phone in step 2.
phoneNumber– this is the same number used in step 1. This is required as a security measure.
It is possible to configure your application to use the phoneNumber column as identity. In this case, the second registration API call will include only four properties (
We hope you’ll find this exciting new integration to be a valuable addition to your application. We can’t wait to see how you put it to use!