Notifications
Order, delivery, appointment, account and outage updates, triggered where the event happens.

The WhatsApp Business API, now delivered as Meta's Cloud API, lets an organisation send and receive WhatsApp messages from its own systems at scale. Arke Technologies in Johannesburg sets it up for organisations, public bodies and schools across South Africa, connects it to your CRM, service desk or chatbot, and supports it under an SLA.
The WhatsApp Business API is Meta's programmable interface to WhatsApp for organisations that need more than one phone can handle. Your CRM, service desk, booking system or chatbot sends messages through the API and receives replies through webhooks. Meta calls the product the WhatsApp Business Platform. Meta's WhatsApp Cloud API is the version Meta hosts, and it is the standard route now that the older self-hosted On-Premises API has been retired.
A WhatsApp Business API account (formally a WhatsApp Business Account, held in your Meta business portfolio) carries your verified profile, phone numbers and approved message templates. It should be registered to your organisation, never to the developer.
Searches for "api whatsapp com" usually mean the click-to-chat address api.whatsapp.com/send (or wa.me), which opens a chat from a website button or QR code. It is free and useful, but it is a link rather than an integration: nothing reaches your systems.

| WhatsApp Business app | WhatsApp Business API (Cloud API) | |
|---|---|---|
| Suits | Sole traders and small teams | Organisations with volume, several agents or systems to connect |
| How it runs | An app on a phone, with linked devices | Your software, connected to Meta's cloud; no phone app |
| Agents | A few people sharing one number | As many agents as your inbox or CRM supports |
| Automation | Quick replies, greeting and away messages | Chatbots, workflows, CRM and ERP integration, notifications |
| Starting a conversation | Any message, sent by hand | Approved templates, sent to customers who opted in |
| Cost | Free app | A price per template message, plus build and running costs |
The choice is about scale and integration. The older "WhatsApp Business API vs Cloud API" question is now history: the Cloud API is the current form of the Business API.

The WhatsApp Business API features that matter most are message templates, interactive buttons and lists, media and documents, and structured forms (WhatsApp Flows). Organisations use them for:
Order, delivery, appointment, account and outage updates, triggered where the event happens.
One-time passcodes for sign-in and payments.
A shared inbox that routes chats, keeps history on the customer record and hands over between bot and agent.
Answers, bookings and status checks outside office hours.
WhatsApp Business API for marketing means templates sent only to customers who opted in, with opt-outs honoured at once.
Schools can use it for parent notices and fee statements, and municipalities for service requests and outage updates.
A WhatsApp chatbot can be a simple menu or an AI assistant that answers in plain language from your own content and systems. For WhatsApp AI automation we build with models from Anthropic (Claude) and Google (Gemini, through Vertex AI), with guardrails, logging and cost controls.
We build each WhatsApp Business API bot with three modes: off, draft (staff approve each reply) and automatic, the approach we use for the customer assistant on our own Server Hub platform. Start in draft, measure accuracy, then automate only what the bot answers well; a person can always take over. Meta's terms restrict general-purpose AI assistants on WhatsApp, so we design bots that answer your own customers' questions and check the current policy during design. See chatbots and conversational AI and AI automation.

How to apply for WhatsApp Business API access:
01.
A Meta business portfolio in your organisation's name, administered by your own staff.
02.
Meta verifies the organisation from its company documents, which raises messaging limits.
03.
A WhatsApp Business Account and a number that can receive a verification code. A number on the Business app can be moved across.
04.
Submitted for approval, with the business profile completed.
05.
Drafted and submitted in the right category: marketing, utility or authentication.
06.
A system-user access token, a webhook endpoint for messages and statuses, and a payment method for template charges.
07.
Your CRM, service desk or chatbot connected, tested and launched.
Meta's developer documentation covers each step. We do the setup with your team, so every credential stays yours.
To send, your system calls the WhatsApp message API with the recipient and either free-form content or an approved template. Inside the 24-hour customer service window, which opens when a customer messages you, you may reply freely; outside it, every message you send through the API must be an approved template.
To get messages, the WhatsApp API uses webhooks: Meta pushes each incoming message, and each delivery and read status, to an endpoint you host. There is no mailbox to poll, so we build the endpoint with signature checks, queues and retries that lose nothing on a busy day.
Quality matters as much as code. Daily messaging limits start low and rise while your quality rating stays high; blocks and reports pull it down, so we design templates and opt-in flows to keep it healthy.

