p202 user apikey rotate

Rotate an API key by creating a new one and optionally deleting the old one

Writessupports --staged
All commands

p202 CLI reference

Back to the docs

01Run it

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

p202 user apikey rotate <user_id> <old_api_key>

02What you get

Pick the shape you need. People get a table. Add --json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats

03Build your command

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

p202 user apikey rotate

Set flags below; the command updates as you type.

04Flags

5 flags, plus the global flags every command takes.

FlagWhat it does
--force, -fboolSkip confirmation prompt when deleting old key
--force-config-updateboolUpdate local config even if current key does not match old key
--keep-oldboolDo not delete the old API key
--scopestringScope for the replacement key (default: the old key's scope, carried over)
--update-configboolUpdate local ~/.p202/config.json with the new API key

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands user apikey rotate --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.
  • This command writes. Add --staged to record it as a proposal a person applies with p202 change apply.
p202 commands user apikey rotate --json
{
  "path": "p202 user apikey rotate",
  "use": "rotate <user_id> <old_api_key>",
  "short": "Rotate an API key by creating a new one and optionally deleting the old one",
  "runnable": true,
  "flags": [
    {
      "name": "force",
      "shorthand": "f",
      "type": "bool",
      "default": "false",
      "usage": "Skip confirmation prompt when deleting old key",
      "required": false
    },
    {
      "name": "force-config-update",
      "type": "bool",
      "default": "false",
      "usage": "Update local config even if current key does not match old key",
      "required": false
    },
    {
      "name": "keep-old",
      "type": "bool",
      "default": "false",
      "usage": "Do not delete the old API key",
      "required": false
    },
    {
      "name": "scope",
      "type": "string",
      "default": "",
      "usage": "Scope for the replacement key (default: the old key's scope, carried over)",
      "required": false
    },
    {
      "name": "update-config",
      "type": "bool",
      "default": "false",
      "usage": "Update local ~/.p202/config.json with the new API key",
      "required": false
    }
  ]
}