Django OTP login with Fast2SMS Smart OTP (starter kit)

This guide shows you how to add a Django OTP login page to your project with Fast2SMS Smart OTP. Our starter kit is a drop-in Django app called fast2sms_otp. You add it to INSTALLED_APPS, mount its URLs and set two values, and users can log in with a code sent to their mobile by SMS or WhatsApp.

What you build

A login page that works like this:

  1. The user types a mobile number and clicks Send OTP. Fast2SMS creates the code and sends it.
  2. The user types the code and clicks Verify. Fast2SMS checks it, and your app logs the user in.
  3. A Resend code button works after a short wait (30 seconds by default).

The kit uses Smart OTP, our recommended way to send OTPs. An OTP template sends on SMS or WhatsApp, with optional fallback to the other channel, on a priority route. Fast2SMS creates, stores and checks the code, so your app does not keep any OTP itself.

Download the ready-made starter kit (zip)fast2sms-smart-otp-python-django.zip · 24 KBDownload .zip

We tested this kit with Python 3.12.10 and Django 6.1.3 in a fresh project that mounted the app at /otp/, against a local copy of the Fast2SMS API (a mock server, so no real SMS was sent): all 23 client tests and the full 16-step browser test passed.

Before you start

  • A Fast2SMS account with wallet balance. Every OTP you send is charged.
  • For SMS OTP: an approved DLT entity, sender ID and OTP content template in DLT Manager. For WhatsApp OTP: a connected WhatsApp number with an approved authentication (or utility) template.
  • A Django 4.2 or newer project with sessions and CSRF turned on. A project made with django-admin startproject has both. No new Python packages are needed.

Set up Django OTP login in 5 steps

  1. Create a Smart OTP template

    In the panel, open Smart OTP > OTP Template List and click Add OTP Template. On the SMS Channel tab, pick your entity, sender and approved DLT OTP template, then click the variable button that holds the code and click Assign OTP Template. For WhatsApp, use the WhatsApp Channel tab. You can also tick SET FALLBACK TEMPLATE to add the other channel as a fallback.

    Add OTP Template window on the SMS Channel tab with entity, sender and DLT template selected and the variable buttons below the preview
    Pick the entity, sender and DLT template, then choose which variable holds the OTP.
  2. Copy the OTP ID

    Your new template shows as a card in the OTP Template List. Copy its OTP ID with the copy icon. It is 10 characters long, for example a1b2c3d4e5.

    Smart OTP Template list with WhatsApp and SMS template cards, each showing its OTP ID with a copy icon
    Each card shows the OTP ID you put in your .env file.
  3. Copy your API key

    In the left menu under Utility, click API Key. Click View to see the full Authorization Key (the panel asks for an OTP sent to your registered mobile first) and copy it. Check that API Access is switched on.

    API Key page with the masked Authorization Key, View and Reset buttons and the API Access switch turned on
    Copy the Authorization Key. API Access must be on.
  4. Add the app and your keys

    Copy the fast2sms_otp folder next to manage.py. Add "fast2sms_otp" to INSTALLED_APPS in settings.py, and mount the URLs in your project’s urls.py:

    from django.urls import include, path
    
    urlpatterns = [
        # ... your other URLs
        path("otp/", include("fast2sms_otp.urls")),
    ]

    Copy .env.example to .env next to manage.py and set your values (or set them as environment variables):

    FAST2SMS_API_KEY=YOUR_API_KEY
    FAST2SMS_OTP_ID=a1b2c3d4e5
    OTP_RESEND_WAIT_SECONDS=30

    Never commit .env to git; make sure your .gitignore lists it.

  5. Run it and log in

    Create the session table if you have not done it yet, then start the server:

    python manage.py migrate
    python manage.py runserver

    Open http://127.0.0.1:8000/otp/, type your own mobile number and click Send OTP, then type the code and click Verify.

How send, verify and resend work in the Django kit

Step Your app calls Fast2SMS endpoint Charged?
Send client.send(mobile, otp_id) POST /dev/otp/send Yes
Verify client.verify(mobile, code) POST /dev/otp/verify No
Resend client.resend_or_send(mobile, otp_id) POST /dev/otp/resend, falls back to send Yes

The client is fast2sms_otp/fast2sms_smart_otp.py and uses only the standard library. The views are in views.py. To see the kit’s log lines, add a logger named fast2sms to LOGGING in settings.py.

Send

The kit first cleans the number, so +91 98765-43210 becomes 9876543210. Anything that is not a 10-digit Indian mobile starting with 6 to 9 is refused before any API call, so it costs nothing. Then it sends the mobile and your OTP ID. Fast2SMS makes a 6-digit code that is valid for 15 minutes, unless you pass otp_length (4 to 10) or otp_expiry (1 to 10080 minutes).

“OTP sent successfully” means Fast2SMS accepted the request. It does not mean the phone has received it. Delivery shows in Smart OTP > Delivery Report and in the OTP webhook.

