Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt

Use this file to discover all available pages before exploring further.

Learn how to migrate to the latest version of the Fireblocks SDK. We’ve upgraded the Fireblocks SDKs to enhance performance and streamline integration. To ensure uninterrupted functionality, we strongly recommend migrating to the new SDK as soon as possible. Migrating will give you access to the latest features, optimized performance, and ongoing support. This document will help you to:
  • Understand the latest features and improvements
  • Map changes between the legacy and new SDKs
  • Complete the migration to the new SDKs with actionable steps

​
Migrate now to avoid disruptions and keep access to features and updates

The legacy SDKs are being deprecated in phases, reducing its functionality and support over time. Here are important dates to remember:
  • February 15, 2025: Legacy SDKs enter maintenance mode. No new API endpoints will be added, and only critical bug fixes will be provided.
  • August 1, 2026: Legacy SDKs reach end-of-life (EOL). No further updates, bug fixes, or support will be provided, and the SDK will no longer be actively maintained.

​
Key improvements

  • Fully Typed: Reduces runtime errors and improves code reliability.
  • Complete API Alignment: Fully consistent with the API specification.
  • Inline Guidance: Provides detailed descriptions for function arguments.
  • Code Samples: Includes practical examples for every function.
  • Comprehensive Documentation: Clear and detailed resources, including method explanations and HTTP request structures.

​
Key actions for migration

  1. Upgrade your environment:
    1. Update your Python to 3.8 or newer for the latest Python SDK
    2. Upgrade to Node.js v16 or newer for the latest TypeScript SDK.
  2. Install the latest SDK versions: Ensure you have the latest SDK packages by checking all the relevant links for each SDK.
    1. TypeScript SDK
      1. Please note that the new TS SDK does NOT include PII encryption.
    2. Java SDK
    3. Python SDK
  3. Update your codebase: Replace the outdated methods with the new ones here.
  4. Get support if needed: Reach out to your Customer Success Manager (CSM) or Fireblocks Support if you experience any migration issues.

​
GitHub repository mapping: Legacy to New

Legacy SDKNew SDK
Fireblocks JS SDK (Legacy)Fireblocks TypeScript SDK
Fireblocks Python SDK (Legacy)Fireblocks Python SDK

​
SDK mapping: JS SDK (Legacy) to New TypeScript SDK

​
SDK Mapping: Python (Legacy) to New Python SDK

​
FAQs

​
Why are the current SDKs being deprecated?

The legacy SDKs are being phased out to provide a more reliable, efficient, and developer-friendly experience through our new SDKs. The new versions are fully typed, better aligned with our API, and include improved documentation and inline guidance.

​
Can I continue using the legacy SDKs after August 1, 2026?

Yes, but we strongly advise against it. The SDKs will no longer be maintained, which may result in security risks, compatibility issues, and a lack of support, potentially impacting your application.

​
Which programming languages are supported in the new SDKs?

We offer SDKs for TypeScript, Python, and Java. Developers using other languages should integrate directly with our API.

​
What happens if I don’t migrate before August 1, 2026?

If you continue using the legacy SDKs:
  • It will no longer receive updates or bug fixes
  • Security vulnerabilities may arise over time
  • New API endpoints and features will not be available
  • Fireblocks Support will no longer assist with issues related to the legacy SDKs

​
Will Fireblocks Support provide extended support for the legacy SDKs?

No. There will be no extended support after August 1, 2026. To avoid any disruptions, migrate as soon as possible.