- US Sandbox:
https://sandbox-api.fireblocks.io/v1 - US Mainnet/Testnet:
https://api.fireblocks.io/v1 - For EU Mainnet or Testnet workspaces:
https://eu-api.fireblocks.io/v1 - For EU2 Mainnet or Testnet workspaces:
https://eu2-api.fireblocks.io/v1
X-API-Key- The API key created from your Fireblocks workspace.Authorization- This value should be set toBearer <Access Token>. The access token is a Base64-encoded JSON Web Token (JWT).
Before you begin: Ensure you have created an API User ID (API key) in your Fireblocks Console.
JWT structure
Authorization: Bearer <JWT>
The JSON Web Token (JWT) payload field should contain the following fields:
uri- The URI part of the request (e.g., /v1/transactions).nonce- Unique number or string. Each API request must have a unique nonce.iat- The time at which the JWT was issued, in seconds since Epoch.exp- The expiration time on and after which the JWT must not be accepted for processing, in seconds since Epoch. (Must be less thaniat+30sec.)sub- The API key.bodyHash- Hex-encoded SHA-256 hash of the raw HTTP request body.
Set up request headers via the Fireblocks SDKs
You can set up the request headers using the Fireblocks API SDKs:When using the above SDK code examples to sign a request, be sure to replace
apiKey with your own API key.