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.
Request payload example
This example demonstrates the raw and decoded JWT payload sent by the Co-Signer to the Callback Handler. Additionally, it includes a test private key that signed the payload and the corresponding public key that should be used for signature validation:The provided Private Key is for example purposes only and should not be used in your production system.
The provided example may contain properties that are not sent by default. Customers should ensure they DO NOT expect to receive values that are not documented in the Approve Transactions and Approve Configuration Changes sections.
Response payload example
This example demonstrates the raw and decoded JWT response returned from the Callback Handler to the Co-signer. The response is signed using the Callback Handler’s private key. The Co-signer then verifies the signature using the predefined public key configured during the Co-signer installation phase. For simplicity, the examples use the same private/public key pair as in the Request Example section:Please note that the iat value is not required in the actual response and will be ignored by the Co-Signer. It is included here because the JWT signature library automatically adds this field.
API Co-Signer basic Callback Handler server example
Here is a code example for a basic Callback Handler application. The application is designed to handle POST requests from the Co-signer at the endpoint /v2/tx_sign_request.- It validates that the received payload is signed with the correct private key.
- If the verification is successful, it responds with a 200 status code, the
REJECTaction, and therejectionReasonin the response body. - If the verification fails, it responds with a 401 status code.