- Halo converses on your WhatsApp line: text, media, interactive messages (buttons, lists), approved templates and published Flows through Atlas
- Staff sends approved template messages for subscription reminders and notifications on a schedule — from the Apivom line or a tenant's own Cloud API credential
- Inbound messages, statuses and Flow completions arrive via signature-verified Meta webhooks
- Phone-number registration, verification, two-step PIN and display-name routes catalogued alongside messaging
- 140 routes (40 read-only) on graph.facebook.com; every send is recorded with Meta's message id
WhatsApp Cloud API Connector
Meta's WhatsApp Cloud API — send and receive text, media, approved templates, interactive messages and published Flows on your WhatsApp Business number — the API behind Apivom Halo and Apivom Staff: the assistant converses on the WhatsApp number Apivom operates for you, and scheduled automation sends approved template reminders and notifications.
What you can do
Use cases
- A WhatsApp assistant on your own number — Let Halo greet, qualify and help customers on a WhatsApp number dedicated to your brand, with hand-over to a person when needed.
- Reminders that get read — Send approved renewal or appointment templates from Staff on a schedule — WhatsApp open rates instead of e-mail ones.
- Forms inside the chat — Deliver a published WhatsApp Flow (booking, address, feedback) as a native form and receive the answers structured, not as free text.
The WhatsApp Cloud API is Meta's hosted way to run a WhatsApp Business number programmatically: register and verify the phone number, send free-form text and media inside the 24-hour customer-service window, send pre-approved templates outside it, offer interactive buttons and lists, deliver WhatsApp Flows and receive everything back — messages, read receipts, delivery statuses — through webhooks. Apivom Atlas catalogues 140 of its routes. Apivom Halo, the conversational assistant, runs on it through Atlas: on the WhatsApp number Apivom operates for your tenant it answers customers in text or media, uses interactive buttons and lists for choices, sends approved templates when the window is closed and delivers published Flows as native in-chat forms, reading the completed form back from the webhook. Apivom Staff uses the same connector for scheduled, approved template sends — subscription renewal reminders and notifications — from the Apivom line or from a tenant's own Cloud API credential. Inbound traffic reaches Apivom through Meta's webhooks with signature verification. Atlas forwards the token on each call and records the request and Meta's message id without storing it.
A Meta Graph access token (System User recommended) for the WhatsApp Business Account that owns the number, sent as Bearer per request; webhooks need the app secret for signature checks. Lines Apivom operates use Apivom's token; a tenant's own token is encrypted in Apivom Iris. Atlas stores nothing.
Frequently asked questions
What is the 24-hour window and how does Apivom handle it?
WhatsApp allows free-form messages only within 24 hours of the customer's last message; outside that window only pre-approved templates may be sent. Halo replies free-form inside the window, and once it has closed only approved templates go out — free text is refused; Staff reminders are always templates.
Which token should I use?
A System User access token from your Meta Business portfolio with the WhatsApp Business Account assigned is the stable choice — it does not expire with a person's session. User and app tokens work but are tied to a person or to app-level operations.
Do I need a Meta app of my own?
Not for a line Apivom operates: a number provisioned on Apivom's WhatsApp Business Account, or your own number onboarded through Embedded Signup, runs under Apivom's Tech Provider app and token, which also receives the webhooks. A tenant with its own Meta app can keep its own Cloud API token stored in Apivom Iris for Staff's template sends.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.