Authentication

Verlign uses browser-based authentication. When you log in, a short-lived local server handles the OAuth callback and stores your API key.

Log in

verlign login

This command:

1. Starts a temporary local server on a free port
2. Opens https://verlign.com/cli-auth in your browser
3. Waits up to 2 minutes for you to complete authentication
4. Stores your API key in ~/.verlign/config.json (permissions 0600)

Once authenticated, all subsequent CLI commands use the stored key automatically.

Log out

verlign logout

This removes the stored API key from ~/.verlign/config.json.

Check status

verlign status

Displays whether you are logged in and shows:

• A truncated API key (first 12 characters)
• The API URL your CLI is pointing to

API keys on the dashboard

You can also manage API keys from the Verlign dashboard. Keys created on the dashboard can be used by setting them in your config file or via environment variables (see Configuration).

Troubleshooting

Login times out

The CLI waits 2 minutes for the browser callback. If your browser didn’t open automatically, copy the URL printed in your terminal and open it manually.

“Not logged in” after login

Make sure ~/.verlign/config.json exists and contains a valid apiKey field. Check file permissions — the file should be readable by your user (0600).