`bullpen solana orders`¶

Last updated: May 29, 2026

List Jupiter Trigger limit orders

Usage¶

bullpen solana orders [OPTIONS]

Live Help¶

List Jupiter Trigger limit orders

Usage: bullpen solana orders [OPTIONS]

Options:
      --mint <MINT>
          Filter displayed orders 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>
          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 Trigger result page to fetch

          [default: 1]

      --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 orders --help
      Show options for this command without signing, submitting, or changing state.

Example Commands¶

bullpen solana orders [OPTIONS]
bullpen solana orders --help
bullpen solana orders --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 orders were queried
`status`	string	no	`active` or `history`
`mint`	string	yes	Optional mint filter
`page`	integer	yes	Page requested from Jupiter Trigger
`total_pages`	integer	yes	Total pages reported by Jupiter Trigger
`orders`	array	no	Raw Jupiter Trigger order rows with stable known fields preserved

Example¶

bullpen solana orders --status active --page 1 --output json

{
  "address": "7qRkWTrM4DLpmeSnB8xT8p8mpqLQ9JdYatYczS4u1G8e",
  "status": "active",
  "mint": null,
  "page": 1,
  "total_pages": 1,
  "orders": [
    {
      "orderKey": "7nE9GJoYHNmtaQvTQpota3KV2oz4pQ2dA6nvYK8EUJHV",
      "inputMint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
      "outputMint": "So11111111111111111111111111111111111111112",
      "makingAmount": "500000000",
      "takingAmount": "2500000000",
      "status": "active"
    }
  ]
}

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 Trigger Notes¶

orders is read-only and queries Jupiter Trigger active or history orders.
--mint queries both inputMint and outputMint filters, then de-duplicates matching order keys.

bullpen solana orders¶