- Business-level routes: owned and client WhatsApp Business Accounts, add phone numbers, extended credits, solution partnerships
- WABA routes: phone numbers, subscribed apps, templates, analytics — the same objects as the Cloud and Management APIs, in Meta's official OpenAPI shape
- Pre-verified numbers and partner onboarding (including Marketing Messages Lite) for Solution Providers
- Version-parameterised paths (/{version}/…) so you pin the Graph version per call
- 97 routes (43 read-only) on graph.facebook.com; Apivom's platform tooling discovers WABAs, numbers and their subscribed apps through it
WhatsApp Business Platform API (Official OpenAPI) Connector
Meta's official OpenAPI description of the WhatsApp Business Platform — business accounts, owned and client WABAs, phone numbers, subscribed apps, solution partnerships, extended credits, pre-verified numbers and the messaging routes — registered in Apivom Atlas as a 97-route, version-parameterised catalogue; Apivom's own platform tooling uses it to discover WhatsApp lines.
What you can do
Use cases
- Inventory your WhatsApp estate — List owned and client WABAs, their phone numbers and subscribed apps to see exactly which lines exist, who controls them and whether they can send.
- Solution Provider operations — Create solution partnerships, share pre-verified numbers and extended credits with client businesses from your own tooling, following Meta's official schema.
- Pin a Graph version — Call any route with an explicit version segment so a Meta API upgrade is a deliberate change in your configuration, not a surprise.
Meta publishes an official OpenAPI document for the WhatsApp Business Platform, and this connector is that document registered in Apivom Atlas: 97 routes keyed by Graph version that span the business layer (owned and client WhatsApp Business Accounts, adding phone numbers, extended credit lines, solution partnerships between a Solution Provider and its clients, pre-verified numbers), the WABA layer (phone numbers, subscribed apps, templates, analytics) and messaging. It overlaps with the WhatsApp Cloud API and WhatsApp Business Management connectors — those are the curated, task-oriented catalogues — while this one is the vendor's own schema, useful when you want to follow Meta's reference exactly or pin a specific API version. Apivom's own platform tooling uses this spec to discover the WhatsApp Business Accounts and phone numbers reachable with a token, read which apps are subscribed to each, decide whether a line may send, complete the Embedded Signup subscription and send text, template and media messages from its operations inbox on those lines. For customer products, messaging runs through the Cloud API connector. The credential is a Meta Graph token; Atlas forwards it, logs each call per tenant and stores nothing.
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
Which WhatsApp connector should I use?
For sending and receiving messages: WhatsApp Cloud API. For templates, numbers and analytics: WhatsApp Business Management. Use this official-OpenAPI connector when you need Meta's exact reference shape, version pinning, or the business-level routes (client WABAs, solution partnerships, pre-verified numbers) the curated catalogues leave out.
Does a customer product send messages through this connector?
No. Apivom's own platform tooling uses it to discover lines, read their subscription state and send from its operations inbox; customer-facing messaging goes through the WhatsApp Cloud API connector.
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.