The Official API is the WhatsApp Business Platform provided by Meta to integrate messages with enterprise systems. A so-called “unofficial” connection typically links a tool to a WhatsApp session via QR code, without using Meta's API to transport messages. The two modalities have different requirements, features, costs and risks; the choice should consider the importance of the channel to the operation.
What is Official WhatsApp?
“Official WhatsApp” is a common way to refer to the WhatsApp Business Platform, also known as WhatsApp Business Platform or Official API. It provides interfaces maintained by Meta for companies to integrate the channel with support systems, automation, campaigns and internal processes.
The platform is not an out-of-the-box inbox by itself. The company can connect it to a partner solution, develop its own interface or use compatible tools. The WPP Marketing WhatsApp platform, for example, is a software layer that organizes operational features over the available connection modalities. It should not be confused with Meta's API.
In the official option, messages initiated by the company are subject to the current template and category rules. Meta's current documentation shows charging per delivered message, with rates that vary by market and category. Partner or platform costs may exist separately.
What is an unofficial QR Code connection?
A QR Code connection links a tool to a WhatsApp account session, similarly to the process used to connect devices. It does not make that tool the Meta Official API and does not grant the same contracts, features or support flows as the Business Platform.
This type of integration may be marketed as “API by QR Code”, “WhatsApp Web API” or “unofficial connection”. Names vary, but the decisive point is technical: ask whether messages travel through Meta's WhatsApp Business Platform or whether the solution depends on a session linked by QR code.
It is not correct to say that the modality has zero cost. Even when there is no Meta charge for the Business Platform, there may be tool subscription fees, infrastructure, support, maintenance and costs resulting from downtime or reconnection.
Official WhatsApp or QR Code: practical comparison
| Criterion | Meta Official API | QR Code connection |
|---|---|---|
| Setup | Requires a business account, an eligible number, configuration on Meta and direct integration or via a partner | Usually requires scanning a QR code and authorizing the session in the tool |
| Stability | Operates using the official infrastructure and interfaces, but remains subject to outages, limits and unavailability | Depends on the linked session and may require reconnection; behavior varies by implementation |
| Templates | Messages initiated by the company must follow the platform's templates, categories and current rules | Does not use the same official template approval flow, but remains subject to policies applicable to WhatsApp use |
| Operation | Designed for integrations, automations and enterprise support through compatible systems | Can serve tests and limited operations, depending on resources and risk tolerance |
| Device dependency | The Business Platform does not depend on keeping a mobile phone connected to transport messages; in CoEx, the app also remains in use | Depends on the account and the session linked by QR code, even when the tool reduces daily interaction with the device |
| Support | Follows Meta channels and, when contracted, the partner or solution provider | Depends mainly on the integration provider and their ability to diagnose the session |
| Costs | Meta charges per delivered message according to market and category; partner and platform may charge separately | There is no universal price: licenses, infrastructure, support, and other operational costs may apply |
| Risk | Lower risk of incompatibility by using official interfaces, without a guarantee of no blocks or interruptions | Greater exposure to changes in operation, disconnections, and measures applied by WhatsApp |
The comparison does not remove the need to test. Volume, message type, criticality, integrations, and contingency capacity can change the impact of each difference.
Official API with CoEx: what does coexistence change?
CoEx, or coexistence, is a configuration that can allow the use of the WhatsApp Business app and the Business Platform on the same number. With it, a company can keep the app in an eligible operation while integrating the number with features offered by the platform and by a partner solution.
This reduces a historical objection to migration: the need to choose between staying on the app or using the API. However, CoEx is not automatically available for all accounts, countries, numbers, or providers. Synchronization, accessible history, app features, and activation steps must be confirmed before switching.
Coexistence also does not mean a verification badge. Using the Official API, completing business verification, and receiving the Official Business Account designation are different matters. Activating the platform does not guarantee a badge on the profile.
See the requirements and how the Official WhatsApp API with CoEx. Before migrating, document how the number, the app, the devices, the conversations, the templates, the integrations, and the possibility of rollback will be handled.
When is the Official API the recommended path?
The official option should be prioritized when WhatsApp is a relevant channel for sales, support, or notifications and the company needs a more predictable foundation for integrations. It is especially recommended to consider when there is:
- recurring message volume and multiple agents;
- the need to integrate e-commerce, ERP, CRM, or proprietary systems;
- automations triggered by business events;
- campaigns that require templates, segmentation, and monitoring;
- security, audit, and access control processes;
- operational dependence that requires official support and documentation;
- growth planning without relying on a session via QR Code.
“Recommended” does not mean infallible. Message quality, permissions, configuration, account limits, and policies remain the operation’s responsibility. The company should also plan for incidents and alternative channels.
When can a QR Code connection be considered?
A QR Code connection can be considered as a secondary alternative in a controlled test, a small operation, or a temporary scenario in which the company understands and accepts the technical differences. It can also be part of the evaluation when the account is not yet eligible for an official modality required by the project.
Before deciding, define the volume, duration, message types, and the impact of a disconnection. Confirm how reconnection works, who will have access to the device, which data will be stored, how to export it, and what support exists. Do not use the alternative to bypass policies, send unexpected messages, or operate without contacts’ authorization.
See the WhatsApp QR Code connection page to understand WPP Marketing’s offering. Features, limits, and conditions of the modality must be verified in the product and the current plan.
Consent, policies, and operational responsibility
The WhatsApp Business Messaging Policy states that the company must obtain the contact’s number and the necessary permission to send subsequent messages. It also requires that opt-out requests be respected and that communication not surprise, deceive, or spam.
On the Business Platform, company-initiated messages use approved templates and must comply with the corresponding category. Within the user-open conversation window, there are specific rules for replies. Template approval does not mean any contact or frequency is appropriate.
Meta also considers quality and user feedback when applying limits and measures to accounts and templates. Therefore, the company must:
- record the origin, purpose and scope of the permission;
- separate transactional and promotional communications when required;
- control total frequency across campaigns, automations and support;
- process opt-outs across all involved systems;
- monitor errors, blocks, complaints and quality indicators;
- provide human escalation for exceptions when applicable;
- keep profile, data and integrations up to date.
These responsibilities exist on both paths. A technical connection does not transfer the company's responsibility for audience, content, frequency, data and compliance to the provider.
Meta API, proprietary API and inbox: they are not the same
The Official API is Meta's infrastructure for WhatsApp Business. A WPP Marketing's proprietary API can expose WPP Marketing platform events and functions for integration with other systems; it does not replace or become Meta's API. A QR Code connection is another transport and account-linking modality.
Similarly, a shared inbox for WhatsApp is the interface used by the team to view, assign and reply to conversations according to available features. The inbox can operate over an official connection or another compatible modality, but it alone does not define which infrastructure is behind the number.
In WhatsApp campaigns, this distinction affects templates, billing, quality, limits, traceability and handling of replies. Before contracting, ask the provider to identify in writing the modality used for each number.
How WPP Marketing offers both paths
WPP Marketing offers official connection options with CoEx and connection by QR Code. For enterprise operations that depend on the channel, the official route with CoEx should be evaluated first because it uses Meta's Business Platform and provides a suitable foundation for integrations and structured processes.
The QR Code option can be considered as a secondary alternative when requirements and risks are compatible with the scenario. In both cases, available features, limits, support, history, costs and eligibility must be confirmed for the plan and account before activation.
Sources consulted
- WhatsApp Business Platform Pricing
- WhatsApp Business Messaging Policy
- WhatsApp Business Platform
- Onboarding to the WhatsApp Business Platform
- Organize your WhatsApp inbox with Meta Business Suite
Sources consulted on August 21, 2026. Prices, categories, policies, limits and eligibility may change; confirm current documentation before implementation.
Choose the connection by risk and business importance
The decision starts with the channel's criticality, the systems that need integration and the impact of an outage. The Official API with CoEx should be the first evaluation for a structured operation; the QR Code can be considered when its scope and risks are acceptable. To check eligibility, deployment and features, see the WPP Marketing official CoEx connection.