Verify

Verify needs only the mobile and the code the user typed, no OTP ID. Fast2SMS checks the latest unverified code for that mobile. Sending a new OTP cancels the older codes, so only the newest one works. The result is one of verified, invalid (wrong code, one try used), expired, max_attempts or not_found.

This is the verify view from views.py. On success it cycles the session key:

r = client().verify(mobile, otp)
if r.ok:
    # Logged in. A new session key stops session fixation.
    # In a real project: find or create the User for this mobile and call django.contrib.auth.login().
    s.cycle_key()
    for k in (PENDING, SENT_AT, NEED_NEW):
        s.pop(k, None)
    s[USER] = mobile
else:
    s[NEED_NEW] = r.reason in ("expired", "max_attempts", "not_found")
    flash(request, "error", VERIFY_MESSAGES.get(r.reason, "Could not check the code: " + r.message))

Resend

Resend sends the same code again and is charged like a new send. It works only within 10 minutes of the last send, and Fast2SMS allows at most 5 sends to one number in those 10 minutes, counting the first. So a user gets up to 4 resends. When there is nothing to resend (never sent, already verified, or the 10 minutes are over), the kit sends a new code instead:

def resend_or_send(self, mobile: str, otp_id: str, **send_options) -> Result:
    """Resend; if there is nothing to resend (none, verified or window over), send a new OTP instead."""
    r = self.resend(mobile)
    if r.reason in ("no_previous", "already_verified", "window_expired"):
        r = self.send(mobile, otp_id, **send_options)
        r.sent_new = True
    return r

The API key goes in the authorization header as the bare key. Do not add Bearer in front: the OTP API refuses it.

"authorization": self.api_key,  # bare key, no "Bearer ", never in the URL

The kit never retries a send or resend on its own, because a retry after a timeout could send, and charge, twice. It retries once, after 1 second, only when the connection could not be opened or Fast2SMS answered 502, 503 or 504 with an error page.

Security notes

Never expose the API key

  • Call Fast2SMS only from your server. Never put the API key in JavaScript, a mobile app or a page the browser can download.
  • Keep the key in .env or environment variables, out of git. If it ever leaks, click Reset on the API Key page; the old key stops working.
  • Turn on API Security and whitelist your server’s public IP, so a stolen key does not work from anywhere else.
  • The kit never writes the OTP or the full key to its logs. Mobiles are logged as 98xxxxxx10.

Rate limits

Every send costs money, so limit who can press Send OTP. There are three layers:

  • The kit’s wait: the Resend button works only after OTP_RESEND_WAIT_SECONDS (30 by default). Clicks before that make no API call.
  • Fast2SMS limits: the SMS Resend / Time Limit in OTP Settings (10 seconds if not set, 0 to 3600) and the fixed cap of 5 sends per number in 10 minutes.
  • Your own limit: add a limit per IP address or a CAPTCHA on the Send button. Bots that try many different numbers are not stopped by per-number limits.

The send, verify and resend views accept POST only and use Django’s CSRF check. Before going live, set DEBUG = False and your own SECRET_KEY.

Verify attempts

Set Max Verify OTP Limit (Per SMS) in Smart OTP > OTP Settings. It can be 1 to 100 and is 10 if you never set it; 3 to 5 suits most login pages. When the limit is reached, the code stops working and the kit shows “Too many wrong tries” with a Send new code button.

OTP Settings page with Max Verify OTP Limit set to 5 and SMS Resend Time Limit set to 30 seconds
Five tries per code and a 30-second wait between sends.
After “Too many wrong tries” or “This code has expired”, give the user a fresh code with client.send(mobile, otp_id). Do not re-send the old code. In the kit, the Send new code button calls client.resend_or_send(mobile, otp_id); for a stricter setup, change it to call send when the last verify ended in max_attempts.

Every send and every resend is charged at your OTP rate; verify is free. A fallback message on the second channel is also charged. See the current rates on the OTP SMS page.

Sending in bulk? For high OTP volumes our team offers discounted rates. Talk to our team or see OTP pricing.

Use HTTPS on the live site. After a correct code the kit starts a new session (or sign-in cookie), which stops session fixation, and every form carries a CSRF token.

OTP over DLT SMS: the second Django kit

Smart OTP is the easier choice. If you would rather send OTPs through your own approved DLT OTP template with the DLT SMS API, use our “OTP over DLT” kit for the same stack. It has the same login page, but the work is split differently:

  • Your app makes the code with a secure random generator and keeps only an HMAC-SHA256 hash of it, with the expiry time and a try counter. The code is never stored, logged or shown.
  • Fast2SMS only delivers the SMS. In dlt mode the kit calls /dev/bulkV2 with route=dlt, your sender ID and the template’s Message ID. In dlt_manual mode it calls /dev/custom with route=dlt_manual, your Entity ID, the 19-digit DLT Template ID and the full text.
  • Verify happens in your app with a constant-time compare. No API call, no charge.
  • Resend sends a new code and the old one stops working.

