`bullpen polymarket watch`¶

Last updated: May 29, 2026

Subscribe to real-time market data via WebSocket

Usage¶

bullpen polymarket watch [OPTIONS] <MARKET>

Live Help¶

Subscribe to real-time market data via WebSocket

Usage: bullpen polymarket watch [OPTIONS] <MARKET>

Arguments:
  <MARKET>
          Market slug or URL

Options:
      --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]

      --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:
  bullpen polymarket watch --help
      Show options for this command without signing, submitting, or changing state.

Example Commands¶

bullpen polymarket watch [OPTIONS] <MARKET>
bullpen polymarket watch --help
bullpen polymarket watch --output json

JSON Output¶

Contract: JSON Output Contract.

Streaming output emits one JSON document per event line. Each event follows the shared contract, including SIGPIPE-safe pipe behavior.

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

Top-level Keys¶

key	type	nullable	notes
`event`	string	no	Event type, such as `book`, `price_change`, `trade`, or `last_trade_price`
`market`	string	yes	Condition id for market-channel events when present
`asset_id`	string	yes	CLOB token id for token-specific updates
`outcome`	string	yes	Outcome label resolved from the token id when known
`timestamp`	string	yes	Upstream event timestamp when present

Example¶

bullpen polymarket watch --output json

{
  "event": "price_change",
  "market": "0xsamplecondition",
  "asset_id": "1234567890",
  "outcome": "Yes",
  "side": "BUY",
  "price": "0.52",
  "size": "250",
  "best_bid": "0.51",
  "best_ask": "0.53",
  "timestamp": "1779920575394"
}

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 watch¶