Skip to content

splashifypro/cli

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

splashify CLI

Connect a Splashify messaging account to OpenClaw (the local-first AI assistant — https://github.com/openclaw/openclaw) so the assistant can perform every app action — send WhatsApp/RCS messages, manage contacts, run broadcasts, edit templates, read analytics — on the user's behalf.

How it fits together

Two products share one oc_live_ access token and one splashify binary:

  • the splashify CLI — a standalone tool that calls the Splashify Pro API directly. No assistant required.
  • the Splashify OpenClaw skill — a SKILL.md bundle (in openclaw-skill/, embedded into the binary) that teaches the OpenClaw assistant to drive the CLI on your behalf.
OpenClaw ──exec──► splashify CLI ──HTTPS, Bearer oc_live_──► backend /api/v1/app/*

The CLI does two things: run every app task itself, and install the Splashify skill into OpenClaw (splashify link openclaw). The skill carries no credentials of its own — it reads the same ~/.splashify/config.json through the CLI it drives.

Build

go build -o splashify ./...

Put splashify on your PATH. The OpenClaw skill bundle is embedded into the binary, so there is nothing else to build or download.

Connect

# Connect this machine. Paste an oc_live_ token from the app
# (Settings → Developer → Access Tokens), or create one here:
splashify connect

splashify token create --name "OpenClaw on laptop"   # mint a token
splashify token list                                 # see your tokens
splashify token revoke <id>                           # kill a token

splashify whoami        # show the connected account
splashify doctor        # diagnose config / token / WABA / openclaw / skill

Config is stored at ~/.splashify/config.json (mode 0600) — it holds the backend URL and the oc_live_ token, so treat it like a password file.

Do everything from the command line

Once connected, the CLI can perform every app task directly — no OpenClaw required. Every command prints the backend's JSON response.

Messaging

splashify message send --to +919876543210 --text "Your order has shipped"
splashify message template --to +919876543210 --name order_update \
  --lang en --vars '["John","ORD-1024"]'
splashify message media --to +919876543210 --type image \
  --url https://example.com/receipt.png --caption "Receipt"

splashify conversations --status open          # list chats
splashify conversation <id>                    # read one chat
splashify conversation <id> resolve            # close a chat
splashify unread                               # unread count

Contacts

splashify contacts --search john --tag vip
splashify contact <id>
splashify contact create --phone +919876543210 --name "John Roe" --email john@x.com
splashify contact tag <id> --tags vip,lead
splashify contact block <id>
splashify contact unblock <id>
splashify contact delete <id>

Broadcasts, templates, analytics, wallet

splashify broadcasts
splashify broadcast <id>
splashify broadcast stats
splashify broadcast create --name "May Sale" --template may_offer \
  --audience-type segment --audience-id <segment-id> --schedule 2026-06-01T10:00:00Z

splashify templates
splashify analytics            # message analytics summary
splashify analytics trends
splashify wallet               # balance
splashify wallet transactions

Everything else — the generic api command

Any /api/v1/app/* endpoint is reachable directly, so the CLI covers the full app surface (segments, AI agents, team, tickets, WABA setup, …):

splashify api GET  /app/segments
splashify api GET  "/app/contacts?page=2&page_size=50"
splashify api POST /app/messages/send-text --data '{"phone":"+919876543210","message":"hi"}'
splashify api POST /app/ai-agents --data '{"name":"Support Bot"}'
splashify api DELETE /app/contacts/<id>

The path may be given with or without the /api/v1 prefix. Use --data to pass a JSON request body for POST/PUT/PATCH.

Connect Splashify Pro with OpenClaw

To let the OpenClaw AI assistant drive your account in natural language, install the Splashify skill into OpenClaw:

# 1. install OpenClaw
npm install -g openclaw@latest && openclaw onboard --install-daemon

# 2. connect this machine (if not already done)
splashify connect

# 3. install the Splashify skill into OpenClaw
splashify link openclaw            # writes the bundle to ~/.openclaw/workspace/skills/splashify/
splashify link openclaw --print    # or just show the target path without writing

# 4. restart OpenClaw so it picks up the skill, then confirm
openclaw dashboard
splashify doctor                   # all checks should be ✓

splashify link openclaw installs the Splashify skill bundle — a SKILL.md that teaches OpenClaw which splashify command maps to each task. The bundle is embedded in the binary, so no extra download is needed; pass --path <dir> to install into a non-default skills directory.

Upgrading from the old MCP integration? Earlier versions connected through an MCP server (splashify-mcp, splashify mcp-config). That path has been replaced by the skill. Remove the old server with openclaw mcp remove splashify.

Then ask your assistant things like "send a WhatsApp to +91… saying the order shipped" or "list my VIP contacts" — it performs them on your account.

Full step-by-step connect + usage guide: https://docs.splashifypro.com/openclaw

Run splashify help for the full command list.

Token model

  • oc_live_ tokens are long-lived credentials accepted on every /api/v1/app/* route as an alternative to the session JWT.
  • The raw token is shown once at creation; only its SHA-256 hash is stored.
  • Revoke from splashify token revoke, the app UI, or the API — revocation is immediate.
  • A token resolves to the account owner; it never grants admin/reseller access.

About

Official command-line interface for Splashify Pro — control your WhatsApp Business account from any terminal.

Topics

Resources

License

Stars

Watchers

Forks

Contributors