Skip to main content
The Invopop CLI is a small program you run in your terminal. It lets you do most of what the Console does without opening a browser: check an invoice, send it through a workflow, look up a job, or reserve the next invoice number. It is also the easiest way to let an AI assistant such as Claude Code work in your workspace on your behalf. You don’t need to be a developer to use it. If you can open a terminal and paste a line of text, you can use the CLI.
Terminal window showing the Invopop CLI help screen with the commands access, auth, ping, sequence, silo, skill and transform

The output of invopop --help, listing the available commands

The CLI is open source at github.com/invopop/cli. Everything it does goes through the same public API as the Console, so it can only do what your account is allowed to do.

​
Install

If you have Homebrew, this is the simplest option and keeps the CLI up to date with your other tools.
Homebrew builds the CLI from source the first time, so the install can take a minute.
Check that it worked with invopop --help. You should see the list of commands.

​
Sign in

The login command opens your browser so you can sign in with the same account you use for the Console. The browser then shows a short code to paste back into the terminal, and the CLI asks which of your workspaces to use by default.
From then on every command runs in that workspace with the same permissions you have in the Console. The CLI keeps you signed in for a week and renews its access on its own.
If you belong to several workspaces, name one directly with its slug. Use sandbox/ plus the slug for a sandbox, since live and sandbox workspaces can share a name. To run a single command elsewhere without changing your default, add -w:
Sandbox and live workspaces use exactly the same commands. Check invopop auth status before doing anything in a live workspace.
For scripts that run without a person present, use an API key from the Console instead. Put it in the INVOPOP_TOKEN environment variable or pass it with --token. An API key already belongs to one workspace, so it cannot be combined with -w.

​
Everyday tasks

The CLI works with GOBL documents, the same format the API uses, written in JSON or in YAML. Save this as invoice.yaml to follow along. There are no totals because Invopop calculates them for you.
invoice.yaml
Check a document. This fills in the totals, validates the document against the rules of the country involved and prints the result. Nothing is stored, so run it as often as you like. If something is wrong, such as an invalid tax ID, you get a message saying which field to fix.
Store a document. Every stored document is a silo entry. The response includes an id you’ll need later. Giving the entry a --key of your own, such as the invoice number in your system, lets you find it again by that key and makes the command safe to repeat.
Send it through a workflow. Workflows are the sequences of steps you set up in the Console. List them to find the id you want, then create a job, which runs one entry through one workflow. With --wait, the CLI waits up to that many seconds and shows you the outcome, including a faults list if a step failed. You can also pass --file instead of an entry ID and the CLI stores the document for you.
Download a generated file. Workflows often attach files to the entry, such as the invoice PDF or the XML sent to the tax authority. Fetch the entry to see its files, then download one. This is the one command that writes to disk instead of printing JSON.
Reserve invoice numbers. If Invopop manages your numbering, each call hands out the next unused number in a series.
Results always come back as JSON, so they are easy to read, paste into a support ticket or pass to another tool. Every command accepts --help for the full list of options.

​
Use with AI agents

Because every command is a line of text with JSON output, an assistant such as Claude Code can drive the CLI just as a person would. You describe what you want in plain language and the agent works out which commands to run. The agent never gets a key of its own. It uses your sign-in, so it can only do what you are allowed to do, in the workspace you chose. You stay in charge of logging in: the agent cannot complete the browser sign-in for you and should never ask for the code the browser shows. The CLI ships with a skill that teaches Claude Code how Invopop works. Install it, then type /invopop in Claude Code followed by what you need, for example “check whether invoice.yaml is valid and tell me what’s wrong”.
Start in a sandbox workspace, and ask the agent to run invopop silo build and show you the result before it sends anything. Documents sent from a live workspace are real and may be legally binding.
Any other assistant that can run terminal commands can use the CLI in the same way. Print the skill with invopop skill show and paste it into that tool’s instructions. For agents that call the API directly, see the agent primer.