Loops CLI

Manage your Loops account from the terminal — send transactional emails, manage contacts, events, mailing lists, and more.

Note

This is beta software. While we're cooking up our first official release there may be breaking changes and other bugs.

Usage

loops [command] [flags]

Run loops --help to see available commands, or loops [command] --help for details on a specific command.

See the docs for comprehensive usage.

Installation

Homebrew

brew install loops-so/tap/loops

Script for macOS, Linux, Windows via WSL

curl -fsSL --proto '=https' --tlsv1.2 https://cli.loops.so | bash

To install a specific version or to a custom path, append -s -- <version> <path> to bash in the command above. The default installation path is ~/.local/bin.

Script for Windows PowerShell

irm https://raw.githubusercontent.com/Loops-so/cli/main/install.ps1 | iex

Go install

go install github.com/loops-so/cli/cmd/loops@latest

Auth

The CLI requires a Loops API key. Get one from Settings > API.

Keyring storage

Store a key with loops auth login --name <name>. Run this again with a different name to store keys for multiple teams.

• loops auth use <name> — set a stored key as the default
• loops auth list — list stored keys and see which is the default

Use --team <name> on any command to pick a specific stored key.

Environment variable

Set LOOPS_API_KEY to use a key directly — useful for CI or when keyring storage isn't available.

Precedence

When multiple keys are available, the CLI resolves them in this order:

1. LOOPS_API_KEY env var
2. --team flag
3. The current default (set via loops auth use)