WandStore CLI

The WandStore CLI (wand) drives your store from the terminal. Everything the WandStore dashboard does through its public API — campaigns, cohorts, generated experiences, standalone emails, and analytics — is available as a command you can run, script, or wire into automation.

It is an optional power-user tool. You never need the CLI to use WandStore; the Shopify app covers the full workflow. Reach for wand when you want to script repetitive work, pull analytics into your own tooling, or manage campaigns from a deploy pipeline.

Who this is for

The CLI is aimed at developers and technical operators. If you only manage your store from Shopify admin, you can skip this page — see Studio and Campaigns instead.

Install

The CLI is published on npm and runs on Node.js 20 or newer.

npm install -g @wandstore/cli
wand --help

The package is a single self-contained bundle with no extra dependencies. To upgrade later, run npm install -g @wandstore/cli@latest.

Get an API token

Every command authenticates with a per-store API token. The token pins all commands to one store, so no command ever takes a store name.

1. In Shopify admin, open Apps > WandStore > Settings > API tokens.
2. Click Create token, give it a name, and copy it.
3. The token looks like wand_<store>_<secret> and is shown once — store it somewhere safe.

Treat tokens like passwords

A token grants full API access to your store’s WandStore data. Don’t commit it to source control or share it. If a token leaks, delete it in Settings > API tokens and create a new one.

Log in

wand login          # prompts for your token, verifies it live, then saves it
wand auth status    # shows the active store, credential source, and onboarding state
wand logout         # forgets the saved token

wand login saves the token to ~/.wandstore/config.json (readable only by your user). Once you’re logged in, commands just work — no need to pass the token each time.

By default the CLI talks to https://api.wand-store.com. You normally don’t change this.

First commands

wand ping                          # liveness check (no token needed)
wand store billing                 # current plan and generation usage this period
wand store settings                # your non-secret store settings
wand store analytics experiences   # performance rollups for every experience

Add --json to any command to get the raw response for scripting, and --help to any command to see its options.

What you can do

Command group	What it covers
wand onboarding	Guided store setup from the terminal — connect, accept AI data consent, and finish setup. Mirrors the dashboard setup guide; anything done in the app is skipped.
wand store …	Read plan and billing usage, store settings, and analytics rollups for experiences and campaigns.
wand campaigns …	List, create, update, approve, and launch campaigns; pull every email asset version and the campaign-to-cohort map.
wand cohorts …	Create and manage audiences — manual lists, Shopify tag cohorts, and AI smart cohorts.
wand experiences …	List experiences and versions, promote a draft live, roll back to a prior version, or archive.
wand emails …	Generate, review, promote, and send standalone marketing emails.

Run wand <group> --help to see every command in a group, or wand --help for the full list.

Onboarding from the terminal

If you’d rather set up a store without the dashboard, wand onboarding walks through the same required steps — connecting your token, accepting the AI data-processing agreement, and marking setup complete. Setup state lives on the store, so onboarding done in the app counts here too, and vice versa.

wand onboarding         # interactive
wand onboarding --yes   # accept every step (useful in scripts/CI)

Adding the WandStore theme blocks still happens in the Shopify Theme Editor — see Adding App Blocks.

Scripting and automation

For CI or scripts, skip the saved config file and pass credentials through the environment. The CLI resolves credentials in this order (first match wins):

Priority	Base URL	Token
1	--api-url flag	--token flag
2	$WANDSTORE_API_URL	$WANDSTORE_API_TOKEN
3	~/.wandstore/config.json	same file
4	the default WandStore API	— (prompts you to log in)

A typical CI step:

export WANDSTORE_API_TOKEN="wand_yourstore_…"
wand campaigns list --json | jq '.[] | {id, status}'

Combine --json with a tool like jq to pull WandStore data into dashboards, reports, or scheduled jobs.

Shell completions

Generate tab-completions for your shell with wand --completions zsh (also bash, fish, and sh).

Related pages

• Quick Start Guide - The fastest path from install to a live experience in the app.
• Dashboard & Settings - Where to mint API tokens and manage your store.
• Campaigns - Plan and launch AI campaigns (also drivable with wand campaigns).
• Audiences - Build cohorts in the app (also drivable with wand cohorts).
• Analytics - Understand the performance signals wand store analytics returns.