CLI

slashbin-cli is a thin client over the same console REST API the web UI calls, so the terminal and the console always report the same data — there is no second source of truth to reconcile. The commands that operate your pipeline are authenticated calls to that API. Reading and switching profiles, and inspecting the contract, are local; slashbin profile add is the exception — it checks the key against the console before storing it.

It exists for two audiences: engineers who would rather stay in a terminal than click through a browser, and AI agents operating Slashbin on someone's behalf, which need a scriptable surface with a stable way to authenticate.

Install

npm install -g slashbin-cli

It requires Node 20 or newer, and installs a binary named slashbin on your PATH.

Confirm the install:

slashbin --version

Sign in

The default is a browser flow — you never paste a key:

slashbin login

It prints an authorization URL and a pairing code, opens your browser to that URL, and waits. Check that the code shown in the browser matches the one in your terminal, approve it, and the console mints an API key that the CLI writes to your profile.

--browserless skips opening the browser; the URL and the pairing code print either way, so this is the flag to use over SSH or anywhere the CLI cannot launch a browser for you.

For CI and other non-interactive contexts, set the key in the environment instead:

SLASHBIN_API_KEY=slashbin_sk_... slashbin data-streams list

Or write a key you already have into a profile once:

slashbin login --key <key>

Where to get an API key

API keys live in the console at console.slashbin.io/account/api-keys (opens in a new tab). slashbin login creates one for you automatically, so you only need to mint one by hand for CI or for a deliberate paste. A key is shown once, at creation — copy it then, because the console will not show it again.

Check which identity you are using at any point:

slashbin whoami

Profiles

Credentials live per profile under ~/.slashbin/. Run slashbin profile to manage more than one — a profile per organization, say, or one for dev and one for prod. --profile <name> selects one for a single command, and SLASHBIN_API_URL overrides the console host for a single invocation.

What you can run

slashbin --help

Some of the command groups are generated from the console's published contract and move with it, which is why they are not reproduced here — a copy on this page would drift the moment a new operation ships. slashbin --help is the authoritative list, and slashbin <command> --help gives the flags on any one of them.

Machine-readable output

Most commands accept --json, which replaces the human-formatted output with the raw API response — the shape a script or an agent can consume without parsing a table.

slashbin data-streams list --json

It is a per-command flag, not a global one, so it goes after the command: slashbin data-streams list --json, not slashbin --json data-streams list. A handful of commands do not accept it and will reject it — slashbin <command> --help is the authority on whether a given command takes the flag.

From the terminal instead of the console

• Webhook debugging — slashbin logs <data-stream-id> is the delivery log without the browser.
• Replay — slashbin replay <data-stream-id> re-delivers a webhook from a terminal.
• Retry — inspect and re-drive failures without opening the console.
• Transform — slashbin transform gets, tests and publishes a model from a script.