bullpen polymarket positions¶
Last updated: May 29, 2026
View prediction market positions and P&L
Usage¶
Live Help¶
View prediction market positions and P&L
Usage: bullpen polymarket positions [OPTIONS]
Options:
--address <ADDRESS>
Wallet address (defaults to your own Polymarket address)
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--closed
Show closed positions instead of active
--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.
--redeemable
Show only redeemable positions
--source <SOURCE>
Positions data source: Polymarket is the public Data API wallet snapshot and the default. Bullpen is the experimental authenticated server-aggregated view with realized P&L
Possible values:
- bullpen: Use Bullpen account data
- polymarket: Use Polymarket data
--condition-id <CONDITION_ID>
Filter positions by condition ID
--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 positions --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket positions [OPTIONS]
bullpen polymarket positions --help
bullpen polymarket positions --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.