// the find
fireblocks/fireblocks-sdk-js
Typescript & Javascript SDK for developers using Fireblocks API
Official TypeScript/JavaScript SDK for the Fireblocks institutional crypto custody API. If you're building on Fireblocks — moving assets, managing vaults, handling transaction signing — this is the starting point. Not useful to anyone who isn't already a Fireblocks customer with API credentials.
First-party SDK means the types track the actual API; you're not guessing at shapes from a community wrapper. The IAuthProvider interface lets you swap in a custom JWT signer, which matters if you're managing keys outside the default flow. Axios interceptor support is a practical touch — you can attach logging or retry logic without forking the SDK. The V4 migration guide exists and is version-documented in CHANGELOG.md, which is more than most vendor SDKs bother with.
84 stars and 72 forks for an official SDK from a multi-billion dollar custody platform signals that most serious integrators are using the REST API directly or a backend language SDK — the JS SDK is clearly not the primary integration path. The repo still has `.DS_Store` committed at the root, which is embarrassing for an official release. Error handling just surfaces raw AxiosError — there's no typed error class hierarchy, so catching specific Fireblocks error codes means string-matching `error.response.data.code`. No test files visible in the directory tree, which for a financial transactions SDK is a genuine problem.