Troubleshooting

Resolve common Saber CLI authentication, API-key, network, JSON output, and rate-limit issues during local or CI usage.

`saber` is not found

Make sure the install directory is on your PATH.

export PATH="$HOME/go/bin:$PATH"

If you installed with the curl installer, open a new terminal session and run:

saber version

Run:

saber auth login
saber auth status

If auth status still fails, create a fresh API key in Saber and log in again.

Use async mode and poll later:

saber signal -d acme.com -q "What changed recently?" --no-wait
saber signal get <signalId>

For larger runs, use saber signal batch --async and process results by ID or webhook.

Use count-preview before create, especially with technology or broad geography filters.

saber list company count-preview --technology hubspot --country US --size "51-200"

Add --json when a script, CI job, or agent needs stable machine-readable output.

saber credits --json
saber signal get <signalId> --json