bullpen portfolio pnl¶
Last updated: May 29, 2026
Show realized and unrealized profit & loss.
Usage¶
Live Help¶
Show realized and unrealized profit & loss.
Without --granularity shows an aggregate summary. With --granularity shows P&L bucketed by day, week, or month using the getPaginatedPnl endpoint.
Usage: bullpen portfolio pnl [OPTIONS]
Options:
--granularity <GRANULARITY>
Time granularity for bucketed P&L: day, week, month. When omitted, shows the aggregate P&L summary
Possible values:
- day: Group P&L transactions by calendar day
- week: Group P&L transactions by ISO calendar week (Monday-Sunday)
- month: Group P&L transactions by calendar month
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--address <ADDRESS>
Wallet address to query (required when --granularity is set)
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
--chain <CHAIN>
Chain identifier (default: polygon). Options: polygon, solana, hypercore-spot, hypercore-perp
[default: polygon]
--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.
--start <START>
Start date for P&L range (ISO 8601 date or Unix timestamp in seconds, e.g. 2024-01-01 or 1704067200)
--end <END>
End date for P&L range (ISO 8601 date or Unix timestamp in seconds)
--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 portfolio pnl --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
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.