Get Transactions By Hashes
POST
Retrieves information for multiple transactions. Up to 1,000 transactions can be queried.
🚧 Getting a 429 error? Check your subscription plan!
A 429 error may occur when the throughput limit of your subscribed plan is exceeded.
For example, the Starter plan has a limit of 300 CU per second, so calling an API that consumes 350 CU while on the Starter plan may result in a 429 error.
Check the CU consumption of the API you are using on the Compute Unit Costs page, and consider upgrading to a higher plan if you need more throughput!
Path Parameters
chainstringrequired
Parameter specifying the target chain to query.networkstringrequired
Parameter specifying the network of the target chain.Request Body
transactionHashesarrayrequired
withBalanceChangesboolean
Optional parameter determining whether to include the balanceChanges field in the response. balanceChanges contains balance change details for native token (XRP) and IOU tokens. Response speed may be slower when set to true.withTokenTransfersboolean
Optional parameter determining whether to include the tokenTransfers field in the response. tokenTransfers contains IOU token transfer history. Response speed may be slower when set to true.Responses
ledgerIndexintegerrequired
Sequence number of the ledger that contains the transaction. Used to identify which ledger the transaction was recorded in.ledgerTimestampintegerrequired
Returns the close time of the ledger containing this transaction as a Unix timestamp. In the XRP Ledger, close time is recorded in seconds since the Ripple Epoch (January 1, 2000 00:00 UTC). Standard Unix timestamps use the Unix Epoch (January 1, 1970 00:00 UTC); the difference between them is 946,684,800 seconds. Thus ledgerTimestamp is the recorded close time plus 946,684,800 seconds.transactionIndexintegerrequired
Index indicating the processing order of the transaction within the ledger. Used to determine the order of transactions in the ledger.transactionHashstringrequired
A 256-bit (64-digit hexadecimal) cryptographic hash that uniquely identifies the transaction. Used for transaction data integrity and identification.transactionTypestringrequired
String indicating the transaction type. Distinguishes various types such as Payment, OfferCreate, EscrowCreate, and is classified by processing method.transactionResultstringrequired
String indicating the transaction processing result, displayed as a result code such as 'tesSUCCESS'. Used to verify whether the transaction succeeded.accountstringrequired
Account address that initiated the transaction. The account address is a Base58-encoded string 25-35 characters in length, starting with 'r'.sequenceintegerrequired
Sequential number of transactions issued by the account, used to prevent duplicate submissions and replay attacks.lastLedgerSequenceinteger
Sequence number of the last ledger in which the transaction is valid. The transaction will not be processed in ledgers after this value.ticketSequenceinteger
For ticket-based transactions, the ticket number. Only present for transactions that use tickets.signingPubKeystringrequired
Public key used for the transaction signature, typically expressed as a 33-byte (66-digit hexadecimal) compressed public key.txnSignaturestring
Transaction signature value generated with signingPubKey. Used for transaction verification and authentication.feestringrequired
Transaction processing fee, expressed as an XRP amount (in XRP units) as a string. In XRP units where 1 XRP equals 1,000,000 drops.flagsstring
Flag values applied to the transaction. Each bit controls a specific option or behavior; the default is often 0.accountTxnIdstring
256-bit hash identifying another transaction. If set, this transaction is valid only when it matches the sending account's most recent transaction ID. Used to prevent duplicate transaction submission or to verify that account state has not changed since a previous transaction.sourceTaginteger
32-bit unsigned integer that the sender may specify when sending a transaction. Primarily used to identify the sending user from shared addresses (e.g. exchange or hosted wallet). Provides additional information so the receiver can determine "who sent it".For multi-signed transactions, an array of objects containing each signer's information. Each object includes signer account, signing public key, signature value, etc.
accountstringrequired
Account address that signed the transaction. The account address is a Base58-encoded string 25-35 characters in length, starting with 'r'.txnSignaturestringrequired
Transaction signature value generated by the signing account, used for transaction validity verification. This signature is DER-encoded; length varies but is typically 70-80 hexadecimal characters.signingPubKeystringrequired
Public key used for the transaction signature, typically a 33-byte compressed public key expressed as a hexadecimal string (about 66 characters).Array of objects containing memo data attached to the transaction. Each memo object provides additional information such as memo content and format.
memoDatastring
Arbitrary hexadecimal string containing the memo content. Can be freely specified.memoFormatstring
Hexadecimal string describing the memo encoding. Typically used to specify MIME type.memoTypestring
Hexadecimal string describing the memo type. Typically represents a unique relation such as a URL defined in RFC 5988.transactionCategorystringrequired
Enumeration string indicating the transaction category. Possible values include AMM, Check, Escrow, Offer, Payment, Payment Channel; each category is defined by the corresponding transaction type (e.g. Payment, OfferCreate).transactionDetailsoneOf
Object containing details related to the transaction. May include additional data and fields required for transaction processing.First asset used in the AMM pool. Composed with Asset2; cannot have the same currency code and issuer.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").Second asset used in the AMM pool. Composed with Asset; cannot have the same currency code and issuer.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").Amount of the first asset added to the AMM pool. In AMMWithdraw, indicates the first asset to withdraw.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.Amount of the second asset added to the AMM pool. In AMMWithdraw, indicates the second asset to withdraw.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.tradingFeeinteger
Trading fee rate set in 1/100,000 units. 1 equals 0.001%, maximum value is 1000 (1%).Sets the maximum valid price in AMMDeposit. In AMMWithdraw, sets the minimum guaranteed price.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.Quantity of LP tokens returned from the AMM pool.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.Quantity of LP tokens issued in return for providing liquidity to the AMM pool.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.Sets the minimum bid amount. Setting this higher makes it harder for others to place higher bids.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.Sets the maximum bid amount. The transaction fails if the bid amount exceeds bidMax.
currencystring
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstring
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestring
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.authAccountsarray
Defines up to 4 additional accounts eligible for discounted fees. The transaction sender's address cannot be included. Each account address is a Base58-encoded string 25-35 characters in length, starting with 'r'.holderstring
Account address targeted for clawback in AMMClawback transaction. An account holding specific assets in the AMM pool; the issuer may claw back assets from this account.affectedNodesIndexintegerrequired
Index of the node within the AffectedNodes array.accountstringrequired
Account address whose balance was changed by the transaction. The account address is a Base58-encoded string 25-35 characters in length, starting with 'r'.currencystringrequired
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstringrequired
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").previousBalancestringrequired
Amount of the asset before the change. For XRP, expressed in XRP units where 1 XRP equals 1,000,000 drops.finalBalancestringrequired
Amount of the asset after the change. For XRP, expressed in XRP units where 1 XRP equals 1,000,000 drops.balanceChangestringrequired
Amount changed by the transaction, including whether it increased or decreased. For XRP, expressed in XRP units where 1 XRP equals 1,000,000 drops.ledgerIndexinteger
Integer value indicating the creation order of the ledger, used to identify its position (sequence number) on the network. Required field in the Transfer query API.ledgerTimestampinteger
The ledger's close time converted to a Unix timestamp. The close time recorded in the ledger header is expressed in seconds since the Ripple Epoch (January 1, 2000 00:00 UTC), which differs from the Unix Epoch (January 1, 1970 00:00 UTC) by 946,684,800 seconds. Thus ledgerTimestamp is the recorded close time plus 946,684,800 seconds. Required field in the Transfer query API.transactionIndexinteger
Index indicating the processing order of the transaction within the ledger. Required field in the Transfer query API.transactionHashstring
A 256-bit (64-digit hexadecimal) cryptographic hash that uniquely identifies the transaction. Used for transaction data integrity and identification. Required field in the Transfer query API.transactionTypestring
String indicating the transaction type. Distinguishes various types such as Payment, OfferCreate, EscrowCreate, and is classified by processing method. Required field in the Transfer query API.affectedNodesIndexintegerrequired
Index of the node within the AffectedNodes array.fromstringrequired
Account address that initiated the transaction. The account address is a Base58-encoded string 25-35 characters in length, starting with 'r'.tostringrequired
Recipient account address of the transaction. The account address is a Base58-encoded string 25-35 characters in length, starting with 'r'.currencystringrequired
Indicates the currency code of the asset. Typically uses ISO 4217 standard codes (e.g. "USD", "EUR"), but 160-bit custom codes may also be used. Custom codes are expressed as 40-character hexadecimal strings and are used for proprietary assets defined by specific projects or platforms (e.g. "SOLO"). For XRP, the fixed string "XRP" is used in the currency field and is returned in the same structure as IOU assets.issuerstringrequired
The address of the account that issued the asset. Even with the same currency code, asset credibility and risk may vary by issuer. Thus, the XRP Ledger uniquely identifies assets by the combination of currency code and issuer. Each asset's trustworthiness largely depends on the issuer's reputation. This field is a Base58-encoded string 25-35 characters in length, always starting with 'r'. XRP is a native asset with no issuer; in that case, issuer is shown as an empty string ("").valuestringrequired
Returns the asset amount as a string. The amount format varies by currency. For \"XRP\", the value is in standard XRP units where 1 XRP equals 1,000,000 drops. IOU assets are expressed based on the precision defined by the issuer.balanceOutAccountsarray
List of account addresses whose final net balance change is less than zero (decreased) after summing all sends and receives in the transaction. Reflects both XRP and IOU token balance changes.balanceInAccountsarray
List of account addresses whose final net balance change is greater than zero (increased) after summing all sends and receives in the transaction. Reflects both XRP and IOU token balance changes.balanceChangedTokensarray
List of token identifiers with non-zero final net balance change when summing the entire transaction. Each item follows the 'currency-issuer' format.codestringrequired
Code identifying the cause of the failed request.messagestringrequired
Detailed message including the name and value of the invalid parameter.{"code": "MISSING_REQUIRED_PARAMETER","message": "Missing required parameter: { PARAMETER_NAME }"}
cURL
curl -X POST 'https://web3.nodit.io/v1/xrpl/mainnet/blockchain/getTransactionsByHashes' \-H 'Content-Type: application/json' \-H 'X-API-KEY: nodit-demo' \-d '{"transactionHashes": ["C466ACB9B54128A433E7FC9EFA49030A547AA06F40A3508BA90EF9D5984BADC3","A14DE85FA752026D5EE591BE0C99B5BC2814CD8FBE744A07EC0BC430254C34DA"],"withBalanceChanges": false,"withTokenTransfers": false}'