Verify every phone number. Send zero OTPs.
Your user sends one short text. We confirm it came from their SIM, carries the right code and hit the right line, then a signed webhook reaches your server. Usually within seconds.
- No DLT templates
- No SMS delivery cost
- HMAC-signed webhooks
+91 90000 00001
VerifyNumber
Today 10:42
Delivered
Number verified
+91 98765 43210 · 2.4 s
Webhook 200 OK
verification.verified
ref: signup-8812
sig: t=1795…,v1=845b…
- SMS delivery cost
- ₹0
- SMS delivery cost
- free, forever
- 100/day
- free, forever
- API calls to integrate
- 2
- API calls to integrate
- per verification on Pro
- < 1 paise
- per verification on Pro
How it works
We flip the OTP. The network does the proving.
Instead of sending a code and hoping it arrives, your user sends one to us, and the mobile operator vouches for who sent it.
- 01
Start a verification
One API call with your user's number. You get back a receiving number and a short code.
- 02
User sends one SMS
A tap on the sms: link opens their messaging app with everything pre-filled.
- 03
Gateway receives it
Our SIM gateways capture the text and forward it to our servers within seconds.
- 04
You get a signed webhook
Sender, code, line and expiry all match, so we mark it verified and notify your server.
Developer first
Live in an afternoon.
Create a verification, show the user what to send, and receive a signed webhook. No SDK required, no templates to approve.
Idempotent and retried
Webhooks retry with exponential backoff for up to 12 attempts, and every attempt is logged.
Signed with HMAC-SHA256
Check X-VerifyNumber-Signature in a few lines of Node, Python or Go.
Test in the dashboard
Run a real verification against your own phone before writing any code.
curl -X POST https://api.verifynumber.in/v1/verifications \
-H "Authorization: Bearer $VERIFYNUMBER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"user_phone": "+919876543210", "reference": "signup-8812"}'Why VerifyNumber
Better than OTP on every axis that matters.
Proof of possession, not just delivery
An OTP proves a message arrived somewhere. An inbound SMS proves the SIM is in your user's hand, because the mobile network itself identifies the sender.
Zero SMS delivery cost
You never send a message: no per-SMS carrier fees, no sender IDs, no DLT templates.
Phishing-resistant
There is no secret code for a fraudster to talk your user into reading out.
Fast, every time
No delivery queues or operator delays. Verification usually completes seconds after the user taps send.
Two endpoints, done
Create, then receive a webhook. HMAC-SHA256 signatures, idempotent processing and automatic retries.
Full visibility
Every verification, inbound message, webhook attempt and response code is in your dashboard, with one-click resend.
Comparison
OTP vs. VerifyNumber
| SMS OTP | VerifyNumber | |
|---|---|---|
| Who sends the SMS | You (paid, per message) | Your user (bundled in their plan) |
| DLT registration & templates | Required | Not needed |
| Proves SIM possession | No: proves delivery only | Yes: network-verified sender |
| Vulnerable to OTP phishing | Yes | No code to share |
| Fails on delayed or blocked SMS | Often | No inbound SMS to delay |
| Integration | Templates, sender IDs, retries | Two API calls |
Use cases
Trusted numbers for every kind of product.
Fintech & lending
Confirm the borrower controls the number linked to their account before disbursal.
Marketplaces
Verify sellers and buyers to cut fake listings and chargeback fraud.
Gig & delivery apps
Onboard riders and partners quickly, even where OTPs fail on patchy networks.
Gaming & communities
Stop multi-accounting and bot sign-ups at the source.
Healthcare & education
Reach the right parent, patient or student before sharing sensitive updates.
Account recovery
Let users prove they own a number when they've lost access to email.
Pricing
Start free. Scale for ₹499.
100 verifications a day on us. When you grow, Pro covers 50,000 a month: less than 1 paise per verification.
Free
Everything you need to build, test and launch.
100 verifications / day
- 100 verifications every day
- Full REST API & signed webhooks
- Shared receiving numbers
- Dashboard, logs & delivery history
- Community support
Pro
Most popularFor products verifying users at real scale.
50,000 verifications / month
Less than 1 paise per verification
- 50,000 verifications every month
- Priority routing on receiving numbers
- Unlimited API keys
- Webhook retries with full attempt log
- Email support
Enterprise
Dedicated numbers, SLAs and custom terms.
Unlimited volume
- Dedicated receiving numbers
- Custom volume & pricing
- Uptime SLA
- Custom data retention & DPA
- Priority support & onboarding
FAQ
Questions, answered.
Does my user pay for the SMS?
They send a normal text from their own plan. On most Indian prepaid and postpaid plans SMS is bundled, so there is usually no extra cost to them.
What do I get for free?
100 verifications every day, with the full API, webhooks and dashboard. Upgrade to Pro (₹499/month for 50,000 verifications, under 1 paise each) when you need more.
How fast is verification?
Typically a few seconds after the user hits send. You get a webhook immediately, or you can poll GET /v1/verifications/{id}.
What if the user sends the wrong code or from another number?
Nothing is verified. The message has to come from the registered number, contain the exact code, and reach the assigned receiving number before it expires (10 minutes by default).
Do you store message contents?
Only what's needed to prove the match, for a limited retention period. See our privacy policy for details.
Ship number verification today.
Create an account, grab an API key and verify your first number in minutes. Free up to 100 a day.