Auth + WhatsApp, built for India. One platform.
Login with WhatsApp, auto-read SMS & WhatsApp OTP and multi-channel routing — plus utility-lane bulk WhatsApp on the same WABA, dashboard and INR invoice. DLT-aligned, sub-3s delivery, no aggregator middlemen.
Two products. One API.
Auth and messaging share the same key, the same dashboard, and the same INR invoice. Pick the track you need first — most teams end up running both.
One-tap login
Single-call API. Returns a session token; no manual OTP screen if WhatsApp is installed.
await quickauth.auth({
channel: 'whatsapp',
phone: '+91 98765 43210',
})Smart Auth OTP
Auto-read SMS Retriever on Android, one-time-code on iOS, and WhatsApp system OTP-prompt — no copy-paste.
await quickauth.otp.send({
phone: '+91 98765 43210',
mode: 'smart', // SMS + WhatsApp fallback
})WhatsApp login
OAuth-style sign-in inside WhatsApp. User confirms, your app gets a signed callback with the phone number.
quickauth.auth.whatsapp({
redirect: 'https://app.example.com/cb',
})Social logins
Google and Apple sign-in wired into the same session model. Drop-in alongside phone auth.
quickauth.auth.social({
provider: 'google', // or 'apple'
})Bulk WhatsApp API
Send 100 to 100k recipients on one call. Async campaign id; live progress + delivery callbacks.
await quickauth.campaign.send({
template: 'order_confirmation',
recipients: csvFile,
})Utility-first routing
Order updates, OTPs and payment alerts auto-routed through Meta’s utility lane — higher delivery, lower cost.
quickauth.send({
template: 'payment_alert',
// category auto-resolved to UTILITY
})WABA ban prevention
Template categorization, sender-quality monitoring, and adaptive rate-shaping keep your WABA out of trouble.
quickauth.health.check()
// → { quality: 'HIGH', tier: 'TIER_100K' }DLT-compliant delivery
TRAI-registered DLT templates and sender IDs handled by our team. You ship; we keep the registry in sync.
quickauth.dlt.templates.list()
// → [{ name, urn, status: 'APPROVED' }, ...]Login + OTP that Indian users actually finish.
A WhatsApp OAuth login button, auto-read OTP for Android and iOS, and multi-channel routing across SMS, WhatsApp and voice — wired into a single auth API in private beta.
Login with WhatsApp
A Continue-with-WhatsApp button replaces password forms and 6-digit OTP screens — 1-tap auth with materially lower drop-off than SMS OTP.
Auto-read OTP
SMS and WhatsApp OTPs auto-fill into your Android and iOS app — no copy-paste, no app-switch. Built on the SMS Retriever API, iOS auto-fill, and WhatsApp's system OTP-hint format.
Multi-channel routing
Pick SMS, WhatsApp or voice automatically based on reachability and cost — with smart fallback the moment a channel fails or stalls.
Three steps. Onboarded by humans.
No self-serve signup yet — we hand-onboard each business so your first login flow and your first campaign both ship clean.
Apply for early access
Tell us your volume and use case. Aarav reviews every application personally and gets back within a day.
We handle compliance
DLT registration, Meta Business verification and a template categorization workshop — done for you, not by you.
Ship login + campaigns
Wire the auth SDK, whitelist templates, fire campaigns — both products live on one dashboard.
Marketing reach, utility deliverability.
Send to your full customer list — not just opted-in subscribers. We route bulk business messages through Meta's utility template category wherever the content qualifies, lifting delivery rates and cutting per-message cost without touching policy. Same platform that runs your authentication — utility-first template routing for both.
Utility-lane routing
Order updates, payment alerts, reminders — categorized into the utility template lane for higher delivery and lower cost.
Template categorization workshop
Our team rewrites your template copy so Meta classifies it correctly the first time — fewer rejections, faster approvals.
Audience segmentation
Filter your customer list by behaviour, location, purchase history — send the right utility message to the right cohort.
Rate shaping & scheduling
Time-zone aware sends and adaptive throughput help keep the WABA healthy during bulk pushes — no flat-line throttling, fewer Quality Rating drops.
Block-resistant sending
Per-template pacing and Quality Rating monitoring help keep your sender healthy through high-volume sends — materially lower WABA-suspension and number-ban risk.
SMS safety net
If WhatsApp delivery fails, the same payload retries on a DLT-registered SMS route in seconds — minimising drop-offs.
Auth and bulk messaging — routed correctly.
Passwordless login
Replace password forms with Login with WhatsApp (one-tap) or phone+OTP with auto-read on Android & iOS. +34% signup conversion on Indian numbers.
Order & delivery updates
Bulk shipping, dispatch and out-for-delivery alerts via the utility template lane — high open, near-zero rejection.
Payment & transaction alerts
RBI-aligned payment receipts, EMI reminders and refund notifications. Utility-categorized for sub-3s delivery.
Quick-commerce login
One-tap Login with WhatsApp on the cart screen with auto-read OTP fallback for cold SIMs. Sub-3s verify, no copy-paste.
Fintech KYC & verify
Multi-channel verification across SMS, WhatsApp and voice. SMS-pumping protection, IP rate limits and DLT-aligned OTP templates by default.
Step-up MFA
Re-verify users for sensitive actions — refunds, profile edits, withdrawals — via SMS OTP, WhatsApp OTP or a Login-with-WhatsApp tap-to-confirm.
Watch every OTP, in real time.
Conversion funnels, per-operator delivery, fraud alerts — without spreadsheets.
From signup to verified user — in one cup of chai.
The HTTP API mirrors common Verify-style signatures — one POST, webhooks for status, retries and fallback handled server-side. Official SDKs (Node, Python, PHP, Flutter) ship to early-access customers through late 2026.
Plans that start free, scale with you.
Free tiers on both products. INR billing, no FX surprises. Pick the side that matches your stack — most teams end up on both.
Built for production-scale India deployments.
QuickAuth internal benchmarks · tested on 500k+ messages · May 2025
Talk to onboarding.
Onboarding is invitation-only. We review every applicant, set up DLT, WABA and Meta verification, and quote one INR volume agreement that rolls up auth and bulk WhatsApp — within 24 hours.
Real human, same day.
Skip the form-wall. Aarav personally reviews your application, runs the auth-flow + template-categorization workshop, and gets your DLT, WABA and Meta setup moving — usually within a few hours.
- Login with WhatsApp + auto-read OTP wired on day one
- Template categorization workshop included
- Free DLT, WABA & Meta Business verification handled
- One INR volume agreement — auth + bulk on one invoice
Questions, answered.
How does QuickAuth get higher delivery rates than other WhatsApp platforms in India?+
Most platforms push every business message through Meta's marketing template category — which carries higher cost, marketing-opt-in friction, and aggressive deliverability throttling. We use intelligent template categorization to route order updates, payment alerts, reminders and account notifications through the utility category whenever the content qualifies. Same Meta WhatsApp Cloud API, same policies — just routed into the lane the message actually belongs in. Result: higher delivery, fewer rejections, no marketing-opt-in friction.
Why don't you publish pricing?+
Real costs in India depend on your volume, channel mix, template categorization breakdown and fallback patterns. A static price list would either mislead you or quote you well above the deal we can actually offer. Aarav puts together a custom INR quote within 24 hours of your application.
What is DLT registration and do I have to do it myself?+
DLT (Distributed Ledger Technology) is the TRAI-mandated registry every Indian SMS sender, header and template has to be enrolled in. You don't have to handle it — our team takes care of DLT registration, sender ID and template approvals end-to-end, usually within 24 hours. Included with onboarding, no extra charge.
Does WhatsApp OTP need DLT registration in India?+
No. WhatsApp Business API messages run on Meta's platform, so they're outside TRAI's DLT scope — only SMS needs DLT. That makes WhatsApp OTP a fast way to start sending verifications without waiting for sender-ID approval. We still recommend SMS as a fallback channel for unreachable numbers.
What is "Login with WhatsApp" and how is it different from OTP?+
Login with WhatsApp is a one-tap auth flow. The user clicks "Continue with WhatsApp", receives a tap-to-verify message in their WhatsApp inbox, taps to confirm, and gets signed in via an SDK callback — no code typing, no copy-paste. OTP-by-WhatsApp still sends a numeric code the user reads and types back. Both sit on the same Meta Cloud API surface; teams typically use Login-with-WhatsApp for primary signup/login (lower drop-off, especially on mobile) and OTP for step-up MFA where a typed code is desirable.
Does QuickAuth support auto-read OTP on Android and iOS?+
Yes. On Android we use the SMS Retriever API (app-hash appended to the OTP message; no SMS-read permission needed). On iOS we set UITextContentTypeOneTimeCode so the keyboard auto-suggests the code from the SMS. For WhatsApp OTPs we use the message-format hint that triggers Android's system OTP-autofill prompt. Reduces friction at the verification step — fewer drop-offs between code-sent and code-entered.
Can I use the same QuickAuth account for both authentication and bulk WhatsApp?+
Yes — that’s the point. QuickAuth runs auth (Login with WhatsApp, OTP, multi-channel routing) and bulk WhatsApp business messaging (utility, marketing) on the same WABA, the same dashboard and the same template-categorization pipeline. Deliverability monitoring, template approvals and INR billing roll up across both — instead of stitching an OTP vendor, a marketing tool and a WhatsApp BSP into one stack.
How do you prevent SMS-pumping fraud?+
Four overlapping layers. (1) suspicious-prefix scoring — a maintained block-list of MNC and country prefixes commonly used for artificial traffic. (2) velocity and ratio heuristics — abnormal request-to-verify ratios on a number range get throttled. (3) per-IP and per-device quotas with graceful back-off. (4) optional device fingerprinting at the request step. The bulk of pumping attempts get blocked at the request step, before any OTP fires and any cost is incurred.
Is the QuickAuth SDK ready?+
The platform is in production today, but the developer experience is dashboard-first. API access is in private beta — we roll it out to early customers as their volume justifies it. The official SDKs (Node, Python, PHP, Flutter) are in active development and ship to early-access customers through late 2026. Most launch customers run end-to-end from the dashboard for now.
Where is user data stored?+
Mumbai (ap-south-1). Phone numbers are hashed; OTPs are wiped 5 minutes after verification. SOC 2 Type II and DPDP Act 2023 compliant.
One API for authentication and WhatsApp messaging.
Free tier included. No credit card required. Live in minutes.