Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.lofty.com/llms.txt

Use this file to discover all available pages before exploring further.

lofty-cli is configured through environment variables, on-disk config files, and per-invocation flags. Everything has a sensible default — you only need to override what is relevant to your environment.

Environment variables

VariableRequiredDefaultPurpose
LOFTY_BASE_URLNohttps://api.lofty.comOverride the API host (e.g. for a staging environment)
LOFTY_TOKEN_URLFor Token URL authEndpoint that exchanges a session ID for tokens
LOFTY_SESSION_IDFor Token URL authSession ID submitted to LOFTY_TOKEN_URL
LOFTY_ACCESS_TOKENNoDirect access token (skips other auth methods)
LOFTY_REFRESH_TOKENNoRefresh token paired with LOFTY_ACCESS_TOKEN
LOFTY_CLIENT_IDFor OAuthVendor client ID from the Vendor Portal
LOFTY_CLIENT_SECRETFor OAuthVendor client secret
LOFTY_CUSTOMER_KEYFor OAuthCustomer key for the Lofty user being represented
NO_COLORNounsetDisables ANSI colors (also see --no-color)
DEBUGNounsetSet to any value to mirror --verbose
See Authentication for the full priority order between these variables.

Global flags

These flags are accepted by every command:
FlagEffect
--jsonEquivalent to --format json
--format <fmt>Output format: text (default), json, csv, yaml
--verboseEnable debug logging to stderr (does not pollute stdout)
--no-colorDisable ANSI color in output
--no-headerOmit table / CSV headers — useful when piping
-V, --versionPrint the CLI version
-h, --helpShow help for any command at any depth
See Output formats for examples of each format.

On-disk files

PathManaged byPurpose
~/.config/lofty-cli/customer-keyauth set / auth removePersistent customer key
~/.config/tokens/*.jsonauth login* commandsCached access / refresh tokens
aliases.yaml (in the package)MaintainersMaps short option names to long ones (e.g. -q to --query)
If you want a fully ephemeral run (e.g. inside a container), set every credential via environment variables and never invoke auth set — no files will be written.

Aliases

Many commands accept short option aliases for ergonomics. The full mapping ships inside the package; run a command with --help to see what is available, for example:
lofty-cli leads list --help
Aliases never conflict with long options — you can mix them in the same invocation.

Output character encoding

The CLI emits UTF-8 unconditionally. On Windows terminals, set the code page once per session if your output looks garbled:
chcp 65001

Locking the CLI version

For reproducible automation, install a specific version rather than @latest:
npm install -g @loftyai/lofty-cli@0.3.30
Pinning is especially recommended for CI: a minor version bump can introduce new flags or change defaults.