Skip to main content
With Plerion CLI configuration, you can manage credentials, profiles, regions, and output preferences. The CLI resolves settings from multiple sources in order of precedence (highest first):
  1. CLI flags (--api-key, --region, --endpoint-url)
  2. Environment variables (PLERION_API_KEY, PLERION_REGION, etc.)
  3. Named profile from config files (selected via --profile or PLERION_PROFILE)
  4. [default] profile from config files

​
Getting an API key

1

Sign in to Plerion

Go to the Plerion dashboard and sign in with your credentials.
2

Navigate to API Keys

Go to Settings > API Keys.
3

Create a key

Click Create API Key, give it a name, and copy the key. You will not be able to see it again.

​
Interactive setup

plerion configure
This prompts for your API key, region, output format, and profile name, then writes both config files. 
plerion configure list
Lists all configured profile names.

​
Credentials file

Location: ~/.plerion/credentials 
[default]
api_key = pk_live_xxxxxxxxxxxxxxxx

[prod]
api_key = pk_live_yyyyyyyyyyyyyyyyyy

[staging]
api_key = pk_live_zzzzzzzzzzzzzzzzzz

​
Config file

Location: ~/.plerion/config 
[default]
region = au
output = table

[prod]
region = us1
output = json

[staging]
region = sg1
output = table
Both files use bare section names (e.g. [prod], not [profile prod]).

​
Environment variables

VariableDescription
PLERION_API_KEYAPI key (overrides credentials file)
PLERION_REGIONRegion (overrides config file)
PLERION_PROFILEProfile name (default: default)
PLERION_ENDPOINT_URLCustom API base URL (for development)
NO_COLORSet to any value to disable color output

​
Regions

RegionCodeBase URL
Australiaauhttps://au.api.plerion.com
Singaporesg1https://sg1.api.plerion.com
Indiain1https://in1.api.plerion.com
United Statesus1https://us1.api.plerion.com

​
Multiple profiles

# Use a named profile for a single command
plerion --profile prod findings list --severity CRITICAL

# Set the default profile for the session
export PLERION_PROFILE=prod
plerion findings list