WhatsApp for your developers and your marketing team
Integrate the WhatsApp Business API in an afternoon, or run broadcasts and conversations without writing code. Approved templates, two-way chat in the 24-hour window, read receipts, and green-tick onboarding — one account for the people who build and the people who send.
What you can build with this
Approved template messages
Reach an opted-in list
Conversations, not just sends
Send your first WhatsApp message
One endpoint sends every message type. For a template, name it, set the language, and pass the variables; the response returns a WhatsApp message ID you reconcile against delivery and read receipts on your webhook.
Inbound replies and button taps arrive on the same webhook, so a bot or an agent can pick up the conversation inside the 24-hour window. Media, quick-reply buttons, and list messages are all fields on the same call — there is no separate SDK per message type.
When WhatsApp can't reach a customer, fall back to SMS on the same number set, so a critical message still lands. Errors return explicit codes — an unapproved template, a closed window, a number that hasn't opted in — so you handle each case rather than parsing prose.
Message status flows back as it changes — accepted, sent, delivered, and read where the user allows it — so you show a customer a real status and reconcile a campaign by message ID rather than assuming a send succeeded. A failed send carries a reason, so a number that has blocked you or never opted in is something you stop retrying.
The same webhook carries inbound messages, button taps, and list selections, which is what lets you build a flow rather than a broadcast: a customer taps a quick-reply, your handler reads it and responds within the window, and the conversation continues without a template until it goes quiet. Media — an image, a PDF invoice, a location — is a field on the message, not a separate integration.
curl https://api.smsapi.in/v1/whatsapp/messages \
-H "Authorization: Bearer $SMSAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+919876543210",
"type": "template",
"template": {
"name": "order_shipped",
"language": "en",
"components": [
{ "type": "body",
"parameters": [{ "type": "text", "text": "AWB123456" }] }
]
}
}'
# -> { "message_id": "wamid.HBg...", "status": "accepted" }How WhatsApp Business works for your team
- 1
Get your number verified and your green tick
We onboard a WhatsApp Business number, verify your business with Meta, and apply for the green official-business badge so customers know the chat is really you.
- 2
We get your templates approved
Message templates go to Meta for review by category — utility, authentication, or marketing. We draft and submit them so they read well and pass review the first time, rather than bouncing back for wording.
- 3
Collect opt-in, then broadcast
Send to customers who have opted in, segment the list by what they bought or where they are, and broadcast a template to thousands at once. Delivery and read receipts come back per recipient.
- 4
Reply inside the 24-hour window
When a customer replies, a 24-hour service window opens where your team — or a bot you connect — can chat freely without a template, then close the loop with another template if it runs long.
What’s included
All three categories
Utility, authentication, and marketing templates with variables, buttons, and media headers.
Images, PDFs and buttons
Send documents, images, quick-reply and call-to-action buttons, and list messages.
Sent, delivered, read
Per-message status on your webhook, including read receipts where the user allows them.
Inbound to your webhook
Customer replies and button taps arrive on your webhook for a bot or an agent to handle.
Official business account
Verified business display name and the green badge, subject to Meta's approval.
Keep or get a number
Use an existing business number or provision a new one for WhatsApp.
Quality-rating aware
Monitor your number's quality rating and messaging limits so a broadcast doesn't get capped.
SMS fallback
Fall back to SMS for a customer a WhatsApp message can't reach.
Built for compliant messaging
WhatsApp is governed by Meta's business policies rather than the DLT framework that covers SMS. The controls are opt-in and template approval: you may message a customer who has opted in to hear from you, using templates Meta has reviewed and approved by category — utility, authentication, or marketing.
We capture and keep the opt-in record, honour opt-outs, and monitor your number's quality rating, because repeated blocks or spam reports lower the rating and tighten the number's daily messaging limits. Staying inside the rules is what keeps a broadcast from being capped. The 24-hour service window is part of this design: free-form replies are allowed only while a customer conversation is open.
Where you also send SMS, that traffic still follows TRAI and DLT separately, with its own principal entity and templates. We run both from one account, so consent and opt-out stay consistent across WhatsApp and SMS. Our DLT guide covers the SMS side.
Two things protect a WhatsApp number in practice: sending what customers expect, and keeping marketing on opted-in lists. Mass-messaging people who didn't ask leads to blocks and spam reports, the quality rating falls, and Meta lowers how many people the number can reach in a day. Treating opt-in as the foundation rather than an afterthought is what keeps a broadcast from being throttled at the moment it matters.
Frequently asked
Why do messages need templates, and how long does approval take?
Outside a 24-hour conversation, WhatsApp only allows pre-approved templates, which is how Meta keeps the channel low-spam. You write the template, we submit it by category, and Meta typically reviews within a day. We draft them to pass the first time so you aren't waiting on re-submissions.
What is the 24-hour window?
When a customer messages you, a 24-hour customer-service window opens in which you can send free-form replies — text, media, buttons — without a template. If you need to reach them after it closes, you send a template again. This is what makes WhatsApp support conversations and not just notifications.
Do I need opt-in to message customers?
Yes. You must have the customer's opt-in to receive WhatsApp messages from you, captured on your website, app, or another channel. We keep the consent record, and opt-outs are honoured. Sending without opt-in risks your number's quality rating and, eventually, its limits.
How is WhatsApp priced, and does DLT apply?
WhatsApp is priced per conversation, with categories — utility, authentication, marketing — charged at different rates, plus any platform fee, with GST shown separately. DLT is an SMS framework and does not apply to WhatsApp; the equivalent control here is Meta's template approval and your opt-in. See the pricing page.
Can I use my existing business number?
Usually, yes. A number that isn't already tied to a personal WhatsApp account can be onboarded to the Business API, so you keep the number customers already know. If it is in use on the consumer app, you migrate it instead — we walk through the steps and the short verification involved so you don't lose continuity.
Can I get the green tick?
The green official-business badge is granted by Meta based on your business's notability and verification, not something any provider can guarantee. We handle business verification and submit the application; whether the badge is granted is Meta's decision. A verified business display name is available regardless.
How is this different from RCS?
WhatsApp runs on Meta's network and needs the app installed; RCS runs through the mobile operator in the native messages app. Many businesses use both — WhatsApp for its reach and conversation model, RCS to upgrade plain SMS on Android. We support both from one account.
Transparent pricing, with GST broken out
6-month packs: OTC + platform fee + message wallet. Base price and 18% GST are shown separately, in rupees.