CLI

The CLI uses the same tenant API key as /v1. There is no separate console credential. Run it from a checkout of the Watahub Enterprise Edition repository after pnpm install --frozen-lockfile.

pnpm exec watahub login --api-key YOUR_API_KEY
# or: export WATAHUB_API_KEY=YOUR_API_KEY

login writes the key to ~/.watahub/config.json. The default base URL is https://cloud.watahub.dev. Override it with WATAHUB_BASE_URL or --base-url.

Commands

pnpm exec watahub setup --origin https://app.example.com
pnpm exec watahub numbers list
pnpm exec watahub messages list
pnpm exec watahub messages send --phone-number-id <id> --to <wa_id> --text 'hola'
pnpm exec watahub webhooks new --url https://hooks.example/wa --secret <32+ chars> \
  --event whatsapp.message.received --phone-number-id <id>
pnpm exec watahub logs search --origin api --errors
pnpm exec watahub templates list [--waba-id <id>]
pnpm exec watahub broadcasts send --phone-number-id <id> --template <name> --language <code> \
  --to <wa_id> [--to ...]

setup only prints a hosted connect URL. It never opens Facebook. setup accepts optional --customer, --success-redirect, --failure-redirect and --connection-type. Without --phone-number-id, webhooks new creates a project webhook. Pass --inactive to create it disabled. logs search accepts --origin and --errors. broadcasts send creates a draft and immediately queues it. The template must already be cached and APPROVED; sync templates first. You can repeat --to for additional recipients. See authentication for how the key is sent, and errors for failed calls.

Getting started

Guides

API reference

Webhook events

Commands

​Commands

Commands