bullpen solana token hidden¶
Last updated: July 13, 2026
List Solana token rows hidden for this Bullpen account
Usage¶
Live Help¶
List Solana token rows hidden for this Bullpen account
Usage: bullpen solana token hidden [OPTIONS]
Options:
--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]
--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.
--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:
# Show hidden Solana token mints
bullpen solana token hidden
# Export hidden token mints as JSON
bullpen solana token hidden --output json
Example Commands¶
JSON Output¶
Contract: JSON Output Contract.
Successful output is a single JSON document. The shape below is representative for this command family; commands may add fields without breaking the shared contract.
Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.
Top-level Keys¶
| key | type | nullable | notes |
|---|---|---|---|
schema_version |
integer | no | Output schema version, currently 1 |
chain |
string | no | Always solana |
list_name |
string | no | User-list name, currently hidden |
user_id |
string | yes | Bullpen user id when returned by Bullpen account services |
mints |
array |
no | Hidden SPL token mint addresses for this Bullpen account |
Example¶
{
"schema_version": 1,
"chain": "solana",
"list_name": "hidden",
"user_id": "user_123",
"mints": [
"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
]
}
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.