This document serves as a detailed glossary and reference guide for businesses, developers, and product owners integrating with the WhatsApp Business API — whether via Meta’s Cloud API, a Business Solution Provider (BSP), or On-Premise deployments. It also clarifies how Meta’s broader ecosystem tools (like Business Manager, Business Suite, and WhatsApp Manager) interact within this integration process.
Meta (formerly Facebook) provides a suite of platforms and tools to manage business assets and integrations across WhatsApp, Facebook, and Instagram.
| Term |
Description |
| Meta for Developers |
The developer portal to create and manage Meta apps that integrate with WhatsApp Cloud API and other APIs. |
| Meta Business Manager |
Centralized dashboard to manage business assets such as Meta Apps, WhatsApp Business Accounts (WABA), ad accounts, and user permissions. |
| Meta Business Suite |
An integrated platform for small-to-medium businesses to manage Facebook, Instagram, and WhatsApp messaging, publishing, and analytics. |
| WhatsApp Manager |
A specialized section within Business Manager to configure and manage WhatsApp Business Account settings, phone numbers, message templates, and messaging quality. |
WhatsApp API Deployment Models
Meta offers two distinct models for businesses to access WhatsApp Business APIs:
| Model |
Description |
| WhatsApp Cloud API |
Cloud-hosted by Meta, no infrastructure setup required. Faster, more scalable, and modern deployment. Businesses manage their own access tokens, templates, and numbers via Business Manager. |
| WhatsApp On-Premises API |
The original API solution hosted on business-owned or BSP-managed servers. Requires infrastructure, server management, and manual updates. Still widely used for enterprise deployments. |
Key Roles and Stakeholders
| Role |
Responsibility |
| Business Solution Provider (BSP) |
Meta-certified partners who provide hosting, onboarding, compliance, and API access — often for On-Premise deployments or as resellers of Cloud API. Examples: Twilio, Gupshup, MessageBird. |
| Tech Provider |
Software companies or platforms offering WhatsApp-based products (CRMs, automation, chatbots), using either Cloud API or BSP integrations. May provide embedded signup and management tools for clients. |
| Direct Cloud API User |
Businesses or SaaS platforms that directly interact with Meta’s WhatsApp Cloud API without intermediaries. They manage phone numbers, templates, and tokens via Meta Business Manager. |
Messaging Concepts and Policies
| Term |
Description |
| 24-Hour Customer Care Window |
A rolling 24-hour period starting from the last user message, during which businesses can send free-form session messages without using templates. |
| Template Messages |
Pre-approved, structured message formats required for initiating conversations or sending notifications outside the 24-hour window. These require prior Meta approval. |
| Template Categories |
Template types include Marketing, Utility, and Authentication based on use-case and content. |
| Session Messages |
Messages sent within the 24-hour customer care window; free-form and unrestricted by templates. |
| Message Template Namespace |
A unique identifier within the Meta app that scopes and organizes message templates. |
| Opt-In |
Explicit customer consent required before sending WhatsApp messages. Must comply with WhatsApp’s policies and regional regulations. |
| Message Tags |
Approved categories for outbound messages sent outside the 24-hour window, e.g., transaction_update. Only specific tags are allowed. |
Account Health & Messaging Limits
| Term |
Description |
| Phone Number Quality Rating |
A real-time quality score (Green/Yellow/Red) reflecting user feedback and policy adherence on messaging from a specific phone number. |
| Messaging Limits (Tiers) |
Quotas on the number of unique customers a business can message per day, starting from 1,000 up to unlimited, based on business verification and performance. |
| Business Verification |
Meta’s identity verification process for businesses, required for production API use and increased messaging limits. |
| Display Name Approval |
Approval of the WhatsApp business display name, which customers see on chat. |
| Two-Factor Authentication (2FA) |
Optional security feature protecting business accounts with a PIN to prevent unauthorized access. |
| Messaging Policy Violations |
Violations such as spam, template misuse, or unsolicited messaging, which can lead to quality score drops, messaging limits reductions, or account bans. |
WhatsApp API Technical Components
| Term |
Description |
| Phone Number ID |
Unique Meta-assigned identifier for your WhatsApp Business phone number, used in API calls to specify the sender. |
| Access Tokens |
Authentication tokens (short-lived and long-lived) that authorize API calls. Managed via Meta Business Manager and OAuth flows. |
| Webhooks |
Callback URLs configured to receive real-time event notifications such as incoming messages, message status updates, and errors. |
| Media Upload Endpoint |
API endpoint to upload images, videos, documents, and retrieve media_id for sending media messages. |
| Graph API Explorer |
Meta’s tool for testing and debugging Graph API calls including WhatsApp endpoints. |
| App Review |
Mandatory Meta review process to approve apps requesting extended permissions before going live in production. |
| Message ID |
Unique identifier returned on sending a message, used to track message delivery and status. |
Account Setup & Integration Workflow (Cloud API)
A typical step-by-step workflow to integrate with WhatsApp Cloud API:
- Create a Meta Developer App: Register your application at Meta for Developers portal.
- Add WhatsApp Product to Your App: Enable WhatsApp Cloud API within your Meta app.
- Register a Phone Number via WhatsApp Manager: Link your business phone number and obtain a Phone Number ID.
- Generate Access Tokens: Obtain temporary tokens for initial testing; later, set up system users to generate permanent tokens.
- Test API Calls Using Graph API Explorer: Validate sending and receiving messages via Meta’s developer tools.
- Configure Webhooks: Set up your webhook endpoint URL to receive incoming messages and event callbacks.
- Submit Message Templates for Approval: Create and submit structured templates in WhatsApp Manager and wait for Meta approval.
- Complete Business Verification & Display Name Approval: Verify your business identity and get the official display name approved.
- Switch to Production Mode & Scale: Use permanent tokens and production phone numbers for live messaging.
Additional Important Concepts
| Term |
Description |
| Embedded Signup |
Feature for Tech Providers to onboard businesses directly via their platform into WhatsApp Cloud API without manual Facebook Business Manager steps. |
| Interactive Messages |
Rich message types supporting buttons, list menus, quick replies, enhancing user engagement. |
| Rate Limits |
API call restrictions to prevent abuse and maintain platform stability. |
| Session Messaging Window |
The period post user message during which businesses can send free-form messages without template restrictions. |
| Business Profile |
Public business information visible on WhatsApp (address, website, description). |
| Sandbox Environment |
Limited test environment (often BSP-provided) to safely test WhatsApp integration without affecting production. |
| Fallback Message |
Automated message sent when the primary message delivery fails or for unrecognized inputs. |
Quick Reference: WhatsApp Cloud API Key Terms
- Business: Uses WhatsApp for communication, responsible for customer opt-in and policy compliance.
- Facebook Business Manager: Central platform to manage business identity, assets, and permissions.
- WhatsApp Manager: Tool within Business Manager to manage phone numbers, message templates, and monitor messaging quality.
- BSP (Business Solution Provider): Meta-certified partners providing API hosting, onboarding, and compliance services.
- Tech Provider: Software/platform providers building WhatsApp integrations, may offer embedded signup and enhanced features.
- WhatsApp Cloud API: Meta-hosted, fully managed API requiring no infrastructure setup; scalable and easy to onboard.
- On-Premise API: Self-hosted WhatsApp API deployment requiring technical resources and infrastructure management.
- Template Message: Pre-approved, structured message formats required for outbound messages outside the 24-hour session window.
- Session Message: Free-form messages allowed within 24 hours of last user interaction without template restrictions.
- Access Token: Authentication credentials to authorize API calls; requires proper handling and renewal.
- Webhook: Callback URLs that receive real-time notifications for incoming messages, delivery, and status updates.
Pabbly Chatflow Team•Updated Jul 25, 2026•6 min read