Overview

Want to know more about the Provider Network and commercial prerequisites?

Visit our Help Center article about the Provider Network to learn more.

See the Fireblocks Provider Connectivity API v2 documentation on GitHub to learn how to connect your service to Fireblocks.

Registering as a service provider

Note on the supported testing scope

As a best practice, we recommend that your onboarding should cover only up to three stages: Dev → Staging → Production. Additional testing setups for supporting multiple internal environments are not supported by default and require explicit approval.

Once your license agreement for listing your service with Fireblocks is signed, the Fireblocks technical team will request the following connected account registration settings:

1. Display name (e.g., “My Exchange” or “My Exchange Sandbox”)

2. Icon (a 32x32 .svg file)

3. Step-by-step guide for generating an API key for your platform

   1. A public link to your knowledge base is preferred. A shareable document or PDF is also acceptable.

4. Base URL for your API endpoints (e.g., “https://my-service.com/fireblocks”)

5. Will your service provide a sandbox environment?

6. For Off-Exchange capabilities, please provide your CSR file.

7. User credentials for testing

8. Which signing method will your server use for all requests? Please choose one of the supported options by specifying the pre-encoding function, signing algorithm, and post-encoding function during the server onboarding process.

   1. Pre-encoding options:

      1. URL encoded
      2. Base64
      3. HexStr
      4. Base58
      5. Base32

   2. Signing algorithms & possible hash functions:

      1. HMAC (SHA512, SHA3_256, or SHA256)
      2. RSA PKCS1v15 (SHA512, SHA3_256, or SHA256)
      3. ECDSA prime256v1/secp256k1 (SHA256 only)

   3. Post-encoding options: (URL encoding not supported)

      1. Base64
      2. HexStr
      3. Base58
      4. Base32

9. Validation tool results