Releases: fireblocks/fireblocks-cli
Release list
v3.0.0
Changelog
2026-07-01
Breaking Change
Connected account creation renamed to 'add'
Products: Connected Accounts (Beta)
Scope: API + SDKs
-
What's new
The endpoint for creating a connected account has been updated to use 'add' terminology, replacing the previous 'create' naming throughout. -
Impact
Existing integrations that call the connected account creation endpoint will need to be updated to use the new 'add' naming.
Affected endpoints:
v2.0.0
Changelog
2026-06-28
Breaking Change
Restructure Reports API response schemas (beta)
Products: Reports (Beta)
Scope: API + SDKs
-
What's new
Introduces a base report job schema and separates list responses from detail responses, removing short-lived download links from list items. -
Impact
Customers must call the individual report endpoint to obtain download URLs instead of getting them from list responses.
Affected endpoints:
Update ConnectedAccountErrorResponse required fields
Products: Connected Accounts (Beta)
Scope: API + SDKs
-
What's new
Changes required fields fromerrorMessage/errorCodetomessage/codewhile keeping legacy fields as optional. -
Impact
Customers must update error handling to use the newmessageandcodefields.
Affected endpoints:
- Get allowlist for connected account
- Get a single allowlist entry for a connected account
- Rename Connected Account
- Get connected accounts
- Create a connected account
Relocate participantsIdentificationPolicy to endpoint level
Products: Trading (Beta)
Scope: API + SDKs
-
What's new
Moves theparticipantsIdentificationPolicyproperty from the manifest root to individual endpoint configurations (order, quote, rate), enabling per-endpoint KYC/AML policy definitions. -
Impact
Customers must now read identification policies from endpoint-specific locations instead of the manifest root.
Affected endpoints:
Restructure Reports API response schemas (beta)
Products: Reports (Beta)
Scope: API + SDKs
-
What's new
Introduces a base report job schema and separates list responses from detail responses, removing short-lived download links from list items. -
Impact
Customers must call the individual report endpoint to obtain download URLs instead of getting them from list responses.
Affected endpoints:
Update PayID schema field requirements
Products: External wallets
Scope: API + SDKs
-
What's new
Makes thebsbfield required in PayID payment info and makesaccountNumberoptional in PayID address to align with current payment processing requirements. -
Impact
Customers must now provide thebsbfield when creating PayID whitelist addresses.
Affected endpoints:
Rename verified field to leiData in Address Registry
Products: Compliance
Scope: API + SDKs
-
What's new
Renames theverifiedfield toleiDatain the Address Registry legal entity schema to better indicate LEI data availability. -
Impact
Existing integrations must update fromverifiedtoleiDatawhen parsing legal entity responses.
Affected endpoints:
Add vaultAccountId and userId to Earn action response
Products: Earn (Beta)
Scope: API + SDKs
-
What's new
Adds requiredvaultAccountIdanduserIdfields to the Earn GetActionResponse schema, identifying which vault account and user executed each action. -
Impact
Customers can now see which vault account and user initiated each Earn action.
Affected endpoints:
Add Binance support to connected accounts allowlist | Add metadata envelope to allowlist entry response
Products: Connected Accounts (Beta)
Scope: API + SDKs
-
What's new
Connected accounts allowlist endpoints now support Binance accounts in addition to CoinbaseExchange. The allowlist entry endpoint now returns a response envelope containing both the entry data and account-level allowlist sync metadata. -
Impact
Customers can use allowlist endpoints with Binance connected accounts. Customers receive additional sync metadata when retrieving individual allowlist entries.
Affected endpoints:
- Get allowlist for connected account
- Sync allowlist for connected account
- Get a single allowlist entry for a connected account
Restructure PolicyMetadata as map keyed by policy type
Products: Policy Editor V2 (Beta)
Scope: API + SDKs
-
What's new
Restructures thePolicyMetadataschema from a flat object to a dictionary keyed by policy type, allowing metadata for multiple policies in a single response. -
Impact
Existing integrations parsingPolicyMetadatamust update to handle the new map structure instead of direct properties.
Affected endpoints:
- Get the active draft by policy type
- Update the draft with a new set of rules by policy types
- Send publish request for a certain draft id
- Get the active policy and its validation by policy type
Rename vout to index in UTXO schemas
Products: Off exchanges, Transactions
Scope: API + SDKs
-
What's new
Renames thevoutfield toindexacross UTXO API schemas to align withlistUnspentand legacy input selection naming conventions. -
Impact
Beta customers using UTXO selection or identifier APIs must update requests to useindexinstead ofvout.
Affected endpoints:
Rename vout to index in UTXO schemas
Products: UTXO Management (Beta)
Scope: API + SDKs
-
What's new
Renames thevoutfield toindexacross UTXO API schemas to align withlistUnspentand legacy input selection naming conventions. -
Impact
Beta customers using UTXO selection or identifier APIs must update requests to useindexinstead ofvout.
Affected endpoints:
Align Exposure schema with vault allocation slice
Products: Earn (Beta)
Scope: API + SDKs
-
What's new
Renames theassetAddressfield toaddressand addsdecimals,assetId, andamountUsdfields to provide richer exposure data. AddsexposureTypeenum to describe what exposure rows represent and increases the exposure array limit from 10 to 20 items. -
Impact
Customers reading exposure data must update to useaddressinstead ofassetAddress.
Affected endpoints:
...v1.0.10
dump new version 1.0.10
v1.0.9
v1.0.8
v1.0.7
v1.0.6
What's new
Profile management
fireblocks configure --set-default=<profile>— switch the
default profile without
re-entering credentials- When configuring a second profile, you are now prompted whether to
make it the default baseUrlis always saved in every profile (including the default
https://api.fireblocks.io),
making the config file fully self-describing
fireblocks whoami
- Now reads directly from the config file — no API call is made
- Shows
defaultProfile, maskedapiKey, andbaseUrlfor the
current default profile
Bug fix
- Configuring a second or third profile no longer silently leaves the
default unchanged —
the CLI now asks if the new profile should become the default