`bullpen polymarket redeem`¶

Last updated: July 13, 2026

Redeem resolved prediction market positions

Usage¶

bullpen polymarket redeem [OPTIONS]

Live Help¶

Redeem resolved prediction market positions

Usage: bullpen polymarket redeem [OPTIONS]

Options:
      --address <ADDRESS>
          Support override for a specific Polymarket wallet route. Omit for normal use so the CLI auto-discovers redeemable positions across the selected account wallet route

      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --condition-ids <CONDITION_IDS>
          Condition IDs to redeem (comma-separated)

      --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.

      --limit <LIMIT>
          Limit auto-discovered redeem candidates. Use --condition-ids for exact targeting

      --collateral <COLLATERAL>
          Collateral token address override for unusual support cases. Defaults to automatic relayer-path detection; only supply this flag if support asks for it

      --index-sets <INDEX_SETS>
          Index sets to redeem as comma-separated integers (defaults to [1,2] for binary markets; use e.g. 1,2,4 for 3-outcome markets)

      --yes
          Skip confirmation prompt

      --no-preflight
          Skip only the early CLI payoutDenominator UX check; the core zero-payout guard still blocks known zero-payout redeems

      --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=]

      --dry-run
          Print the redeem submission plan, then exit without submitting. Useful for support diagnostics: run with --dry-run and share the JSON output with Bullpen support. Dry-run does not submit, but it should still be treated as the plan evidence for wallet route and condition selection

      --support-bundle
          Build a no-submit support bundle as JSON. This is stricter than a normal dry-run: it does not enter the deploy-capable wallet-ready path, request signatures, call the signing server, or submit to the relayer/exchange

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

EXAMPLES:
  # Preview the bounded auto-discovered redeem plan
  bullpen polymarket redeem --dry-run --output json

  # Preview the first 20 auto-discovered redeemable positions
  bullpen polymarket redeem --limit 20 --dry-run --output json

  # Preview redeeming a specific condition ID
  bullpen polymarket redeem --condition-ids 0xYourConditionId --dry-run --output json

  # Build a no-submit support bundle for an affected condition
  bullpen polymarket redeem --condition-ids 0xYourConditionId --support-bundle --output json

  # Submit redeem for a specific condition ID after confirmation is bypassed
  bullpen polymarket redeem --condition-ids 0xYourConditionId --yes

--support-bundle uses only cached auth. It does not refresh tokens, start
device login, build signing clients, call Bullpen account services for wallet-ready state, or
write wallet/auth cache. If cached auth is unavailable, run
bullpen doctor auth --refresh --output json first; run bullpen login only if
auth diagnostics report that login is required.

Example Commands¶

bullpen polymarket redeem --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.

Error Envelope¶

When a Polymarket CLOB or gasless-relayer rejection coincides with a degraded Polymarket status page, the error envelope may include a polymarket_status object:

{
  "polymarket_status": {
    "page_status": "HASISSUES",
    "status_url": "https://status.polymarket.com",
    "affected_components": [
      {"name": "CLOB API", "status": "PARTIALOUTAGE"}
    ],
    "advisory": "Polymarket is experiencing issues; this rejection is most likely a Polymarket-side outage."
  }
}

The field is omitted on local validation/auth/balance errors and when the status-page fetch times out or reports healthy relevant components.

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.

bullpen polymarket redeem¶