- Message templates: list, create, edit and delete templates and read their approval status
- Phone numbers: list business numbers, display-name status, request verification; QR codes with prefilled messages
- Analytics and conversation analytics per WABA; billing credit lines; commerce settings
- Two-step media upload sessions for template headers and catalogue assets
- 41 routes (22 read-only) on graph.facebook.com, documented in the AI integration guide (llms.txt)
WhatsApp Business Management API Connector
Meta's WhatsApp Business Management API — the account-level surface of a WhatsApp Business Account: message templates, phone numbers and display names, analytics and conversation analytics, credit lines, QR codes, commerce settings and media uploads — registered in Apivom Atlas with your own Meta token.
What you can do
Use cases
- Manage templates in code — Create and update message templates from your own tooling and poll their approval status instead of clicking through Meta Business Manager.
- Monitor usage and spend — Pull analytics and conversation analytics per WABA to reconcile message volumes and conversation categories with Meta's billing.
- QR codes for campaigns — Generate WhatsApp QR codes with a prefilled message for print or in-store campaigns and track which one opened the conversation.
Where the WhatsApp Cloud API moves messages, the WhatsApp Business Management API administers the WhatsApp Business Account behind them: the message templates and their review status, the business phone numbers with their display names and verification state, QR codes that open a chat with a prefilled text, account-level analytics (messages sent and delivered) and conversation analytics (billable conversation categories), the credit lines that pay for them, commerce settings for catalog and cart, and resumable media uploads for template headers. Apivom Atlas catalogues 41 of these routes with the Meta credential contract, per-tenant logging and the AI integration guide (llms.txt). Apivom's messaging products work through the Cloud API connector with templates you have already approved; the template-management, analytics and account-administration routes here are available to your own tooling through Atlas today, and bringing them into a product workflow — for example template creation from inside the content calendar — is scoped per customer.
A Meta Graph API access token — a System User token from your Meta Business portfolio is the stable choice — with the permissions this API needs, sent as Bearer on every call. Tokens are encrypted in your Iris tenant when stored; Apivom Atlas forwards and logs the call and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
How is this different from the WhatsApp Cloud API connector?
The Cloud API sends and receives messages on a phone number; the Business Management API configures the account those numbers belong to — templates, numbers, analytics, billing, QR codes. Apivom's messaging products use the Cloud API; this connector covers administration.
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.