bullpen solana dca list¶
Last updated: May 29, 2026
List Jupiter Recurring DCA schedules
Usage¶
Live Help¶
List Jupiter Recurring DCA schedules
Usage: bullpen solana dca list [OPTIONS]
Options:
--mint <MINT>
Filter displayed DCA schedules by SPL token mint address
--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]
--status <STATUS>
DCA order status to list
[default: active]
[possible values: active, history]
--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.
--page <PAGE>
Jupiter Recurring result page to fetch
[default: 1]
--all
Fetch all pages starting from --page
--include-failed
Ask Jupiter to include failed transaction rows when supported
--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 solana dca list --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen solana dca list [OPTIONS]
bullpen solana dca list --help
bullpen solana dca list --status active --page 1 --output json
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 |
|---|---|---|---|
address |
string | no | Bullpen Solana wallet whose DCA schedules were queried |
status |
string | no | active or history |
mint |
string | yes | Optional mint filter |
page |
integer | yes | First page requested from Jupiter Recurring |
total_pages |
integer | yes | Total pages reported by Jupiter Recurring |
items |
array | no | DCA schedule summaries with derived progress and raw Jupiter row |
Example¶
{
"address": "7qRkWTrM4DLpmeSnB8xT8p8mpqLQ9JdYatYczS4u1G8e",
"status": "active",
"mint": null,
"page": 1,
"total_pages": 1,
"items": [
{
"order_key": "7nE9GJoYHNmtaQvTQpota3KV2oz4pQ2dA6nvYK8EUJHV",
"input_mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"output_mint": "So11111111111111111111111111111111111111112",
"in_amount_per_cycle": "50",
"raw_in_amount_per_cycle": "50000000",
"raw_in_deposited": "200000000",
"cycle_frequency": 86400,
"total_cycles": 4,
"executed_cycles": 1,
"remaining_cycles": 3,
"progress_percent": "25",
"next_execution_time": "2026-05-30T12:00:00+00:00",
"status": "active",
"created_at": "2026-05-29T12:00:00Z",
"updated_at": "2026-05-29T12:00:00Z",
"raw": {}
}
]
}
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.
Solana Recurring Notes¶
dca listis read-only. It uses the cached/read-only Solana signer path and does not call Turnkey, Jupiter/execute,createOrder,cancelOrder, orTxService.SubmitV4.- Jupiter Recurring uses
recurringType=time.--status activeis the default; pass--status historyfor completed or cancelled schedules. --mintis forwarded as Jupiter's Recurring mint filter.- Use
bullpen solana dca create --previeworbullpen solana dca cancel --previewto inspect unsigned Jupiter Recurring transactions without Turnkey signing or/execute.