Authentication¶

Alegra authenticates API requests with HTTP Basic auth: your account email as the username and an API token as the password. The CLI encodes these as Authorization: Basic base64(email:token). (Marketplace apps can instead use an OAuth bearer token via ALEGRA_BEARER_TOKEN.)

Get your API token¶

Sign in to Alegra.
Go to Configuración → Integraciones → API.
Copy your token (and the email associated with the account).

Option 0: `alegra init` (easiest first run)¶

alegra init

Prompts for your email and token, verifies them, auto-detects your country (used for pre-flight validation), and saves a profile — all in one step. On both init and auth login the CLI reads /company and caches the country, so country-specific behavior works automatically.

Option 1: `alegra auth login`¶

alegra auth login
# Alegra email: you@example.com
# Alegra API token: ********

Your email is saved to ~/.alegra-cli/config.yaml; the token is stored in your operating system keyring (macOS Keychain, Linux Secret Service, Windows Credential Manager) — never written to disk in plaintext.

Option 2: environment variables¶

Ideal for CI and scripts:

export ALEGRA_EMAIL="you@example.com"
export ALEGRA_TOKEN="your-api-token"

Environment variables take precedence over the config file and keyring.

Verify¶

alegra auth status

This calls GET /users/self and prints the active profile, base URL, and the authenticated user.

Multiple accounts¶

Use profiles to switch between Alegra accounts.