bullpen polymarket bracket fill¶
Last updated: July 13, 2026
Fill all picks from a JSON file
Usage¶
Live Help¶
Fill all picks from a JSON file
Usage: bullpen polymarket bracket fill [OPTIONS] --file <FILE> <CONTEST_ID>
Arguments:
<CONTEST_ID>
Contest ID
Options:
--file <FILE>
Path to JSON picks file
--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]
--tiebreaker <TIEBREAKER>
Tiebreaker: predicted combined championship game score
[default: 0]
--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.
--dry-run
Show picks without submitting
--yes
Confirm submission without prompting
--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:
# Review existing picks before importing a file
bullpen polymarket bracket picks march-madness-2026
# Preview imported picks without submitting
bullpen polymarket bracket fill march-madness-2026 --file picks.json --dry-run
# Preview imported picks as JSON
bullpen polymarket bracket fill march-madness-2026 --file picks.json --dry-run --output json
# Submit imported picks after review
bullpen polymarket bracket fill march-madness-2026 --file picks.json --yes
Example Commands¶
bullpen polymarket bracket picks march-madness-2026
bullpen polymarket bracket fill march-madness-2026 --file picks.json --dry-run
bullpen polymarket bracket fill march-madness-2026 --file picks.json --dry-run --output json
bullpen polymarket bracket fill march-madness-2026 --file picks.json --yes
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.