Video summary

Como Configurar API Oficial do WhatsApp (Meta) em 2026: com Coêxistência + Integração com Chatwoot

Main summary

Key takeaways

Technology

Overview

This video is a detailed, step-by-step guide for integrating WhatsApp into Meta’s official WhatsApp Cloud API (referred to as “Meta PI” in the subtitles) in 2026. It covers:

  • Creating and verifying a Meta app
  • Setting up coexistence/integration so you can use WhatsApp via an external chat tool (e.g., Chatwoot) while still using Meta’s official API
  • Creating WhatsApp message templates
  • Using webhooks so conversations appear inside the chat tool

A recurring emphasis is having a “chat inbox/tool” to avoid losing access to the WhatsApp UI/panel when certain integration approaches are used.

Integration approaches (two paths)

Path A — Direct registration / direct API number setup

  1. Integrate the WhatsApp number directly in Meta.

Downside: you lose access to WhatsApp through the WhatsApp app/panel (no conversation management UI), so you rely on the chat tool (e.g., Chatwoot) to view and manage conversations.

Path B — Coexistence (verified setup)

This is used when you want to connect WhatsApp while meeting Meta requirements to become a partner/technology provider workflow.

Requires:

  • Business/app verification
  • Additional prerequisites (e.g., making required API calls and completing app review requirements)

The creator notes that you often must do Path A first, then Path B, to satisfy prerequisites.

Chat tool requirement (mandatory in practice)

The speaker repeatedly states you need a chat interface/tool to manage conversations.

Options:

  • Use a partner tool (example: Chatwoot) and pay monthly (plus possibly per-message markup)
  • Run your own Chatwoot instance (self-host) for lower cost and full control

Example costs mentioned:

  • Chatwoot: R$119 per agent
  • Self-hosting: about ~R$40/month (server cost)

Self-hosted Chatwoot setup (VPS + domain + server)

To self-host the chat tool, the video includes infrastructure steps:

  • Rent a VPS (example provider: Hostinger; OS selection isn’t required in the flow they describe)
  • Use Cloud Code (or similar assistant tools) to accelerate setup and reduce programming effort
    • Requires at least a Pro plan
  • Install Chatwoot on the VPS using a GitHub repo/workspace approach
  • Use a domain name (they mention it can be obtained for free with a longer VPS contract, e.g., 12 months)
  • Choose a VPS location close to you (example: Campinas/São Paulo, or else US)

Time expectation for app review: business/app review can take ~20 days on average (sometimes more/less), per the video’s warning.

Meta Business Manager (BM) setup and Business Verification

Key steps in Meta Business settings include:

  • Create/select a Business Portfolio (Business Manager / BM)
  • Configure access for integrations (Facebook Page/Instagram/WhatsApp, etc.)

Business Verification

  • Described as mandatory for the coexistence path.
  • Brazil-focused requirements mentioned:
    • Must include CNPJ
    • Meta may send a verification code via a phone number tied to the CNPJ
    • Requires uploading documents/proof
      • They mention using a tax office site to generate a proof/payment document using CPF

Create and publish the Meta app (developers.facebook.com)

Create the app

  • Go to Meta Developers and create an application for WhatsApp use cases.

The app creation process uses an approach described in the subtitles as MCP shortcut / connecting Meta to Cloud Code workflows.

Publish the app

Publishing requires:

  • A real privacy policy URL
  • Valid terms/service URLs
  • Required metadata (e.g., app icon, category, and other required fields)

Troubleshooting hint: publishing errors are likely due to incorrect privacy policy / terms URLs.

WhatsApp number registration and verification (in Meta)

The video outlines how to connect the phone number:

  • Add the phone number in Meta’s WhatsApp setup
  • Register and confirm it reaches pending → connected status

If the UI PIN method fails:

  • They recommend completing verification via API calls

Other details mentioned:

  • Generating tokens (temporary and permanent)
  • Handling identifiers such as WABA (WhatsApp Business Account)
  • A “2-stage PIN” concept and the risk of burning attempts (there are limited tries)

Templates: WhatsApp message templates required

To send messages and support the workflow, you must create templates:

  • Create a welcome message template (example: for a course buyer/student)
  • Use a permanent token for template operations
  • They demonstrate:
    • Template creation (possibly multiple variations)
    • Template approval before sending in some flows

Templates become visible in WhatsApp Manager (and developer templates appear to synchronize there).

Webhook + Chatwoot integration (to view conversations)

To sync conversations into Chatwoot:

  • Configure a Webhook URL in Chatwoot integration settings
  • In Chatwoot, set:
    • Phone number / Phone Number ID
    • WhatsApp account ID
    • API key

Webhook events

  • Example event used: message (receive messages)
  • Other possible events mentioned: group updates and template updates

Verification of the integration

  • Send a WhatsApp message externally
  • Confirm it appears in the Chatwoot inbox and renders correctly

Coexistence (technology provider) app review

The coexistence section focuses on Meta’s requirements for WhatsApp coexistence/technology provider status:

  • In the app’s use cases area, select the technology provider / coexistence workflow.
  • The review checklist requires:
    • Correct permissions fields (at least two are emphasized in the subtitles)
    • Upload videos demonstrating:
      1. WhatsApp Business Message permission usage (show sending a message and how it appears)
      2. WhatsApp Business Management permission usage (show creating a template and the workflow)

They also mention using the cloud tool to generate/edit:

  • Captions/subtitles
  • Descriptions required by Meta

They note you should ensure API calls exist to satisfy evidence requirements.

After submission: review is again described as around ~20 days.

Facebook login + embedding the WhatsApp experience in the chat tool

Later steps include:

  • Setting up Facebook login / permissions for the integration UI
  • Ensuring allowed domains and redirect settings
  • Connecting an existing WhatsApp Business App via QR code pairing

After pairing, Chatwoot begins receiving/sending through the API setup.

Payment setup

The video briefly mentions:

  • Adding a payment method (credit card) in Meta BM/WhatsApp Manager
  • Notes about Brazil currency/time zone settings
  • WhatsApp messaging requires payment (referred to as “shots” in the subtitles)

Key deliverables / “what you end up with”

By the end, the guide aims to produce:

  • WhatsApp number registered and verified in Meta
  • At least one WhatsApp template created
  • A permanent token and webhook configured
  • Chatwoot configured to receive:
    • Incoming WhatsApp messages
    • Template sync updates
  • A submitted coexistence/technology provider app review (demo indicates it can be shown as completed)

Main speakers / sources

  • Claudio (repeatedly referenced as the guide/assistant within the “Cloud Code” style workflow)
  • The video’s instructor/speaker (examples/coupons reference the name “Pedro Almeida”, though it’s not fully explicit that this is the speaker’s full identity)
  • Meta (Facebook Developers / Meta Business Suite)
  • Chatwoot
  • Cloud Code
  • Hostinger (mentioned as a VPS/server provider)

Original video