Skip to content

Releases: fireblocks/fireblocks-cli

v3.0.0

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 01 Jul 11:26

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:

  1. Add a connected account

v2.0.0

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 28 Jun 13:50

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:

  1. List reports

Update ConnectedAccountErrorResponse required fields

Products: Connected Accounts (Beta)

Scope: API + SDKs

  • What's new
    Changes required fields from errorMessage/errorCode to message/code while keeping legacy fields as optional.

  • Impact
    Customers must update error handling to use the new message and code fields.

Affected endpoints:

  1. Get allowlist for connected account
  2. Get a single allowlist entry for a connected account
  3. Rename Connected Account
  4. Get connected accounts
  5. Create a connected account

Relocate participantsIdentificationPolicy to endpoint level

Products: Trading (Beta)

Scope: API + SDKs

  • What's new
    Moves the participantsIdentificationPolicy property 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:

  1. Get trading provider by ID
  2. Get providers

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:

  1. List reports

Update PayID schema field requirements

Products: External wallets

Scope: API + SDKs

  • What's new
    Makes the bsb field required in PayID payment info and makes accountNumber optional in PayID address to align with current payment processing requirements.

  • Impact
    Customers must now provide the bsb field when creating PayID whitelist addresses.

Affected endpoints:

  1. Add an asset to an external wallet.

Rename verified field to leiData in Address Registry

Products: Compliance

Scope: API + SDKs

  • What's new
    Renames the verified field to leiData in the Address Registry legal entity schema to better indicate LEI data availability.

  • Impact
    Existing integrations must update from verified to leiData when parsing legal entity responses.

Affected endpoints:

  1. Look up legal entity by blockchain address

Add vaultAccountId and userId to Earn action response

Products: Earn (Beta)

Scope: API + SDKs

  • What's new
    Adds required vaultAccountId and userId fields 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:

  1. Get a single earn lending action
  2. List earn lending actions

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:

  1. Get allowlist for connected account
  2. Sync allowlist for connected account
  3. 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 the PolicyMetadata schema from a flat object to a dictionary keyed by policy type, allowing metadata for multiple policies in a single response.

  • Impact
    Existing integrations parsing PolicyMetadata must update to handle the new map structure instead of direct properties.

Affected endpoints:

  1. Get the active draft by policy type
  2. Update the draft with a new set of rules by policy types
  3. Send publish request for a certain draft id
  4. 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 the vout field to index across UTXO API schemas to align with listUnspent and legacy input selection naming conventions.

  • Impact
    Beta customers using UTXO selection or identifier APIs must update requests to use index instead of vout.

Affected endpoints:

  1. Create a new transaction
  2. Estimate transaction fee
  3. Add Collateral
  4. Remove Collateral

Rename vout to index in UTXO schemas

Products: UTXO Management (Beta)

Scope: API + SDKs

  • What's new
    Renames the vout field to index across UTXO API schemas to align with listUnspent and legacy input selection naming conventions.

  • Impact
    Beta customers using UTXO selection or identifier APIs must update requests to use index instead of vout.

Affected endpoints:

  1. Attach or detach labels to/from UTXOs

Align Exposure schema with vault allocation slice

Products: Earn (Beta)

Scope: API + SDKs

  • What's new
    Renames the assetAddress field to address and adds decimals, assetId, and amountUsd fields to provide richer exposure data. Adds exposureType enum 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 use address instead of assetAddress.

Affected endpoints:

  1. Get list of earn opportunities
...
Read more

v1.0.10

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 11 Jun 14:23
dump new version 1.0.10

v1.0.9

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 02 Jun 12:52
dump new version 1.0.9

v1.0.8

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 07 May 12:20
dump new version 1.0.8

v1.0.7

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 28 Apr 08:09
dump new version 1.0.7

v1.0.6

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 27 Apr 09:28

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
  • baseUrl is 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, masked apiKey, and baseUrl for 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

v1.0.5

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 21 Apr 10:50
dump new version 1.0.5

v1.0.3

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 21 Apr 10:09
dump new version 1.0.3

v1.0.2

Choose a tag to compare

@cli-generation-automation cli-generation-automation released this 20 Apr 11:35
release 1.0.2