The two calls are otp_service().send_otp(mobile) and otp_service().verify_otp(mobile, code). These are the DLT settings in its .env, next to the API key and an OTP_HASH_SECRET (a long random string; the app will not start without it):

# How to send: dlt (DLT SMS, default) or dlt_manual (DLT Manual).
OTP_SEND_MODE=dlt

# Your approved DLT sender ID, exactly as in DLT Manager (case matters).
FAST2SMS_SENDER_ID=FSTSMS

# DLT SMS: the "Message ID" from the template card in DLT Manager. NOT the 19-digit DLT Template ID.
FAST2SMS_DLT_MESSAGE_ID=111111
FAST2SMS_DLT_VARIABLES={otp}

# DLT Manual: the full approved DLT text, with {otp} where the code goes.
FAST2SMS_DLT_MANUAL_TEXT=Your OTP is {otp} for Login. -Demo
FAST2SMS_DLT_ENTITY_ID=1101234567890123456
FAST2SMS_DLT_TEMPLATE_ID=1107123456789012345
Rule Default Setting
Code length 6 digits (4 to 6 allowed) OTP_LENGTH
Code expires after 5 minutes OTP_EXPIRY_MINUTES
Wrong tries per code 5, then the code is deleted OTP_MAX_ATTEMPTS
Wait between sends to one number 30 seconds OTP_RESEND_WAIT_SECONDS
Sends per number per hour 5 OTP_MAX_SENDS_PER_HOUR
Use the Message ID from the template card in DLT Manager, not the 19-digit DLT Template ID. The sender ID is case-sensitive. In DLT Manual mode, Fast2SMS does not check your text against the template: if it does not match exactly, the SMS fails at the operator and is not refunded.

OTP records live in Django’s cache through a small CacheStore in views.py. The default LocMemCache works for one process only; set a shared cache such as Redis if you run several. This kit was run with Django 6.1.3 against the mock server in both modes: 20 of 20 tests and the 11-step browser test passed each time.

Download the OTP over DLT starter kit (zip)fast2sms-otp-dlt-python-django.zip · 26 KBDownload .zip

Common problems and fixes

What you see Why Fix
“SMS login is not set up correctly” and Invalid authorization key in the log Wrong key, or Bearer in front of it Copy the key again from API Key and send it bare.
Authorization Key Disabled (413) in the log API Access is off Switch on API Access on the API Key page.
IP is blacklisted (414) in the log API Security is on and your server IP is not listed Add the server’s public IP in API Security.
“Could not send the code: Invalid OTP ID” The OTP ID is wrong, deleted or from another account Copy it from OTP Template List, in the same account as the key.
“Please wait N seconds before asking for a new code.” Fast2SMS cooldown for this number Wait, or change the time in OTP Settings.
“Could not send the code: Insufficient wallet balance” Low balance Recharge with Add Amount.
“Maximum resend limit (5 times) reached” 5 sends to this number in 10 minutes Wait and try later.
“Could not reach the SMS service.” Network problem, or Fast2SMS was busy Try again in a minute.

Test without sending SMS

Each kit has a fake Fast2SMS server in its mock folder (it needs Python 3). It never sends an SMS, and with it the correct code is always 123456. Start it, then run the tests in a second terminal:

python mock/mock_fast2sms.py
FAST2SMS_BASE_URL=http://127.0.0.1:4010 python -m unittest discover -s tests -v

To click through the login page with the mock, set FAST2SMS_API_KEY=TEST_KEY_OK and FAST2SMS_BASE_URL=http://127.0.0.1:4010 in .env. Remove FAST2SMS_BASE_URL before you go live.

Frequently asked questions

Does the kit log the user in with django.contrib.auth?

Not by itself. After a correct code it stores the verified mobile in the session. In your project, find or create the User for that mobile at that point and call django.contrib.auth.login().

Can I use it with Django REST Framework?

Yes. The client in fast2sms_smart_otp.py is plain Python. Call send, verify and resend_or_send from your API views and keep the same rate limits.

Is the starter kit free?

Yes. The kit is free under the MIT license. You pay only for the OTPs you send from your Fast2SMS wallet.

Can the same code send the OTP on WhatsApp?

Yes. The code only knows the OTP ID. If that OTP ID uses a WhatsApp authentication template, or has a WhatsApp fallback, Fast2SMS handles the channel and your code stays the same.

The page says the code was sent, but no SMS arrived. Why?

“OTP sent successfully” means Fast2SMS accepted the request. Check the status in Smart OTP > Delivery Report. If the message failed and you set a fallback, the same OTP goes out once on the other channel.

How many times can a user resend the OTP?

Up to 4 times: Fast2SMS allows 5 sends of one OTP ID to a number in 10 minutes, counting the first. The wait between sends comes from your OTP Settings and the kit’s 30-second Resend wait.