Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getpara.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Install

npm install -g @getpara/cli
Verify the installation: 
para --version
You can also run the CLI without installing globally using npx @getpara/cli@latest, yarn dlx @getpara/cli@latest, or pnpm dlx @getpara/cli@latest.

​
Authenticate

Log in with your Para developer account: 
para login
This opens your browser for OAuth authentication. Once you approve, the CLI stores your session locally at ~/.config/para/credentials.json with restricted file permissions (0600). For headless or CI environments where a browser isn’t available: 
para login --no-browser
This prints a URL you can open on any device to complete authentication. After login, the CLI automatically selects your first organization and project. Use para whoami to verify: 
para whoami

​
Configuration

The CLI resolves configuration from multiple sources in this order (highest priority first):
  1. CLI flags (-e, --org, --project)
  2. Environment variables (PARA_ENVIRONMENT, PARA_ORG_ID, PARA_PROJECT_ID)
  3. Project config (.pararc in the current directory)
  4. Global config (~/.config/para/config.json)
  5. Defaults (key environment: beta)

​
Project-Level Config

Pin your organization, project, and environment to a directory with para init: 
para init
This creates a .pararc file in the current directory. Team members who clone the repo get the same defaults without manual setup. See the config commands page for details.

​
Global Config

Set defaults that apply across all projects: 
para config set defaultEnvironment beta
para config set defaultOrganizationId your-org-id
para config set defaultProjectId your-project-id

​
Key Environment

Each Para project has two API key tiers: beta (for development and testing) and prod (for production). The -e flag selects which tier to operate on: 
para keys list -e beta    # List beta keys (default)
para keys list -e prod    # List prod keys
Key EnvironmentDescription
betaDevelopment and testing keys
prodProduction keys
The default is beta. Most commands auto-resolve the correct API key from your active project and key environment, so you rarely need to pass a key ID explicitly.

​
Global Flags

These flags work with every command:
FlagDescription
-e, --environment <env>Key environment: beta or prod (default: beta)
--jsonOutput as JSON for scripting and CI/CD
-q, --quietSuppress non-essential output
--no-inputDisable interactive prompts (auto-detected in CI)
--org <id>Override the active organization
--project <id>Override the active project

​
Next Steps