Get transaction history
Get the transaction history for your workspace.
Endpoint Permissions: Admin, Non-Signing Admin, Signer, Approver, Editor, Viewer.
Query Parameters
Response
A list of transactions
The primary status of the transaction. For details, see Primary transaction statuses.
See Transaction substatuses for the list of transaction sub statuses.
The hash of the transaction on the blockchain.
-
This parameter exists if at least one of the following conditions is met:
-
The transaction’s source type is
UNKNOWN,WHITELISTED_ADDRESS,NETWORK_CONNECTION,ONE_TIME_ADDRESS,FIAT_ACCOUNTorGAS_STATION. -
The transaction’s source type is
VAULTand the status is either:CONFIRMING,COMPLETED, or was in any of these statuses prior to changing toFAILEDorREJECTED. In some instances, transactions in statusBROADCASTINGwill include the txHash as well. -
The transaction’s source type is
EXCHANGE_ACCOUNTand the transaction’s destination type isVAULT, and the status is either:CONFIRMING,COMPLETED, or was in any of these status prior to changing toFAILED.
-
-
In addition, the following conditions must be met:
-
The asset is a crypto asset (not fiat).
-
The transaction operation is not RAW or
TYPED_MESSAGE.
-
TRANSFER- Transfers funds from one account to another. UTXO blockchains allow multi-input and multi-output transfers. All other blockchains allow transfers with one source address and one destination address.MINT- Mints new tokens. Supported for Stellar, Ripple and EVM-based blockchains.BURN- Burns tokens. Supported for Stellar, Ripple and EVM-based blockchains.CONTRACT_CALL- Calls a smart contract method for web3 operations on any EVM blockchain. The Fireblocks development libraries are recommended for building contract call transactions.TYPED_MESSAGE- An off-chain message in either Ethereum Personal Message or EIP712 format. Use it to sign specific readable messages that are not actual transactions. Learn more about typed messages.RAW- An off-chain message with no predefined format. Use it to sign any message with your private key, including protocols such as blockchains and custom transaction types that are not natively supported by Fireblocks. Learn more about raw signing transactions.ENABLE_ASSET- Algorand, DigitalBits, Solana, and Stellar require an on-chain transaction to create an asset wallet and enable the deposit address. This transaction is automatically created when adding assets on these blockchains at a vault account.STAKE- Assign assets to a staking pool managed by a staking validator. Supported for Stellar and EVM-based blockchains. This transaction is automatically created when performing staking operations.SUPPLY_TO_COMPOUND- Deprecated since April 1st, 2023. Older transactions may have this as their operation, in case users in the workspace have used the direct integration between Fireblocks and the Compound DeFI protocol.REDEEM_FROM_COMPOUND- Deprecated since April 1st, 2023. Older transactions may have this as their operation, in case users in the workspace have used the direct integration between Fireblocks and the Compound DeFI protocol.PROGRAM_CALL- In Solana refers to invoking on-chain programs (smart contracts) to execute transactions and interact with the blockchain.APPROVE- Enables the approve function for a smart contract or wallet to withdraw from a designated wallet. Learn more.SOROBAN_CALL- Invokes a Soroban smart contract on the Stellar blockchain.
TRANSFER, BURN, CONTRACT_CALL, MINT, RAW, TYPED_MESSAGE, ENABLE_ASSET, STAKE, REDEEM_FROM_COMPOUND, SUPPLY_TO_COMPOUND, PROGRAM_CALL, APPROVE, SOROBAN_CALL The ID of the asset to transfer for TRANSFER, MINT, BURN, ENABLE_ASSET, or STAKE operations. See the list of supported assets and their IDs on Fireblocks.
For account based assets only, the source address of the transaction.
Note: If the status is CONFIRMING, COMPLETED, or has been CONFIRMING; then moved forward to FAILED or REJECTED, then this parameter will contain the source address. In any other case, this parameter will be empty.
Address where the asset were transferred. Notes:
- For Multi destination transactions, this parameter will be empty. In this case, you should refer to the destinations field.
- If the status is
CONFIRMING,COMPLETED, or has beenCONFIRMING; then moved forward toFAILEDorREJECTED, then this parameter will contain the destination address. In any other case, this parameter will be empty.
Decoded data for CONTRACT_CALL operations. The Fireblocks development libraries are recommended for setting this parameter's value.
Decoded instruction list for PROGRAM_CALL (Solana) operations. Each entry represents one instruction in the transaction, in execution order. Fireblocks-injected instructions (e.g. AdvanceNonceAccount, ComputeBudget) appear first, followed by the original dApp instructions.
For transactions initiated via this Fireblocks workspace, when set to true, the fee is deducted from the requested amount.
Note: This parameter can only be considered if a transaction's asset is a base asset, such as ETH or MATIC. If the asset can't be used for transaction fees, like USDC, this parameter is ignored and the fee is deducted from the relevant base asset wallet in the source account.
Canton transaction context. Present on transactions that belong to a Canton flow, and the authoritative signal that a transaction IS one — do not branch on operation, which is CANTON_CALL for customer-initiated calls but TRANSFER for an incoming Canton transfer offer. No cantonDetails at all means the transaction is not a Canton item.
The service sets exactly one of offerResponse, call or settlement. That is a guarantee about what is sent, NOT a constraint this schema enforces: the three are declared as independent optional properties on purpose, so that a response carrying a block a client does not yet know about — or a row written before a block type existed — still validates. Response schemas here stay additive. Read the block you recognise; do not reject a payload for the shape of the others.
Every block carries version, stamped when the transaction is created and never changed — a transaction written today keeps its shape, so version is how you know which shape you are reading.
The information about your Transaction Authorization Policy (TAP).
Additional protocol / operation specific key-value parameters:
For UTXO-based blockchain input selection, add the key inputsSelection with the value set to the input selection structure. The inputs can be retrieved from the Retrieve Unspent Inputs endpoint.
For RAW operations, add the key rawMessageData with the value set to the raw message data structure.
For SOROBAN_CALL operations, add the key sorobanCallData with the value set to an object containing envelopeXdr - a base64 encoded, unsigned Stellar TransactionEnvelope holding the contract invocation.
For CONTRACT_CALL operations, add the key contractCallData with the value set to the Ethereum smart contract Application Binary Interface (ABI) payload. The Fireblocks development libraries are recommended for building contract call transactions.
For exchange compliance (e.g., Binance) and Travel Rule purposes, include the key piiData containing a custom JSON structure with Personally Identifiable Information (PII) relevant to the transaction. This data must be fully encrypted by the sender before being submitted to the Fireblocks API. The recommended encryption method is hybrid encryption using AES-256-GCM for the payload and RSA-OAEP for key exchange, with the recipient exchange's public key. development libraries
Note: rawMessageData, contractCallData, sorobanCallData, and inputsSelection cannot be used together in the same call.
A JSON used to store additional data that is blockchain-specific.
TON (Early Access). For TON transfers the object contains:
All amounts inside feeBreakdowns are integer strings in nanoTON (1 TON = 1,000,000,000 nanoTON), unlike the top-level feeInfo, which is in TON.
Each entry of feeBreakdowns contains:
A Jetton transfer sent without a forward amount sends the recipient no notification, so the recipient wallet has no transaction and pays nothing: its entry has no txHash, all its figures are "0" and feeInfo.recipient.feesDeducted is "0.000000000". An amount that could not be established from on-chain data is reported as no entry and no struct in feeInfo for that role.
Only the wallets that belong to the notified workspace appear in feeBreakdowns. A transfer between two wallets of your own workspace is a single transaction and carries an entry for each wallet (tell them apart by role), and the top-level feeInfo has both a sender and a recipient struct.
blockchainInfo is kept to 2,048 characters. When a very long message pushes a TON transfer over that, the optional details are dropped to make it fit: feeBreakdowns go first when the message fits without them, messageContent goes when the breakdowns fit without it, and both go when neither does. The hashes, tonTransferType, isFeeExcess and the top-level feeInfo are always kept.
Example of a Jetton transfer sent from one of your wallets (addresses and hashes are placeholders):