• ExchangeType data object
  • Added the KRAKENINTL value
  • Removed the FTX value due to the FTX integration being deprecated
  • Added a note to the object clarifying that the BINANCEUS and KRAKENINTL values should be used only by their respective customers

• API Reference > Resources > API Co-Signer
  • Moved the Automated Callback Signer content to API Reference > Webhooks & Notifications > API Co-Signer Callback to align the callback with similar content
    • Also changed the page's name from Automated Callback Signer to API Co-Signer Callback to help clarify its relationship to the API Co-Signer
  • Updated the API Co-Signer page with links to the Help Center's API Co-Signer section and to the Callback Handler structure

• Exchange Account Objects
  • Updated the Exchange Objects page title to Exchange Account Objects for consistency
• Network Connection Objects
  • Updated the Network Objects page title to Network Connection Objects to help clarify that these objects refer to the Fireblocks Network
  • Updated the NetworkConnectionRoutingPolicy object
    • Removed the following parameters due to the Signet and Silvergate integrations being deprecated:
      • sen
      • signet
      • sen_test
      • signet_test
• Transaction Objects
  • Removed the FeePayerInfo object
  • Moved the UnspentInputsData object to the Vault Objects page
  • Further separated the page's contents into the following pages:
    • Transaction Authorization Objects
    • Fee Estimation Objects
    • Transaction Screening Objects
    • Raw Signing Objects
  • Adjusted order of objects based on their perceived importance

We updated the following API Reference pages:

• Data Objects
  • Separated the data object sets into discrete articles and reformatted them for easier reading
  • Corrected a variety of errors in parameter descriptions
• Transaction Statuses
  • Separated viewing transaction statuses, primary statuses, and substatuses into discrete articles and reformatted them for easier reading
  • Updated all statuses to reflect current functionality in the UI and the API
  • Added troubleshooting information to primary status and substatus descriptions where applicable

On May 9th, 2023 , the new API GET /v1/vault/asset_wallets provides a fast traversal of all of your account balances.

It is considered faster than using GET /v1/vault/accounts_paged. This API endpoint is in limited availability and available for selected customers.

If you would like to get early access to this endpoint, please reach out to Fireblocks Support

On April 10, 2023 , API calls made to the GET v1/vault/accounts endpoint will be rate limited to a maximum of 400,000 vault accounts in a minute, per workspace.

Please note that if you attempt to retrieve more than 400,000 vault accounts in a single request, the API response will return an HTTP status code 429.

Additionally, if two requests are made in a minute to retrieve 200,000 vault accounts each, the second request will also fail with status 429.

To minimize the impact on your workspaces, we recommend that you migrate to the GET /v1/vault/accounts_paginated endpoint.

For any questions, please contact Fireblocks Support by submitting a request.

As per the previous notices, the error codes for API calls that use the Idempotency-Key header have now been changed from Error 500 to Error 400.

With this change, Fireblocks API will return the following error after the first failed API call:

Error 400 - “This operation doesn't support the usage of the same idempotency key after an internal error”

For any questions, please contact Fireblocks Support by submitting a request.

On January 30, 2023 Fireblocks is changing error codes for API calls that use the Idempotency-Key header from Error 500 to Error 400. If your application logic does not depend on Error 500, no action is required.

All other customers must update their application logic by January 30, 2022 to account for the new Error 400 API response.

With this change, Fireblocks API will return the following error after the first failed API call:

Error 400 - “This operation doesn't support the usage of the same idempotency key after an internal error”

For any questions, please contact Fireblocks Support by submitting a request.

A new introductory article about Fireblocks Network Link for Exchanges has been added to the "OpenAPI and SDK" section. This article also links to the OpenAPI/Swagger specification, as well as the Github Official Documentation.

Updated documentation to take out Transfer Tickets, which was an unused endpoint.