bullpen solana cancel-order

Last updated: May 29, 2026

Cancel a single Jupiter Trigger limit order

Usage

bullpen solana cancel-order [OPTIONS] <ORDER_KEY>

Live Help

Cancel a single Jupiter Trigger limit order

Usage: bullpen solana cancel-order [OPTIONS] <ORDER_KEY>

Arguments:
  <ORDER_KEY>
          Jupiter Trigger order account/key to cancel

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --yes
          Skip confirmation prompt

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --preview
          Show the cancel request without signing or submitting

      --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:
  bullpen solana cancel-order --help
      Show options for this command without signing, submitting, or changing state.

Example Commands

bullpen solana cancel-order [OPTIONS] <ORDER_KEY>
bullpen solana cancel-order --help
bullpen solana cancel-order 7nE9GJoYHNmtaQvTQpota3KV2oz4pQ2dA6nvYK8EUJHV --preview --output json

JSON Output

Contract: JSON Output Contract.

Preview (--preview --output json)

Preview output is a single JSON document emitted only when --preview --output json is passed. Live submit output uses the corresponding Solana Trigger mutation-report schema instead.

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
action	string	no	cancel_limit_order for previews
order	string	no	Jupiter Trigger order key to cancel
maker	string	no	Bullpen Solana wallet used as maker
request	object	no	Jupiter Trigger cancelOrder request preview; live success adds signature and receipt fields

Example

bullpen solana cancel-order 7nE9GJoYHNmtaQvTQpota3KV2oz4pQ2dA6nvYK8EUJHV --preview --output json

{
  "action": "cancel_limit_order",
  "order": "7nE9GJoYHNmtaQvTQpota3KV2oz4pQ2dA6nvYK8EUJHV",
  "maker": "7qRkWTrM4DLpmeSnB8xT8p8mpqLQ9JdYatYczS4u1G8e",
  "request": {
    "order": "7nE9GJoYHNmtaQvTQpota3KV2oz4pQ2dA6nvYK8EUJHV",
    "maker": "7qRkWTrM4DLpmeSnB8xT8p8mpqLQ9JdYatYczS4u1G8e"
  }
}

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

• --preview builds the cancel request without Turnkey signing, Jupiter cancel mutation endpoints, or TxService.SubmitV4 submission.
• Live cancel builds unsigned cancel transactions with Jupiter Trigger, signs with the Bullpen Solana wallet, and submits through Bullpen TxService.SubmitV4 after confirmation.
• Cancel commands do not run JupiterShield and do not expose --skip-shield-check or --slippage-bps.