The Official Python SDK for Fireblocks API
⚠️ This package is deprecated.
fireblocks-sdkis deprecated and reaches end-of-life on November 1, 2026 — no further updates or fixes will be released after that date.Existing installs continue to work, and this package will never be unpublished or yanked.
Migrate to the
fireblockspackage — see the SDK Migration Guide.To silence the startup warning, set
FIREBLOCKS_SDK_SUPPRESS_DEPRECATION_WARNING=1.
About
This repository contains the official Python SDK for Fireblocks API. For the complete API reference, go to the API reference.
Usage
Before You Begin
Make sure you have the credentials for Fireblocks API Services. Otherwise, please contact Fireblocks support for further instructions on how to obtain your API credentials.
Requirements
An officially supported version of Python, as per the official lifecycle: https://devguide.python.org/versions
Installation
pip3 install fireblocks-sdk
Importing Fireblocks SDK
from fireblocks_sdk import FireblocksSDK
fireblocks = FireblocksSDK(private_key, api_key)
You can also pass additional arguments:
fireblocks = FireblocksSDK(private_key, api_key, api_base_url="https://api.fireblocks.io", timeout=2.0, anonymous_platform=True)
Using Fireblocks Tokenization endpoints
from fireblocks_sdk import FireblocksSDK, FireblocksTokenization, \
ContractUploadRequest
fireblocks = FireblocksSDK(private_key, api_key)
# Get linked tokens
tokens=fireblocks.get_linked_tokens()
# Upload a private contract
contractTemplateRequest=ContractUploadRequest(
name='New Contract Template',
description='description',
longDescription='long description',
bytecode='0x12345',
sourcecode= 'sourcecode',
initializationPhase='ON_DEPLOYMENT',
abi=[]
)
template=fireblocks.upload_contract_template(contractTemplateRequest)
print(template['id'])
Metadata
Release files for fireblocks-sdk 2.19.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fireblocks_sdk-2.19.1.tar.gz | 38.3 kB | Without provenance | Details for fireblocks_sdk-2.19.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fireblocks_sdk-2.19.1-py3-none-any.whl | Python 3 | none | any | Details for fireblocks_sdk-2.19.1-py3-none-any.whl |
Total release size: 74.2 kB
Release files / fireblocks_sdk-2.19.1.tar.gz
| Download URL | fireblocks_sdk-2.19.1.tar.gz |
|---|---|
| Size | 38.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d977155bdd2032c7d99a85046745fcdc78a1d006009159d263fd6f2c853c97ab
|
|
BLAKE2b-256 checksum How to use checksums |
ae7660226e749a089d2b6807a3a2b9f747aa36a3b43e290e6f1b2b7a6261b5cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / fireblocks_sdk-2.19.1-py3-none-any.whl
| Download URL | fireblocks_sdk-2.19.1-py3-none-any.whl |
|---|---|
| Size | 35.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6d8df00cd89073ffb53d53c477cadfec580c17fe0e94489a620f5479bc29aea
|
|
BLAKE2b-256 checksum How to use checksums |
d63a043f810138352b4672318782c993683151f8757d73caf8ee3d9c9bc23278
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for fireblocks-sdk 2.19.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.