Skip to main content
The CLI uses your browser to sign you in and securely saves your session, so you never need to enter an API key.

​
Sign in

Your browser opens to complete sign-in. The CLI also prints the sign-in URL in case the browser does not open, and waits up to five minutes for you to approve. Once you approve it, the CLI saves credentials for that subdomain. If you omit --subdomain, the CLI prompts for it.
Your subdomain is the first part of your workspace URL - for https://spinkart.neetoauth.com, the subdomain is spinkart. See Workspace subdomain.

​
Where credentials are stored

Credentials for every signed-in workspace live in a single file:
Removing this file signs you out of every workspace, the same as neetoauth logout --all.

​
Check who you are

Lists every signed-in account. When exactly one is signed in, it is marked (default). Pass --subdomain <name> to show just one.

​
Sign out

​
Working with multiple workspaces

You can sign in to several subdomains at once. To add another workspace, name its subdomain:
When more than one workspace is signed in, every command that talks to the API requires --subdomain. If you omit it, the CLI errors and lists the signed-in workspaces.
With one signed-in workspace, it is the default and --subdomain stays optional.

​
Environment variables

NEETOAUTH_BASE_URL overrides the server the CLI talks to. By default every command, including login, uses https://<subdomain>.neetoauth.com. Set the variable to point the CLI at a staging or local server. Every request, including the session token saved in ~/.config/neetoauth/auth.json, goes to that server, so only point it at a server you trust:

​
What your session can do

A CLI session acts as you, not as the workspace. Commands are checked against your own permissions, so a member who cannot invite people in the NeetoAuth UI cannot invite them through the CLI either. An API key is different: it is not tied to a person and is scoped to the whole workspace.

​
Troubleshooting

If sign-in or connection problems come up, run neetoauth doctor first. See Troubleshooting for common issues and fixes.