bullpen wallet approvals approve

Last updated: October 7, 2026

Sign and submit pending EVM transfer approval requests

Usage

bullpen wallet approvals approve [OPTIONS] [ID]

Live Help

Sign and submit pending EVM transfer approval requests

Usage: bullpen wallet approvals approve [OPTIONS] [ID]

Arguments:
  [ID]
          Pending transfer approval request UUID

Options:
      --all
          Approve every pending request after validation

      --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]

  -y, --yes
          Submit approval(s) without an interactive confirmation prompt

      --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:
  # Approve one pending transfer approval request
  bullpen wallet approvals approve 00000000-0000-4000-8000-000000000001 --yes

  # Approve all pending EVM transfer approval requests
  bullpen wallet approvals approve --all --yes --output json

Example Commands

State change: One or more examples below change account or trading state. Run only the command that matches your intended action.

bullpen wallet approvals approve 00000000-0000-4000-8000-000000000001 --yes
bullpen wallet approvals approve --all --yes --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.