bullpen polymarket orders¶
Last updated: May 29, 2026
View open orders, trade history, or cancel orders
Usage¶
Live Help¶
View open orders, trade history, or cancel orders
Usage: bullpen polymarket orders [OPTIONS]
Options:
--address <ADDRESS>
Wallet address (used with --history)
--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]
--history
Show past trade history
--cancel <CANCEL>
Cancel order(s) by ID; comma-separate multiple IDs for bulk cancel
--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>
Maximum history rows to fetch
--offset <OFFSET>
Number of history rows to skip
--read-only
Enable read-only mode: blocks all mutating commands
--side <SIDE>
Filter self history by trade side
[possible values: buy, sell]
--category <CATEGORY>
Filter self history by Bullpen category
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
--market-slug <MARKET_SLUG>
Filter self history by market slug
--cancel-all
Cancel ALL open orders
--cancel-market <CANCEL_MARKET>
Cancel all orders on a specific market (by condition ID)
--yes
Skip confirmation prompt
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
bullpen polymarket orders --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket orders [OPTIONS]
bullpen polymarket orders --help
bullpen polymarket orders --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.