Skip to main content
The CLI authenticates to the Fireblocks API using the same JWT-signing mechanism as the official SDKs: each request is signed with your RSA private key and identified by your API key.

Prerequisites

You need:
  • A Fireblocks API key — obtained from the Fireblocks Console under Developer Center > API Users
  • An RSA private key — the .key file generated when creating the API user
See Quickstart for instructions on creating an API user and generating a key pair.

Credential Resolution Order

The CLI resolves credentials in priority order:
  1. CLI flags--api-key and --secret-key passed directly on the command line
  2. Environment variablesFIREBLOCKS_API_KEY and FIREBLOCKS_SECRET_KEY (or FIREBLOCKS_SECRET_KEY_PATH)
  3. Config file profile — stored in ~/.config/fireblocks/config.json
If no credentials are found, the CLI exits with an error and instructions for how to configure them.

Interactive Setup

The easiest way to configure credentials is the interactive configure command:
This prompts for your API key, the path to your private key file, and optionally a base URL override. Credentials are written to ~/.config/fireblocks/config.json with file permissions 0600. To configure a named profile:
To switch the default profile:

Config File Format

Environment Variables

For CI/CD pipelines and non-interactive environments, set credentials as environment variables:
You can also pass inline PEM content directly — useful when pulling key material from a secrets manager:

CLI Flags

Pass credentials directly on the command line to override environment variables and the config file:
--secret-key accepts either a file path or an inline PEM string.

Multiple Profiles

Use profiles to manage multiple workspaces or environments:

API Base URL

The default base URL is https://api.fireblocks.io. Override it per command, in a profile, or via FIREBLOCKS_BASE_URL.

Verify Your Setup

Run whoami to confirm credentials are configured correctly and that the API key can authenticate:
This calls GET /v1/users/me and returns the masked API key, base URL, and user details on success. To preview the resolved auth context without making a network call: