Built on the official WhatsApp Business Platform

Send WhatsApp like you send email.

Your order updates, booking reminders and invoices go to customers on WhatsApp — from your own business number, with Meta's rules handled for you. For your developers, it's one API call.

Get started See how it works

For teams in the UAE and across the Gulf · English and Arabic · No markup on Meta's prices · No setup fee

Acme Servicestypingvia walpio · business account

Hi! Has my order shipped yet?

09:12

Window open — sent as plain text

Yes — it's out for delivery and arrives today between 2–4 PM. You'll get live tracking updates. 📦

09:12

Next day

Window closed — sent as your approved template

Your order has been delivered — thanks for shopping with us! Reply here if anything isn't right.

11:48

POST /v1/messages200 OK

Official Meta Cloud APIYour own number & accountNo markup — Meta bills you directlyArabic & English templates24-hour window: handledAES-256 encrypted credentials

Examples

What teams send on WhatsApp.

The updates your systems already produce, in English or Arabic. When a customer hasn't written to you in the last 24 hours, walpio sends them as the approved templates you choose.

Field service

Technician on the way

Ahmed is on his way and should reach you by 3:30 pm. Reply here if you need a different time.

Billing

Invoice due, in Arabic

فاتورتك رقم INV-1042 بقيمة 350 درهمًا مستحقة في 30 سبتمبر. للاستفسار، يُرجى الرد على هذه الرسالة.

Retail

Order shipped

Good news, Sara: order #1042 has shipped and should arrive on Thursday.

How it works

Live on WhatsApp in three steps.

No apps to install, no platform to migrate to. walpio operates your WhatsApp Business number — you stay the owner of everything.

Connect your account

Bring your own Meta WhatsApp Business account. Your number, your display name, your billing relationship with Meta — you keep full ownership, always.

We set you up

We connect your number, submit your message templates for Meta's review and hand you an API key. Onboarding is done with you, not dumped on you.

Send with one call

POST a message. walpio picks the compliant route, sends it and records every status Meta reports — sent, delivered, read, failed — in your message log and, if you want, posts it to your own URL.

The hard part, handled

The 24-hour rule, handled.

WhatsApp only allows free-form messages within 24 hours of a customer's last message. Outside that window, only templates Meta has approved can be sent — get it wrong and the message fails, often only after your code thinks it was sent.

walpio checks the window on every single send. Inside it, your text goes out as-is. Outside it, walpio sends an approved template: the one you name, or — with a text rule — the template that matches the wording your systems already send, with the values filled in. If nothing matches, the send is refused with a clear reason instead of disappearing.

Window state tracked per customer, per number
Text rules turn your own wording into the right approved template
A clear refusal when a message can't be sent — never a silent drop

How this compares with calling Meta's API yourself, and with Meta's Direct Send: Why walpio.

What you get

The hard parts of WhatsApp, handled.

What walpio sends today: text messages and your approved templates (a template can carry a media header and buttons). Customers' replies reach you as text; a photo or file they send arrives as its caption or a placeholder, not the file itself.

Bring your own Meta

Your WhatsApp Business account stays yours — number, display name, Meta billing and all. walpio operates it; you own it. If you leave, your number and templates stay with you, and we export your walpio data on request.

Delivery tracking

Sent, delivered, read, failed — every status Meta reports is recorded per message. See it in your message log, read it with GET /v1/messages/{id}, or have walpio post it to your own URL.

Familiar request shape

Text and template sends follow the Cloud API's JSON for those two types, so the body will look familiar. It is not a drop-in swap for code that calls Meta directly: the endpoint, the key, the answer and the errors are walpio's own.

Security by default

Meta credentials encrypted at rest with AES-256-GCM. Meta's webhooks verified by signature on every event, and our callbacks to you are signed too. API keys stored only as hashes — shown once, revocable any time.

Isolated workspaces

Every business gets its own workspace — API keys that belong to it alone, its own send-rate limit, and every request scoped to its own data.

Built to operate

A public health check, a message log, and errors with a machine code and a retryable flag. Send with an Idempotency-Key and a retry never messages a customer twice.

