Skip to main content

​
Run the doctor

When something goes wrong, start with neetoauth doctor. It checks your authentication, API connection, and CLI version.
When multiple workspaces are signed in, name the one to check:

​
Common errors

When a command fails, it prints an error message to standard error and exits with status 1. Usage errors such as an unknown flag or a missing argument add Run 'neetoauth --help' for usage.
Problem: no workspace is signed in.
Solution: run neetoauth login --subdomain <name>.
Problem: more than one workspace is signed in, so the target is ambiguous.
Solution: add --subdomain <name> to the command. For logout, --all signs out of every workspace.
Problem: the --subdomain value does not match any signed-in workspace.
Solution: use one of the listed subdomains, or sign in to the new one.
Problem: neetoauth login could not find a workspace at <subdomain>.neetoauth.com.
Solution: use the first part of your workspace URL. For https://spinkart.neetoauth.com, enter spinkart.
Problem: the browser sign-in was not approved before the session expired. NeetoAuth CLI authentication timed out after 5 minutes. Please try again. means the CLI stopped waiting.
Solution: run neetoauth login again and approve the sign-in in the browser. If the browser does not open, visit the URL the CLI prints.
Problem: the CLI could not reach the API.
Solution: check your network and run neetoauth doctor. If NEETOAUTH_BASE_URL is set, confirm it points at a reachable server.
Problem: a required flag was omitted.
Solution: check the command’s reference page or run neetoauth <command> --help for the required flags. For commands that accept --json-file, a key in the file satisfies the matching flag.
Problem: the --json-file path does not exist, is not readable, or does not contain a JSON object.
Solution: check the path and validate the file, for example with jq . <path>.
Problem: users create ran without an email address.
Solution: pass --email <address>, or supply it in the file given to --json-file.
Problem: users create ran without an organization role.
Solution: pass --role owner or --role non_owner. This is the organization-level role, not a product role.
Problem: an --app value is missing the role half.
Solution: write it as name:role, for example --app Cal:Admin. Run neetoauth products list to see the valid pairs.
Problem: products enable or products disable was given a name that is not a product in the workspace.
Solution: use the name shown by neetoauth products list. Names are matched without regard to case.
Problem: the server rejected the request. The CLI prints API error (<status>): <message>, one line per additional error, and a Suggestion: line for common statuses: 401 (sign in again), 403 (no permission), 404 (check the ID), 422 (check required fields with --help), and 429 (rate limited, wait and retry).
Solution: follow the suggestion. For 401, run neetoauth login to refresh the session. A 422 usually means the person is already an active member, an --app product or role is not offered in the workspace, or the removal would leave the workspace without an owner.
Problem: neetoauth setup claude requires Claude Code to have been run at least once.
Solution: install and open Claude Code, then run the command again.

​
Permission errors

The CLI acts as the person who signed in, so commands are checked against your own permissions. A command you are not allowed to run fails with API error (403) and the suggestion You do not have permission to perform this action. Ask a workspace owner to grant you the permission, or use an API key against the REST API instead. Enabling or disabling products needs permission to manage workspace settings.

​
Check the version

Prints the CLI version, commit hash, and build date - useful when reporting an issue. To upgrade, run neetoauth update.