In this post, we're going to know how to code modules in Python Django to use the Sparrow SMS API integration to verify a Nepali phone number (NTC/ Ncell) using an API as a service server-generated OTP code. This is an
works in production example of an
API as a service backend web app built around Django and Django REST framework that allows clients like mobile apps or React.js/ Vue.js enabled frontend interfaces to integrate a phone number verification using Sparrow SMS service gateway. In addition, this feature could be used as a sign in or sign up wall during user authentication.
To follow this post ahead, you will need:
- basic knowledge of Python Django (3.2) and Django Rest Framework (3.12.x),
- a Sparrow SMS account (demo account works too. Register here),
- an initial setup of Get Started with Django and Quickstart Django REST Framework,
- and an active NTC or Ncell phone number that can receive text messages.
- (optional - not needed) Google SMS Retriever API for Automatic SMS Verification, without requiring the user to manually type verification codes.
Assumed we have installed the requirements and started running an instance of a Django main project successfully, we can start by creating a new Django app using:
that will create a directory structure as:
Sticking to the dev conventions, we will add more python files to the app later such as
Step 1 — Defining database layout in models.py
The first step is to add some basic imports needed in our
RegexValidator are the built-in validator classes from
django.core module that checks the minimum length of a value and performs
re.search() by a regex validation respectively. Next up we have
models which is the most common and important
db import. Finally the
AbstractUser module allows us to customize the default user groups and auth permissions that comes battery included in
AccountUser is a custom account user model class that entails custom user model attributes like
username, first_name, last_name etc. The custom class
AccountUser subclasses in-built
django.contrib.auth.models from the
imports section above.
AbstractUserprovides the full implementation of the default
Useras an abstract model. - Django 3.2
Next is the class
PhoneOtp that has a custom regex validator starting in line 2. If you look closely the regex only allows phone numbers that start with 98 plus any 8 digits afterwards; a total of 10 digit phone number
9812345678. But there are phone numbers in Nepal that start with 97 too. So you just need to change the regex as per your needs on
phone_regex line 2.
phone_number will hold the 10 digit phone number and validate against the
phone_regex rules specified above it; added to it you have other arguments like
unique to meddle in the database properties.
max_length allows you to set a maximum length of phone number digits including white spaces.
null specifies whether the phone number is allowed to be saved as a void in the database or not.
unique specifies the phone number to be unique in the database once saved unless popped off.
validated is another important model attribute that will store a boolean value; either a True or a False. This is where we set the verification badge status after the users have successfully verified their phone numbers. Each phone number entry in the database are set False
0 by default until the user verifies the phone number in which case the entry is updated to True
1. And in turn, the frontend UI developers can code the appropriate to denote the phone number as verified, checked etc.
otp_code will hold the 6 digits randomly generated number by the
generate_otp function in the
views.py file which in turn will act as the 6 digits One Time Passwords sent to the user's phone numbers by the Sparrow SMS API gateway.
otp_count will hold the integer values of the number of times the OTP is sent to a phone number by the server. This data will be useful to limit the unwanted retries by users for OTP to request or overload the SMS gateway within API level access.
PhoneOtp models from Terminal.
NOTE: This is Part 1 of a multi-part series.
Part 2 is here.