What is the WhatsApp Cloud API?
The WhatsApp Cloud API is Meta's hosted version of the WhatsApp Business Platform. It gives businesses a way to send and receive WhatsApp messages programmatically — through API calls rather than through the WhatsApp app on a phone.
Meta launched the Cloud API in May 2022 as an alternative to the older On-Premises API. The key difference is where the infrastructure lives. With the On-Premises API, businesses (or their BSP) had to host the API on their own servers, manage Docker containers, handle updates, and deal with scaling. The Cloud API moves all of that to Meta's servers. You make API calls to Meta's endpoints, and Meta handles the message routing, delivery, encryption, and infrastructure.
For UAE businesses, this is a practical improvement. You don't need to provision servers, you don't need a DevOps team to keep the API running, and you get automatic updates when Meta adds new features. The Cloud API supports everything the old On-Premises API did — text messages, media, interactive buttons, message templates, webhooks — without the hosting overhead.
Meta is actively phasing out the On-Premises API in favour of the Cloud API, so any new WhatsApp Business API setup in the UAE will use the Cloud API by default.
Cloud API vs WhatsApp Business App
The WhatsApp Business App is the free mobile application that many UAE businesses start with. It works well for a single person handling a small number of conversations. The Cloud API is the infrastructure layer that powers everything beyond that.
| Feature | Business App | Cloud API |
|---|---|---|
| Hosting | Your phone | Meta's servers |
| Number of users / agents | 1 device (+ up to 4 linked devices) | Unlimited (via CRM or custom build) |
| Shared team inbox | No | Yes (via BSP/CRM) |
| Broadcast messages | 256 contacts max | Unlimited (with opt-in) |
| Automated replies | Basic quick replies | Full automation via webhooks |
| CRM integration | No | Yes |
| Message templates | Not required | Required for business-initiated messages |
| Green tick eligibility | No | Yes |
| Cost | Free | Per-message (Meta fees) + platform fee |
| Best for | Solo operators, low volume | Teams, scale, automation |
If you have more than one person answering WhatsApp messages, or you want to send broadcasts to more than 256 contacts, or you need any kind of automation or CRM integration — the Cloud API is what you need. The Business App is fine for a single shop owner handling enquiries personally.
Setup requirements for UAE businesses
Getting on the WhatsApp Cloud API in the UAE requires several components. Having these ready before you start avoids the most common delays.
Meta Business Manager
You need a Meta Business Manager account at business.facebook.com. This is the central admin layer that controls your WhatsApp access, phone numbers, and permissions. Create it using your company's legal name exactly as it appears on your trade licence.
Business verification
Meta requires you to verify your business before you can access the Cloud API for production messaging. For UAE businesses, this means uploading your trade licence and completing domain verification. The business name on your Meta account must match your trade licence exactly. Verification typically takes 2–5 business days. For a detailed walkthrough, see our WhatsApp Business API setup guide.
Phone number
You need a UAE phone number (DU or Etisalat) that is not currently active on any WhatsApp or WhatsApp Business App account. If the number is currently on WhatsApp, you must delete that account and wait before registering the number with the Cloud API.
BSP or direct access
You can access the Cloud API in two ways. Through a Business Solution Provider (BSP) like Tawasel, which handles the technical setup, template management, and provides a user interface. Or directly through Meta, which gives you raw API access but requires your own development team to build the interface, handle webhooks, and manage message queuing.
Most UAE businesses without in-house developers choose the BSP route. It is faster to set up and you get a ready-made inbox, broadcast tools, and automation features without writing code.
Message templates and approval
The Cloud API requires pre-approved message templates for any message you send outside the 24-hour customer service window. If a customer messages you first, you can reply freely within 24 hours. But to reach out to a customer proactively — an appointment reminder, an order update, a promotional offer — you need an approved template.
Template categories
Every template falls into one of four categories, which determines both its approval criteria and its cost:
- Marketing — promotional messages, offers, product announcements. These have the highest per-message cost and the strictest approval criteria.
- Utility — transactional messages like order confirmations, shipping updates, appointment reminders. Lower cost, easier approval.
- Authentication — one-time passwords and login verification codes. Similar cost to utility.
- Service — your replies within 24 hours of a customer messaging you first. Free. No template required.
The approval process
You write your template text, submit it through your BSP dashboard or Meta Business Manager, and Meta reviews it. Most templates are approved within 24–48 hours. Rejections are common when templates sound too promotional for their declared category, contain prohibited content, or use formatting that doesn't meet Meta's guidelines. Keep utility templates genuinely transactional and marketing templates clear about what the customer will receive.
Templates support variables (like customer name, order number, appointment time), media attachments, interactive buttons, and quick reply options. You can submit templates in both English and Arabic — recommended for UAE businesses serving bilingual customers.
Webhooks and integrations
Webhooks are the mechanism that makes the Cloud API useful beyond simple message sending. When something happens on your WhatsApp number — a customer sends a message, a message is delivered, a message is read — Meta sends a real-time notification to a URL you specify. Your system receives these notifications and can act on them immediately.
This is what enables:
- Real-time message delivery — incoming messages appear in your CRM or team inbox instantly, not when someone checks the phone.
- Automated responses — your system can parse incoming messages and trigger automated replies, route conversations to the right team member, or escalate to a human when the chatbot can't handle the query.
- Delivery and read receipts — track whether messages were delivered and read, useful for time-sensitive communications.
- CRM updates — automatically log conversations, update contact records, and trigger workflows in your CRM when specific events happen on WhatsApp.
If you're using a CRM like Tawasel, webhook handling is built in — you don't need to set up endpoints or write parsing logic. If you're building on the raw Cloud API, webhook implementation is one of the more complex parts of the integration.
Cloud API pricing basics
Since 1 July 2025, Meta charges per delivered message rather than per 24-hour conversation. Each template message you send is billed at the rate for its category. Service messages — your replies within 24 hours of a customer-initiated conversation — remain free.
For UAE numbers, approximate per-message rates are:
- Marketing: ~AED 0.16–0.18 per message
- Utility: ~AED 0.039–0.057 per message
- Authentication: ~AED 0.039–0.057 per message
- Service: Free
On top of Meta's per-message charges, you pay a platform fee to your BSP or CRM provider. Tawasel charges a flat monthly fee — Starter at AED 99/month, Growth at AED 279/month, Pro at AED 549/month — with no markup on Meta's message rates. Some BSPs add a per-message markup on top of Meta's base rate, which compounds quickly at volume. For a detailed cost breakdown with worked examples for UAE businesses, see our WhatsApp Business API pricing guide.
When to use a CRM like Tawasel instead of raw API
The Cloud API is a powerful infrastructure layer, but it is exactly that — infrastructure. It gives you endpoints to send messages, receive webhooks, and manage templates. It does not give you a user interface, a team inbox, broadcast scheduling, analytics, or automation rules. You build those yourself, or you use a platform that provides them.
When raw Cloud API access makes sense
- You have an in-house development team that can build and maintain a custom integration
- You need WhatsApp as a notification channel inside an existing product (order updates from your e-commerce platform, OTPs from your app)
- You're building something custom that no off-the-shelf CRM supports
When a CRM layer makes more sense
- Team inbox — multiple agents need to handle conversations from one WhatsApp number. A shared inbox with assignment, notes, and handoff is essential once you have more than two people on WhatsApp.
- Broadcasts — you want to send broadcast campaigns to opted-in contacts with segmentation, scheduling, and delivery tracking without writing API calls.
- No-code automation — you want automated replies, routing rules, and workflows without employing a developer.
- Template management — submitting, tracking, and managing templates through a visual interface rather than API calls.
- Analytics — conversation metrics, response times, agent performance, and campaign results in a dashboard.
For most UAE SMEs — clinics, retailers, real-estate offices, service businesses — the CRM route is more practical. The raw API is the right choice for product teams building WhatsApp into their own software.