The Fireblocks Python SDK provides a robust interface to interact with the Fireblocks platform for secure digital asset operations, including managing vault accounts and executing transactions. It is actively maintained with frequent updates and bug fixes, currently at version 2.17.0, and follows a regular release cadence.
pip install fireblocks-sdkVerified import paths — ran on the pinned version, not inferred.
Initializes the Fireblocks SDK using API key and secret, then fetches a list of vault accounts. It demonstrates secure loading of credentials via environment variables and basic error handling.
Review the GitHub release notes and API documentation for `fireblocks-sdk-py` for affected API endpoints and adjust your request/response models accordingly. Pay close attention to schema changes for `CreateVaultAccountRequest`, `AddAssetToExternalWalletRequest`, and TAP-related operations.
Always load the private key securely, preferably from a file specified by an environment variable (e.g., `FIREBLOCKS_SECRET_KEY_PATH`) and ensure proper file permissions. Avoid exposing it directly in source code or insecure environment variables.
Ensure your development and deployment environments are running Python 3.8 or a later supported version. Upgrade Python if necessary.
Install the package correctly using `pip install fireblocks-sdk` and ensure your Python code uses `from fireblocks_sdk import FireblocksSDK`.
Verify that `FIREBLOCKS_API_KEY` and the content of your private key (from `FIREBLOCKS_SECRET_KEY_PATH` or `FIREBLOCKS_SECRET_KEY`) are correct. Check the Fireblocks Console under 'Developer Center > API Users' to ensure the API user has the required workspace roles and permissions.
Confirm network connectivity. Verify that `FIREBLOCKS_BASE_PATH` is set to the correct Fireblocks environment endpoint (e.g., `https://sandbox-api.fireblocks.io/v1` for sandbox, `https://api.fireblocks.io/v1` for production). Review your request payload for correctness. If persistent, check the Fireblocks system status page or contact Fireblocks support with the `x-request-id` from the error response if available.
No dependency data recorded yet.