WatMark

WABA Manager

WhatsApp Cloud API · onboarding & settings

Where do IDs & token come from?
  1. WABA ID — WhatsApp Manager URL: use the asset_id value (illustration only: …/overview?business_id=430xxxxxxxxxx069&asset_id=130xxxxxxxxxx678 → paste 130xxxxxxxxxx678).
  2. Phone number ID — Fill token + WABA ID, run List phone numbers, then copy response.data[].id.
  3. 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.
  4. SMB / NOT_VERIFIED — If code_verification_status is NOT_VERIFIED and register is not available, use Request verification code then Submit verification code (not the register PIN flow).

Meta sign-in & IDs

Used by all actions. WABA ID = WhatsApp Business Account (from Manager URL asset_id). Phone number ID = your business Cloud API sender id (from List phones → data[].id).

Preset or type any version.

Register (PIN path)

Only for button: Register phone number. Ignore if you use SMS verification (section 3).

SMS / voice verification

For Request verification code then Submit verification code (e.g. SMB NOT_VERIFIED). Fill the code field after Meta sends SMS or calls.

Webhook

Only for Set webhook.

Commerce

Only for Update commerce settings. Get commerce settings ignores these toggles.

Test message

For Send test text message (body below) or Send template message (template name only — 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.