Your team's view

The dashboard your team uses every day, and the board walpio's operators watch. These are screens from a demo workspace: the customers are made up and phone numbers are masked.

The walpio dashboard’s Inbox: a list of customer conversations beside an open conversation with a customer, a note that the reply window is open for 23 more hours, and a reply box. — **Inbox.** Customers’ replies, one conversation per customer and number. The bar above the thread says whether the 24-hour window is open, so your team knows how a reply will go before sending it.

The dashboard’s Overview: today’s counts of unread conversations, refused sends, failed sends and sends waiting for a delivery report, and a readiness checklist with all six steps done. — **Overview.** What needs you today — unread conversations, refused and failed sends — and a checklist that says when your workspace is ready to send.

A message’s details in the dashboard: the times it was sent, delivered and read, the message text, the sending number, the API key that sent it and Meta’s pricing category. — **Messages.** Every message and its status. Open one to see what happened — sent, delivered, read — which of your numbers sent it, what sent it and how Meta priced it.

The text-rule tester: a pasted “order ready” message recognised by a rule, to be sent as the approved template order_update with the value WO-1042. — **Text rules.** Paste a message as your system would send it and see which approved template it becomes outside the 24-hour window, with the values filled in. Nothing is sent.

The operator console’s Needs attention board with one item: two texts refused in the last 24 hours for a demo client, the reasons, and what to do. — **walpio’s side.** walpio’s operators work from one board of the numbers, templates and sends that need attention across clients, worst first, with what to do about each.

Pricing

Simple plans. Serious value.

Monthly plans in US dollars, agreed with you and invoiced directly — no setup fee, no card on file. Meta's per-message charges are separate and billed by Meta to your own Meta account — we never mark up your traffic.

Starter

For a single business getting serious about WhatsApp.

$29 USD / month

≈ AED 107 / month

1 WhatsApp number
3,000 messages / month
Send rate up to 60 / min
24-hour window handling + text rules
Delivery tracking & message log
Assisted onboarding, email support

Choose Starter

Recommended

Growth

For teams where WhatsApp drives real revenue.

$79 USD / month

≈ AED 290 / month

3 WhatsApp numbers
25,000 messages / month
Send rate up to 300 / min
Everything in Starter
Help writing templates for Meta review

Choose Growth

Scale

For high-volume operations and multi-brand teams.

$199 USD / month

≈ AED 731 / month

10 WhatsApp numbers
100,000 messages / month
Send rate up to 600 / min
Everything in Growth
Help moving from your current provider

Choose Scale

See a month's total, Meta's fees included

Need more numbers or more volume? Tell us what you need or write to [email protected].

Currency and billing. Prices are in US dollars (USD) per month, and walpio invoices in US dollars. The dirham (AED) amounts are the same prices at the UAE's fixed peg of 3.6725 dirhams to the dollar, shown for reference. Plans are agreed with you in writing and invoiced directly by walpio; taxes, where they apply, are shown on the invoice. See the cancellation & refund policy.
Meta's charges are separate. Meta bills its per-message charges to your own Meta account at Meta's rates — templates by category and country and, from 1 October 2026, service replies beyond 1,000 per number per month. How Meta pricing works.
What counts as a message. Each outbound message Meta accepts from your workspace in a calendar month (UTC); messages customers send you are not counted. Go over and sending continues while we agree the right plan with you — or ask for a hard monthly cap.

For developers

If you can call an API,
you can send WhatsApp.

One send endpoint whose body follows the Cloud API's text and template shapes, bearer-key auth, and signed callbacks for what happens next. The API reference has the rest.

# Send a WhatsApp message. The Idempotency-Key makes a retry safe.
curl -X POST https://api.walpio.com/v1/messages \
  -H "Authorization: Bearer wp_live_····" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-42-out-for-delivery" \
  -d '{
    "to": "+9715XXXXXXXX",
    "type": "text",
    "text": { "body": "Your order #42 is out for delivery today." }
  }'

