WABA Manager
WhatsApp Cloud API · onboarding & settings
Where do IDs & token come from?
- WABA ID — WhatsApp Manager URL: use the
asset_idvalue (illustration only:…/overview?business_id=430xxxxxxxxxx069&asset_id=130xxxxxxxxxx678→ paste130xxxxxxxxxx678). - Phone number ID — Fill token + WABA ID, run List phone numbers, then copy
response.data[].id. - Access token — Obtain from your team’s private ops channel or Meta’s tools for your app; never share it publicly or commit it to source control.
- SMB / NOT_VERIFIED — If
code_verification_statusisNOT_VERIFIEDand register is not available, use the Verify workflow (request code, then submit).
Meta sign-in & IDs Required
Used by all actions. WABA ID = WhatsApp Business Account (Manager URL asset_id). Phone number ID = Cloud API sender id (List phones → data[].id).
Pick or type a version.
Workflow
Optional · pick one path at a time. Credentials above stay shared.
PIN path for Register phone number. Skip if you use SMS verification.
For Request then Submit verification (e.g. SMB NOT_VERIFIED). Fill the code after Meta sends SMS or calls.
Override callback for Set webhook.
Update uses the toggles below. Get is read-only.
Send a test text or template (no variables). Recipient is the customer’s WhatsApp number — not the Phone number ID.
Customer must message your business first. Free-form text only works inside a user‑initiated session (about 24 hours). Otherwise use an approved template — Meta will reject plain text.