The agent-ready communication platform for WhatsApp.
Verify users with one-time passcodes and send transactional messages through one REST API. No SDKs, no SMS approvals—codes arrive in a chat your users already open.
JSON in, JSON out No SDK required ~1s delivery Live the same day
$ curl -X POST https://api.yourdomain.com/otp/send \
-H "Content-Type: application/json" \
-d '{
"authorization": "APP_TOKEN",
"recipient": "919876543210",
"channel": "whatsapp"
}'
{ "success": true, "message": "Message queued for sending" }
Your verification code is
849201
Valid for 5 minutes. Don’t share this code with anyone.
10:42 ✓✓
How it works
Your backend or agent makes two calls. Falcon handles generation, delivery, expiry and attempt limits in between.
-
01
Request. Your agent or backend posts the app token and the user’s number to
/otp/send. Falcon queues the message and returns immediately. -
02
Delivery. The six-digit code arrives in the user’s existing WhatsApp chat in about a second. Nothing to install.
-
03
Entry. The user types the code into your app. Falcon is not in the browser or the client.
-
04
Validation. Your agent or backend posts the code to
/otp/validate. Falcon checks expiry and attempts, then answers pass or fail.
Specification
| Property | Value |
|---|---|
| Channel | |
| Delivery time | About 1 second |
| Passcode | 6 digits |
| Passcode lifetime | 5 minutes |
| Resend cooldown | 60 seconds per recipient |
| Verification attempts | 3 per code, then the code is voided |
| Passcode storage | Hashed, in memory with a TTL. Never written to a database. |
| Transactional messages | Up to 500 characters |
| Transport | HTTPS, JSON request and response |
| Authentication | Bearer token |
| Allowance | Yearly message allowance, set by your plan |
Life of a passcode
A code exists for five minutes at most, in one place, and cannot be guessed by retrying.
-
01Generated
Six random digits, created when the request arrives.
-
02Hashed
Stored as a hash in memory with a five-minute TTL.
-
03Delivered
Sent over WhatsApp, which is end-to-end encrypted.
-
04Checked
Three wrong attempts and the code is voided.
-
05Gone
Expired or used, the entry is removed. Nothing is logged in plaintext.
A 60-second cooldown per recipient also stops anyone from flooding a number with codes.
Compared with SMS
Texts depend on carrier routes, regulatory templates and signal strength. WhatsApp travels over the data connection users already have.
| Falcon on WhatsApp | Traditional SMS | |
|---|---|---|
| Delivery path | User’s data connection | Carrier routes |
| Approvals | None to wait for | DLT registration, sender IDs, templates |
| Encryption | End-to-end | Plain text, open to SIM-swap |
| Time to deliver | About a second | Varies by network |
| Cost per code | Lower | Higher, especially international |
API reference
Plain HTTPS, JSON in, JSON out, with no SDK required. If your agent framework can call a tool, it can call Falcon.
| Method | Path | Description |
|---|---|---|
| POST | /otp/send | Generate a passcode and deliver it on WhatsApp. |
| POST | /otp/validate | Verify a passcode entered by the user. |
| POST | /message/send | Send a transactional message of up to 500 characters. |
| GET | /health | Gateway and Redis status, for monitoring. |
Request fields
| Field | Used by | Description |
|---|---|---|
| Authorization | All |
Header
Bearer <token> or
body authorization.
|
| recipient | All | Number with country code, digits only. |
| channel | /otp/send |
"whatsapp"
|
| passcode | /otp/validate | The numeric code to check (4-8 digits). |
| message | /message/send | Message body, 500 characters max. |
Status codes & agent hints
| Code | Meaning |
|---|---|
| 200 |
Passcode authenticated. Includes
agent_hint.
|
| 202 | Message accepted and queued for WhatsApp delivery. |
| 400 | Invalid passcode or malformed request parameters. |
| 401 | Unauthorized: token missing or invalid. |
| 403 | Application/agent token is inactive or expired. |
| 429 |
Cooldown active (retry_after) or quota limit reached.
|
Who it’s for
One platform, three reasons to like it. Here is what each person around your product gets.
Two calls and you’re live
- Plain JSON over HTTPS with a Bearer token. No SDK.
- OpenAPI spec and ready-made tool definitions for Claude and OpenAI.
-
Clear status codes,
with
retry_afteron 429 andagent_hinton success so agents know the next step.
Nothing to wait on
- No DLT registration or sender approvals. Live the same day you get your token.
- OTPs and transactional alerts from one API and one allowance.
- Simple yearly pricing in INR, with no per-route surprises.
A code that just arrives
- Lands in the WhatsApp chat they already use. Nothing to install.
- Arrives in about a second over their data connection, with no carrier signal needed.
- End-to-end encrypted, and the code expires after five minutes.
Pricing
Simple yearly plans. Pay once, then send up to your limit. Every plan includes the full API.
Starter
Right-sized for a new product or a first rollout. Put WhatsApp verification live without over-committing.
- OTPs and transactional messages
- Your own API token
- Live the same day you get your token
Growth
For products with steady sign-ups and logins. Twice the headroom, so a busy month never stalls verification.
- Double the message headroom
- OTPs and transactional messages
- Your own API token
Enterprise
For high-volume teams and multi-product companies. Tell us what you send and we’ll size the quota around it.
- Quota sized to your traffic
- Separate allowance for each product
- Talk to us about your setup
Prices in INR, billed yearly. OTPs and transactional messages both count toward the limit.
Included in every plan
- WhatsApp delivery in about a second
- OTP generation and validation
- Transactional messages up to 500 characters
- Cooldown, expiry and attempt limits
- Health endpoint for your monitoring
- No DLT registration or sender approvals
Questions
Can an AI agent use Falcon directly?
Yes. Every endpoint is a single JSON POST with a token, so you can
wrap it as a tool in any agent framework. Keep the token on your
server rather than in the model’s context, and start from the
ready-made tool definitions at /agent/tools.
Do users need to install anything?
No. The code arrives in the WhatsApp app they already use. There are no extra apps or authenticators to set up.
Do I need DLT registration or sender approvals?
No. Those requirements belong to SMS. Falcon sends over WhatsApp, so you can get a token and send a first code the same day.
How are codes protected?
Each code expires after five minutes, is held as a hash in memory, and is voided after three wrong attempts. A 60-second cooldown limits repeat requests to the same number.
Can it send messages other than OTPs?
Yes.
POST /message/send
delivers order confirmations, alerts and account updates of up to
500 characters.
What happens if I reach my message limit?
Falcon returns a 429 so your app can handle it cleanly. Get in touch and we’ll raise your limit.
What counts toward my message limit?
Each OTP and each transactional message counts as one message. Usage is counted against your plan’s yearly allowance.