Skip to main content
Start with the health check. It reports authentication, API reachability, and version independently, so one failure does not mask another.

Authentication

Cause: no credentials are stored.Fix: sign in. See Authentication.
Cause: two or more workspaces are signed in, so the CLI cannot pick one for you.Fix: pass --subdomain on the command, or sign out of the ones you do not need.
Cause: --subdomain names a workspace you are not signed in to.Fix: run neetoinvoice whoami to see the signed-in accounts, then use one of those names or sign in to the new one.

Commands and flags

Cause: a required flag was omitted.Fix: check the flag table for that command in the command reference, or read the catalog directly with neetoinvoice commands.
Cause: the installed binary predates it.Fix: upgrade, then refresh completion.
Cause: the completion script on disk was generated by an older binary.Fix: re-run the completion install for your shell and start a new shell. See Shell completion.

Permissions

The CLI acts as the signed-in user, not as the workspace, so commands are limited by what your role allows. A request that a workspace API key would satisfy can still be refused for your account.
Cause: your role does not grant that permission. Viewing other users’ time entries, managing monthly PTO, and overriding autolock are each gated separately.Fix: ask a workspace admin to adjust your role, or run the equivalent REST API call with a workspace API key.
Cause: the entry has been included on an invoice, and billed entries are immutable.Fix: nothing to change on the entry. Adjust the invoice instead.

Connectivity

Cause: the subdomain is wrong, the network is blocking the request, or NEETOINVOICE_BASE_URL points somewhere unreachable.Fix: confirm the workspace subdomain, and unset NEETOINVOICE_BASE_URL if you had pointed the CLI at a local or staging server.

Reading errors

Every command exits non-zero on failure and writes a single line to standard error. Errors raised by the API carry the server’s own message; inspect the JSON envelope, or the --quiet payload, for error, errors, or notice keys.

Still stuck?

Visit the help center, email support@neetoinvoice.com, or join the Neeto Community.