WhatsApp

These commands wrap the /v1/whatsapp/* API. Scope is intentionally narrow — template lifecycle plus outbound template sending. WABA connection is browser-only (OAuth) and remains in the dashboard.

All commands accept either the internal social account UUID (from accounts:list) or the Meta WABA provider ID in the <account-id> position. The v1 controller resolves UUIDs to provider IDs server-side.

whatsapp:templates

List every template registered on a WhatsApp Business account, including status (APPROVED, PENDING, REJECTED), category, language, and component structure.

so-me whatsapp:templates <account-id>

Argument	Description
`<account-id>`	WhatsApp social account UUID (from `accounts:list`) or Meta WABA provider ID (required)

Examples

# Full list
so-me whatsapp:templates e6be46a2-430a-41df-b180-b51527e954e3

# Only approved templates
so-me whatsapp:templates e6be46a2-... | jq '.data[] | select(.status == "APPROVED")'

# Just names + status as a table-ish view
so-me whatsapp:templates e6be46a2-... | jq -r '.data[] | "\(.status)\t\(.name)\t\(.language)"'

# Pass provider ID instead of UUID
so-me whatsapp:templates 1050417321480811

whatsapp:create-template

Submit a new template to Meta for approval. Templates can take minutes to hours to approve; poll whatsapp:templates to see the status transition from PENDING → APPROVED.

so-me whatsapp:create-template --account <id> (--file <path> | --data <json>)

Option	Description
`--account <id>`	WhatsApp account UUID or provider ID (required)
`-f, --file <path>`	JSON file with the full template definition
`-d, --data <json>`	JSON string with the full template definition

Provide the template definition with either --file or --data (if both are passed, --file wins; if neither is passed, the command errors). The payload matches Meta’s WhatsApp Cloud API schema. Minimum fields:

name — lowercase, underscored
language — e.g. en_US
category — MARKETING, UTILITY, or AUTHENTICATION
components[] — HEADER, BODY, FOOTER, BUTTONS

The CLI merges accountId (from --account) into the payload before submitting, so you do not need to include it in the JSON.

{
  "name": "order_shipped",
  "language": "en_US",
  "category": "UTILITY",
  "components": [
    { "type": "HEADER", "format": "TEXT", "text": "Order update" },
    { "type": "BODY", "text": "Hi {{1}}, your order #{{2}} has shipped." },
    { "type": "FOOTER", "text": "Thanks for shopping with us!" }
  ]
}

Examples

# From a file
so-me whatsapp:create-template --account e6be46a2-... --file ./order_shipped.json

# Inline
so-me whatsapp:create-template --account e6be46a2-... --data '{
  "name": "welcome_v1",
  "language": "en_US",
  "category": "MARKETING",
  "components": [{ "type": "BODY", "text": "Welcome, {{1}}!" }]
}'

Template names must be lowercase alphanumeric with underscores (^[a-z0-9_]+$). Meta validates this — mismatched names reject immediately with 400.

whatsapp:delete-template

Permanently delete a template. Once deleted, it cannot be restored; you must re-submit under a new name.

so-me whatsapp:delete-template <account-id> <template-name> [-y]

Argument	Description
`<account-id>`	WhatsApp social account UUID or provider ID (required)
`<template-name>`	Template name (`lowercase_underscored`) (required)

Option	Description
`-y, --yes`	Skip the confirmation prompt

Without -y, the command prompts Delete template "<name>" on account <id>? (y/N) and aborts unless you answer y.

Examples

# With confirmation
so-me whatsapp:delete-template e6be46a2-... old_template

# Skip prompt
so-me whatsapp:delete-template e6be46a2-... old_template -y

# Delete every REJECTED template (careful)
so-me whatsapp:templates e6be46a2-... \
  | jq -r '.data[] | select(.status == "REJECTED") | .name' \
  | xargs -I {} so-me whatsapp:delete-template e6be46a2-... {} -y

whatsapp:send

Send an approved template message to a recipient. This is the primary way to initiate a WhatsApp conversation outside the 24-hour customer-service window.

so-me whatsapp:send <account-id> --to <phone> --template <name> --language <code> [--components <json>]

Argument	Description
`<account-id>`	WhatsApp social account UUID or provider ID (required)

Option	Description
`--to <phone>`	Recipient in E.164 format (e.g. `+15551234567`) (required)
`--template <name>`	Name of an APPROVED template (required)
`--language <code>`	Language code (e.g. `en_US`, `es`, `pt_BR`) (required)
`--components <json>`	Template parameters as an inline JSON string
`--file <path>`	Template parameters from a JSON file

--components and --file are both optional (a template with no variables needs neither). If both are supplied, --file takes precedence. Component parameters fill variables ({{1}}, {{2}}, etc.) in the approved template. Shape matches Meta’s Cloud API:

[
  {
    "type": "body",
    "parameters": [
      { "type": "text", "text": "Alice" },
      { "type": "text", "text": "1234" }
    ]
  }
]

Examples

# Template with no variables
so-me whatsapp:send e6be46a2-... \
  --to +15551234567 --template welcome_v1 --language en_US

# Template with body variables
so-me whatsapp:send e6be46a2-... \
  --to +15551234567 --template order_shipped --language en_US \
  --components '[{"type":"body","parameters":[{"type":"text","text":"Alice"},{"type":"text","text":"ORD-1234"}]}]'

# Parameters from a file (easier for complex components)
so-me whatsapp:send e6be46a2-... \
  --to +15551234567 --template order_shipped --language en_US \
  --file ./order_components.json

# Broadcast loop (be mindful of Meta's messaging rate limits)
while read -r phone name; do
  so-me whatsapp:send e6be46a2-... \
    --to "$phone" --template welcome_v1 --language en_US \
    --components "[{\"type\":\"body\",\"parameters\":[{\"type\":\"text\",\"text\":\"$name\"}]}]"
done < recipients.tsv

Sending templates is billed per Meta’s WhatsApp Business pricing. Always test with a single recipient first. Unapproved or rejected templates will fail with 400.

whatsapp:upload-media

Upload header media (image/video/document) for use inside a template’s HEADER component. Returns a media handle you can reference when creating or sending templates.

so-me whatsapp:upload-media --account <id> --type <fileType> (--url <url> | --base64 <content>)

Option	Description
`--account <id>`	WhatsApp account UUID or provider ID (required)
`--type <fileType>`	File type: `image`, `video`, or `document` (required)
`--url <url>`	Public URL of the media to upload
`--base64 <content>`	Base64-encoded file contents (alternative to `--url`)

Provide exactly one of --url or --base64 — the command errors if you supply neither or both.

Examples

# From a public URL
so-me whatsapp:upload-media \
  --account e6be46a2-... --type image \
  --url https://cdn.example.com/hero.jpg

# From a local file (base64-encoded)
so-me whatsapp:upload-media \
  --account e6be46a2-... --type image \
  --base64 "$(base64 -w0 ./hero.jpg)"

Bigger picture

Session messages (replies within 24 hours of an inbound message) go through inbox:reply — no template required.
Template messages (first-contact or outside the 24-hour window) use whatsapp:send and require a Meta-approved template.
Connecting a WhatsApp Business Account is still browser-only — complete OAuth in the dashboard first, then your CLI scripts can reference the connected account.

Getting Started

Publishing

AI Studio

Inbox & Engagement

Analytics

Biolink

Team & Collaboration

Settings & Billing

Webhooks

Support

whatsapp:templates

whatsapp:create-template

whatsapp:delete-template

whatsapp:send

whatsapp:upload-media

Bigger picture

​whatsapp:templates

​whatsapp:create-template

​whatsapp:delete-template

​whatsapp:send

​whatsapp:upload-media

​Bigger picture

whatsapp:templates

whatsapp:create-template

whatsapp:delete-template

whatsapp:send

whatsapp:upload-media

Bigger picture