`bullpen polymarket clob create-api-key`¶

Last updated: July 13, 2026

Create or derive API key credentials for the authenticated wallet (authenticated).

Usage¶

bullpen polymarket clob create-api-key [OPTIONS]

Live Help¶

Create or derive API key credentials for the authenticated wallet (authenticated).

If Polymarket blocks `/auth/api-key` with Cloudflare 403, falls back to `/auth/derive-api-key` and prints an actionable recovery message.

Usage: bullpen polymarket clob create-api-key [OPTIONS]

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --yes
          Confirm API-key creation or derivation

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --config <CONFIG>
          Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).

          Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.

      --read-only
          Enable read-only mode: blocks all mutating commands

      --non-interactive
          Suppress interactive prompts; does NOT imply --yes for money-moving commands

          [env: BULLPEN_NON_INTERACTIVE=]

  -h, --help
          Print help (see a summary with '-h')

EXAMPLES:
  # Review existing API keys first
  bullpen polymarket clob api-keys

  # Review the credential-creation flow without creating credentials
  bullpen polymarket clob create-api-key --help

Example Commands¶

bullpen polymarket clob api-keys
bullpen polymarket clob create-api-key --help

JSON Output¶

Contract: JSON Output Contract.

This command supports --output json, but this generated reference page intentionally does not include a synthetic success schema or example.

Use the live command in your target environment to inspect command-specific success fields. Error output follows the shared JSON output contract linked above.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Stability¶

Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.