Skip to main content
Deprecation noticeThe legacy Python SDK (fireblocks-sdk) will reach end of life on November 1, 2026, after which it will no longer receive updates, bug fixes or support. Existing installations will continue to work and the package will not be unpublished or yanked, but we cannot guarantee compatibility with future Fireblocks API changes. Fireblocks is not responsible for any disruption resulting from continued use of the legacy SDK after this date. Migrate to the fireblocks package now. For upgrade steps, see the SDK Migration Guide.
A Python developer can use the Fireblocks API in 2 different ways:
  1. The Fireblocks Python SDK.
  2. A standard HTTP library such as http.client or Requests.
In this guide, you’ll set up the Fireblocks SDK and see an example of non-SDK usage (including signing the JWT token).

Using the Fireblocks SDK

Install Python 3.6 or newer

The Fireblocks Python SDK requires Python 3.6 or newer. You can check which version of Python you already have installed with the following command. python --version or python3 --version Learn how to install or update Python to a newer version.

Install fireblocks-sdk

The Fireblocks Python SDK is open-source and hosted on both GitHub and PIP, the official package repository. Installing the latest SDK is easy with pip: pip install fireblocks-sdk

Your First Fireblocks Python script!

Now that you’re set up, run a quick check for the API. The script will query existing vaults, create a new vault and then query again to see that the vaults were created. The requests-based implementation will require some library dependencies:
Use the correct API Base URLDepending on the script, make sure you’re using the correct value for base_url for your environment:
  • For Sandbox workspaces: https://sandbox-api.fireblocks.io
  • For Mainnet or Testnet workspaces: https://api.fireblocks.io