# 200 — sent to Meta. The customer wrote in the last 24 h, so it went as text.
{
  "messaging_product": "whatsapp",
  "messages": [{ "id": "wamid.HBgM…" }],
  "walpio": { "id": "7b1c…", "via": "text", "status": "accepted" }
}

# Teach walpio your wording once — a text rule points it at an approved template…
curl -X POST https://api.walpio.com/v1/text-rules \
  -H "Authorization: Bearer wp_live_····" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Order out for delivery",
    "pattern": "Your order {{order}} is out for delivery today.",
    "templateName": "order_out_for_delivery",
    "templateLanguage": "en",
    "params": ["order"]
  }'

# …and the same send, outside the window, goes out as that template:
{
  "messages": [{ "id": "wamid.HBgM…" }],
  "walpio": { "via": "template", "status": "accepted",
              "template": { "name": "order_out_for_delivery", "language": "en" },
              "transformations": ["matched_text_rule"] }
}
# No rule matches? 422 no_matching_template — nothing is sent.

# walpio POSTs statuses, inbound messages and template changes to your URL.
POST https://your-app.example/walpio
walpio-event: message.status
walpio-delivery: 5f0e…
walpio-signature: t=1790330400,v1=<hex HMAC-SHA256(secret, "<t>.<raw body>")>

{ "id": "…", "event": "message.status", "created_at": "2026-09-25T10:00:00Z",
  "data": { "message_id": "7b1c…", "wa_message_id": "wamid…",
            "status": "delivered", "client_reference": "order-42",
            "pricing": { "category": "utility", "billable": true } } }
# Verify the signature, reject a t older than 5 minutes, de-duplicate by id.

Safe retries. Send an Idempotency-Key and a retry replays the first answer — the customer gets one message, not two.

Errors you can act on. Every error carries a code, a plain message and a retryable flag; a rate-limit 429 comes with Retry-After.

Signed callbacks. The statuses Meta reports, customers' replies and template changes are posted to your URL, signed with walpio-signature and retried if you're down.

Read the API referenceService health: api.walpio.com/health

FAQ

Answers, straight.

Something we didn't cover? Ask us directly — a human replies.

Is this the official WhatsApp API?

Yes. walpio is built on Meta's official WhatsApp Business Cloud API. No unofficial clients or gray-market tricks — your number stays on Meta's official platform, under Meta's policies.

Do I need my own WhatsApp number?

Yes — and that's a feature. You bring your own Meta WhatsApp Business account: your number, your display name, your direct billing with Meta. walpio operates it for you, but ownership never leaves your hands.

What happens outside the 24-hour window?

Outside the window WhatsApp only delivers templates Meta has approved. walpio checks the window on every send: you can send a template by name, or set up text rules so the wording you already send is recognised and sent as the matching approved template, values filled in. If nothing matches, the send is refused with a clear reason rather than dropped — and every answer says which route was used.

Why not use Meta's Direct Send instead?

Direct Send lets a business send plain text marked as utility, and Meta picks a matching approved template or creates one for it. As of September 2026 Meta offers it only to businesses that meet its prerequisites (it calls it a premium solution), and it does not cover marketing messages. walpio's text rules work on every account: you choose the approved template each wording goes out as, you can test the match before anything is sent, and every answer says which route and template were used. walpio does not send through Direct Send today.

What does onboarding look like?

We do it with you: connect your Meta account, submit your templates for Meta's review, hand you your API key, and send the first live message together. How long it takes depends mostly on Meta's business verification and template reviews.

How is pricing structured?

Monthly plans from 29 US dollars, agreed with you and invoiced directly — no setup fee and no card on file. Meta's per-message charges are separate: Meta bills them to your own Meta account, and walpio never marks them up. Refunds are handled case by case under your plan agreement.

Can I leave whenever I want?

Yes. Your Meta account, number and templates are yours and keep working without walpio, and we export your walpio data on request. Our send body follows the Cloud API's text and template shapes, so the messages your code builds carry over; the endpoint, the errors and the status callbacks are walpio's own and would change.

Put WhatsApp to work.

Tell us about your business and what you want WhatsApp to do for it — we'll set up your number and templates with you and get you sending.

Get started

or write to [email protected]