bullpen wallet import

Last updated: May 29, 2026

Import an external wallet private key into Turnkey custody

Usage

bullpen wallet import [OPTIONS] --chain <CHAIN>

Live Help

Import an external wallet private key into Turnkey custody

Usage: bullpen wallet import [OPTIONS] --chain <CHAIN>

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

          [possible values: table, json]

      --private-key <PRIVATE_KEY>
          Private key material. Use hex for EVM, base58 for Solana. Omit this flag to enter the key interactively without echo

      --chain <CHAIN>
          Import target chain/account type

          [possible values: evm, solana]

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

      --nickname <NICKNAME>
          Optional display name for the imported wallet

  -y, --yes
          Skip confirmation prompt

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

Example Commands

bullpen wallet import [OPTIONS] --chain <CHAIN>
bullpen wallet import --help
bullpen wallet import --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.