| Route | What it is | Suits | Watch for |
|---|---|---|---|
| Cloud API, direct | Your own WhatsApp Business Account on Meta's hosted Cloud API, integrated into your systems | Organisations that want to own the account, the data flow and the costs | Needs development and someone to run it |
| A BSP platform | A business solution provider (Meta lists them as WhatsApp Business API partners), such as Twilio or WATI, providing access plus its own inbox or developer tools | Teams that want a ready-made inbox, or already use one | Platform fees on top of Meta's charges; data and templates held in their tool |
| An unofficial "open" or third-party API | Libraries or services that automate the consumer WhatsApp app | Nothing we would recommend | Breaks WhatsApp's terms; numbers get banned; no POPIA-grade control of data |
You do not need a WhatsApp BSP to use the Cloud API. If your number already sits with a provider such as Twilio or WATI, we can integrate your systems with that provider's API instead of moving you. We will not build on unofficial WhatsApp open API libraries: a banned number takes your customer channel down with it.
Meta charges no hosting fee for the Cloud API, and replies inside the 24-hour customer service window cost nothing. You pay for business-initiated template messages, charged per delivered message, and for the integration that sends them. The full cost has three parts.
| Cost | What sets it | Who charges it |
|---|---|---|
| Template messages | The price per delivered message depends on the category (marketing costs most; utility and authentication less) and on the recipient's country. Utility templates sent inside an open service window are free | Meta, from its published WhatsApp API pricing, which includes rates for South African numbers |
| Platform fees | A subscription or per-message mark-up; nil on the Cloud API directly | A BSP, if you use one; Twilio WhatsApp API pricing, for example, sits on top of Meta's |
| Integration and running | Systems connected, chatbot complexity, reporting, hosting for your webhook endpoint | Arke: the build is quoted per project after discovery; support, monitoring and template management run under an SLA |
What moves the total is the cost per message multiplied by your mix of categories, plus the systems you connect. For context, published hourly rates for IT project work in South Africa run from about R550 to R750 ex VAT (matnet.co.za, September 2026). The WhatsApp Business app itself is free, so WhatsApp Business charges begin only with the API.
Last reviewed: September 2026.
WhatsApp business integration is where the value sits. We connect the WhatsApp integration API to:

A CRM with WhatsApp integration logs each conversation against the contact in Salesforce, HubSpot or Zoho, and triggers templates from CRM events.
Chats become tickets with SLA clocks.




Filing reminders and document requests raised by the systems that track SARS and CIPC deadlines.
Moving from a BSP's tool to the Cloud API? Your WhatsApp Business Account can move with you, and opt-in records and conversation history that the old tool can export are moved as a planned data migration.
The WhatsApp Business API is Meta's interface for sending and receiving WhatsApp messages from an organisation's own software instead of a phone app. It connects WhatsApp to CRMs, service desks and chatbots, supports many agents on one number, and uses approved templates for business-initiated messages. New integrations use the Cloud API, which Meta hosts.
Partly. Meta charges no hosting fee for the Cloud API, and replies inside the 24-hour customer service window are free. Business-initiated template messages are charged per message, by category. Building, hosting and supporting the integration are separate costs, which we quote after discovery so you can compare them with the manual work they replace.
The WhatsApp Business API in South Africa costs Meta's per-message charges for templates, set by category and published for South African numbers, plus any provider platform fees and the cost of building and running the integration. Marketing templates carry the highest price per message. We model your expected message mix before you commit.
You apply through Meta: create a business portfolio, verify your organisation, register a WhatsApp Business Account and phone number, and have your display name and message templates approved. Then connect the API to your systems. We do this with your team, so the account and credentials are registered to your organisation.
The WhatsApp Business app runs on a phone and suits a few people answering chats by hand. The API has no app of its own: it connects WhatsApp to your software, supports many agents, chatbots and automated notifications, and charges for business-initiated templates. Organisations move to it when volume or integration needs outgrow the app.
No. Meta's Cloud API is open to organisations directly, and we build on it under your own account. A business solution provider makes sense if you want its ready-made inbox, and if you already use one, we can integrate with its API instead of moving your number to a new provider.
Only once one phone stops coping. For one or two people answering chats, the free WhatsApp Business app is usually enough. The API makes sense when several staff share the number, when you need automated notifications or a chatbot, or when chats must be logged in a CRM. See IT for small and medium businesses.
Tell us what customers should be able to do on WhatsApp, and which systems hold the answers. We will map the flows, estimate your message costs and quote the build.