p202 config test

Test the connection to the Prosper202 instance and that the API key works

All commands

p202 CLI reference

Back to the docs

01Run it

Replace the <placeholders> with your own values, or use the builder below.

p202 config test

02What you get

Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.

p202 config test
$ p202 config test
Connection successful: the key acts as user 1.
api_version:  v3
roles:        ["super user"]
scopes:       ["*"]
status:       healthy
timestamp:    1791540191
user_id:      1
Real output · p202 1.9.77 · demo dataexit 0

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 config test

Set flags below; the command updates as you type.

04How it works

Checks that the instance answers (GET /system/health) and then that it accepts the configured key, and says which user the key acts as (p202 whoami shows more). The health check alone is answered before authentication, so it passed with any key.

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands config test --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
p202 commands config test --json
{
  "path": "p202 config test",
  "use": "test",
  "short": "Test the connection to the Prosper202 instance and that the API key works",
  "long": "Checks that the instance answers (GET /system/health) and then that it accepts the\nconfigured key, and says which user the key acts as (`p202 whoami` shows more).\nThe health check alone is answered before authentication, so it passed with any key.",
  "runnable": true
}