Install the splashify CLI
The splashify CLI is a single binary that lets you drive every part of your
Splashify Pro account — sending messages, managing contacts, running
broadcasts, pulling analytics — from a terminal on your laptop or VPS.
You do not need Go, npm, or any other toolchain to install it.
Prerequisites
| You need | Notes |
|---|---|
| A Splashify Pro account | With an active trial or paid plan. |
| A connected WhatsApp Business Account | Required — the CLI refuses to connect until one is linked. Set it up at app.splashifypro.com → WhatsApp → Connect Number. |
An oc_live_ access token | Created in the app — see Access Tokens. |
Step 1 — Install
Pick the one-liner for your OS. It downloads the latest release, verifies the
checksum, and drops splashify onto your PATH.
Linux / macOS
curl -fsSL https://raw.githubusercontent.com/splashifypro/cli/main/install.sh | shThe script installs to /usr/local/bin/splashify (using sudo if needed) or
falls back to ~/.local/bin/splashify when there’s no write access.
Pin to a specific version with SPLASHIFY_VERSION=v0.1.0; install elsewhere
with SPLASHIFY_INSTALL_DIR=/opt/bin.
Windows (PowerShell)
iwr -useb https://raw.githubusercontent.com/splashifypro/cli/main/install.ps1 | iexInstalls to %USERPROFILE%\.splashify\bin\splashify.exe. The script prints a
setx PATH … line if the directory isn’t on your PATH yet.
Verify
splashify versionStep 2 — Create an access token
In Splashify Pro, open Settings → Developer → Access Tokens & OpenClaw,
click New Token, name it (e.g. “my VPS”), and copy the oc_live_…
value — it is shown only once.
You can also create tokens from the CLI after connecting — see Access Tokens.
Step 3 — Connect your account
splashify connectIt prompts for:
- the Backend URL —
https://api.splashifypro.com(press Enter to accept) - your
oc_live_token — paste it
The CLI:
- Validates the token.
- Checks that your account has a connected WhatsApp Business Account.
- Saves your config to
~/.splashify/config.json(mode0600— treat it like a password file).
No WABA yet? The connect command refuses with a clear message pointing you to Meta Embedded Signup. Finish that flow, then try again.
Confirm:
splashify whoamiStep 4 — Verify
splashify doctorYou should see:
✓ config — found
✓ access token — valid (you@example.com)
✓ waba — connectedYou are ready — see the command reference or jump straight to a first task:
splashify message send --to +919876543210 --text "Hello from my VPS"Updating
Re-run the same one-liner. The script overwrites the binary in place; your
~/.splashify/config.json is preserved, so you do not need to reconnect.
The CLI also nudges you with a one-line hint after any command when a newer
version is available. Set SPLASHIFY_NO_UPDATE_CHECK=1 to suppress the hint.
From source (advanced)
If you want to build from a local checkout instead of downloading a release:
git clone https://github.com/splashifypro/cli
cd cli && go build -o splashify ./...Requires Go 1.23+. Place the resulting splashify binary on your PATH.
Everything else (connect, tokens, commands) works identically.
Next
- Commands — the full command reference.
- Access Tokens — manage
oc_live_tokens. - OpenClaw skill — drive these commands from an AI assistant.