Skip to content

bullpen polymarket sell

Last updated: July 13, 2026

Sell shares on a prediction market outcome

Usage

bullpen polymarket sell [OPTIONS] <MARKET_SLUG> <OUTCOME> [SHARES]

Live Help

Sell shares on a prediction market outcome

Usage: bullpen polymarket sell [OPTIONS] <MARKET_SLUG> <OUTCOME> [SHARES]

Arguments:
  <MARKET_SLUG>
          Market slug

  <OUTCOME>
          Outcome name

  [SHARES]
          Number of shares to sell (e.g., "50" or "12.5"; NOT USD)

Options:
      --max
          Sell the maximum CLOB-accepted two-decimal share amount for this outcome. Sub-0.01 residual shares may remain as unsellable dust

      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

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

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

      --yes
          Skip confirmation

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

      --preview
          Show order preview without executing

      --min-price <MIN_PRICE>
          Minimum acceptable fill price — reject if fill would be below this price

      --auto-wrap
          Accepted for compatibility; no-op on sells (no collateral consumed)

      --wallet <WALLET>
          Pin the signer to a specific owner EOA (0x…). Does not override the server-selected Safe/Proxy/Deposit Wallet or bypass 1151 safety checks. Use in bot automation to avoid wallet-select races

      --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:
  # Preview selling 10 No shares without signing or submitting
  bullpen polymarket sell will-ronaldo-cry-at-the-world-cup-20260604013616610 No 10 --preview --output json

  # Sell 10 No shares with a minimum fill price
  bullpen polymarket sell will-ronaldo-cry-at-the-world-cup-20260604013616610 No 10 --min-price 0.001 --yes

  # Preview selling the maximum CLOB-accepted No shares from a pinned owner EOA
  bullpen polymarket sell will-ronaldo-cry-at-the-world-cup-20260604013616610 No --max --wallet 0xYourOwnerEOA --preview

Example Commands

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