bullpen hyperliquid funding¶
Last updated: May 29, 2026
Show current funding rates for all markets, or your funding payment history
Usage¶
Live Help¶
Show current funding rates for all markets, or your funding payment history
Usage: bullpen hyperliquid funding [OPTIONS]
Options:
--address <ADDRESS>
Ethereum address to query for funding payments
--no-multi-wallet-warning
Suppress the table-mode warning shown when multiple EVM wallet accounts exist
--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]
--start <START>
Start of the funding history window in Unix milliseconds. Defaults to 30 days ago when querying user funding
--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.
--end <END>
End of the funding history window in Unix milliseconds. Defaults to the current time when querying user funding
--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 hyperliquid funding --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen hyperliquid funding [OPTIONS]
bullpen hyperliquid funding --help
bullpen hyperliquid funding --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.