Skip to main content
Postman is an application designed to help with API integration and exploration. Intuitive for different tech skill levels, this is the tool of choice both for experienced developers and no-code enthusiasts to get familiar with our available endpoints, requests, and responses. Using our Postman Collection, you can start testing our API before you write a single line of code.

Install Postman and Fireblocks Collection

  1. Download and install the Postman app or use Postman online.
  2. Import the Fireblocks collection: Run in Postman
After following the steps above and opening Postman, you’ll see the Fireblocks API collection.

Set up authentication

The Fireblocks Postman collection signs each request with a JSON Web Token (JWT) using your API credentials. The collection includes a pre-request script that reads your API key and secret key from a Postman environment you create. The collection does not include credentials or an environment file.
New to API authentication? Follow Step 1 in the Quickstart to generate a CSR, create an API user, and obtain your credentials. For ongoing key management, see Manage API Access.

Create a Postman environment

Mind your environment’s scope. Postman environments can live in a personal workspace (private to you) or a shared/team workspace, where they sync to every member with access. Create your Fireblocks environment in your personal workspace, not a shared or team workspace, and keep fireblocksSecretKey there only. Treat it with the same care as your private key file — anyone who can access the environment can read it.
  1. In Postman, select Environments in the left sidebar.
  2. Select + to create a new environment.
  3. Name it (for example, Fireblocks API).
  4. Add the following variables and set their Current value:
  1. Select Save.

Select the environment

  1. In the top-right corner of Postman, open the environment dropdown.
  2. Select the environment you created.
The collection pre-request script requires an active environment. If none is selected, requests fail with an error like No environment containing a fireblocksApiKey variable has been selected.

Set the base URL

The collection includes a baseUrl collection variable, defaulting to https://api.fireblocks.io/v1. Update it to match your workspace:
  1. Select the Fireblocks API collection in the left sidebar.
  2. Open the Variables tab.
  3. Set baseUrl to the value for your workspace:
  1. Select Save.
Sandbox users: Developer Sandboxes include a pre-created API user. You can download the API key and secret key from the Sandbox Console instead of generating your own CSR. See the Quickstart for details.

Verify your setup

  1. Confirm your Fireblocks environment is selected in the top-right environment dropdown.
  2. Open any GET request in the Fireblocks API collection (for example, a vault accounts endpoint).
  3. Select Send.
A 200 response confirms authentication is working. If you receive an authentication error, check the troubleshooting tips below.

Troubleshooting

Store your API key and secret key only in your Postman environment. Do not share screenshots that include these values.
  • No environment selected — Select the environment you created before sending requests. The pre-request script reads fireblocksApiKey and fireblocksSecretKey from the active environment only.
  • Empty fireblocksSecretKey — Paste the full PEM contents of your private key file, including the header and footer lines. The pre-request script rejects values that do not start with -----BEGIN PRIVATE KEY-----.
  • Duplicate variables — Keep fireblocksApiKey and fireblocksSecretKey in your environment only. If the same variables also exist as collection variables, remove or clear the collection-level copies.
  • Wrong baseUrl — Include the /v1 suffix (for example, https://sandbox-api.fireblocks.io/v1, not https://sandbox-api.fireblocks.io). Set baseUrl on the collection Variables tab.
  • 404 errors — A missing or incorrect baseUrl often causes 404 responses. Double-check the value against your workspace type in Workspace Comparison.
For details on how request signing works, see Authenticate.