bullpen polymarket events

Last updated: May 29, 2026

List and filter prediction market events

Usage

bullpen polymarket events [OPTIONS]

Live Help

List and filter prediction market events

Usage: bullpen polymarket events [OPTIONS]

Options:
      --limit <LIMIT>
          Maximum results (default 25)

          [default: 25]

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

      --sort <SORT>
          Sort by: volume (default), liquidity, start_date

          [default: volume]

      --active
          Only active events (default)

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

      --closed
          Only closed events

      --include-closed
          Include closed events alongside active events

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

      --tag <TAG>
          Filter by tag slug (e.g. "politics", "crypto")

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

Example Commands

bullpen polymarket events [OPTIONS]
bullpen polymarket events --help
bullpen polymarket events --output json

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.