bullpen polymarket activity¶
Last updated: May 29, 2026
View activity history (trades, redemptions, rewards, etc.)
Usage¶
Live Help¶
View activity history (trades, redemptions, rewards, etc.)
Usage: bullpen polymarket activity [OPTIONS]
Options:
--address <ADDRESS>
Polymarket address (defaults to your own)
--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]
--limit <LIMIT>
Maximum number of results (default 25)
[default: 25]
--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.
--type <TYPE>
Filter by type. Omit for all activity, or pass all by itself
Possible values:
- all: Do not send an activity-type filter
- trade: Trades
- split: CTF split operations
- merge: CTF merge operations
- redeem: Redemptions
- reward: Rewards
- conversion: Conversions
- yield: Yield activity
- maker_rebate: Maker rebates
--market <MARKET>
Filter by market condition ID (repeatable)
--side <SIDE>
Filter by side: buy, sell
--read-only
Enable read-only mode: blocks all mutating commands
--start <START>
Start date (ISO 8601 or unix timestamp)
--end <END>
End date (ISO 8601 or unix timestamp)
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
--sort <SORT>
Sort by: timestamp, tokens, cash
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
bullpen polymarket activity --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket activity [OPTIONS]
bullpen polymarket activity --help
bullpen polymarket activity --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.