Skip to main content

Get Token Transfers by Account

POST
Retrieves the list of ERC20 token transfers sent or received by a specific address. Results include token contract metadata and the transferred token amount.
Path Parameters
chainstringrequired
Parameter specifying the target chain to query.
networkstringrequired
Parameter specifying the network of the target chain.
Request Body
accountAddressstringrequired
Parameter specifying the account address for balance query. It is a Base58-encoded string of 25-35 characters, always starting with "r".
relationstring
Parameter for filtering transactions where the queried account address is the sender or recipient.
  • from: Filter by sender only.
  • to: Filter by recipient only.
  • both (default): Returns all transactions where the queried address appears in from or to.
currencystring
Parameter specifying the currency symbol to query. Can be entered as an ISO-4217 format string such as "USD" or "EUR".
issuerstring
Parameter specifying the issuer of the currency to query. Enter the issuer account address using a Base58-encoded string of 25-35 characters (starting with "r").
fromLedgerstring
Parameter specifying the starting ledger for the query. You can enter one of the following formats:
  • **ledger index**: Enter ledger number as a decimal string
  • **ledger hash**: 64-character hexadecimal string (excluding 0x prefix)
  • **ledger tag**: Enter "earliest" or "latest" (oldest or most recent ledger)
Notes:
  • If provided without toLedger, results are queried from this ledger to the latest ledger.
  • fromLedger value cannot be greater than toLedger value.
  • If fromLedger and toLedger have the same value, only that ledger is queried.
  • "latest" for fromLedger is only allowed when toLedger is "latest".
toLedgerstring
Parameter specifying the ending ledger for the query. You can enter one of the following formats:
  • **ledger index**: Enter ledger number as a decimal string
  • **ledger hash**: 64-character hexadecimal string (excluding 0x prefix)
  • **ledger tag**: Enter "earliest" or "latest" (oldest or most recent ledger)
Notes:
  • If provided without fromLedger, results are queried from genesis ledger to this ledger.
  • toLedger value cannot be less than fromLedger value.
  • If fromLedger and toLedger have the same value, only that ledger is queried.
  • "earliest" for toLedger is only allowed when fromLedger is "earliest".
fromDatestring
Parameter specifying the start date for the query. Date must follow ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) including seconds.Notes:
  • If provided without toDate, results are queried from this date to the latest block.
  • fromDate value must be equal to or earlier than toDate value.
  • If fromDate and toDate have the same value, only blocks from that date are queried.
  • This field cannot be used together with fromBlock and toBlock.
  • If fromDate and toDate are not provided, the API queries data from the latest 30 days.
toDatestring
Parameter specifying the end date for the query. Date must follow ISO 8601 format (YYYY-MM-DDThh:mm:ss{time zone}) including seconds.Notes:
  • If provided without fromDate, results are queried from genesis block to this date.
  • toDate value must be equal to or later than fromDate value.
  • If fromDate and toDate have the same value, only blocks from that date are queried.
  • This field cannot be used together with fromBlock and toBlock.
  • If fromDate and toDate are not provided, the API queries data from the latest 30 days.
pageinteger
The page parameter specifies the data page to query. It accepts values up to 100; for pages exceeding 100, use the cursor pagination method.The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.
rppinteger
rpp stands for results per page and specifies the page size. You can specify a number greater than 0 and up to 100.
cursorstring
The cursor parameter supports pagination and data navigation between pages. Provide the cursor value from the previous page in the next request to load the next page of data.The page and cursor parameters cannot be used together. If both page and cursor are empty, cursor pagination is used.
withCountboolean
Parameter specifying whether to include the count field in the response. The count field indicates the total number of requested data items. When set to true, the count field is included and response speed may be slower.
Responses
pageinteger
Field representing the page number specified in the page parameter. This field is only included in the response when a value greater than 0 is specified for the page parameter.
rppinteger
Field representing the number of results per page specified in the rpp parameter.
cursorstring
A field for cursor pagination. This value must be provided in the next request to load the next page of data.
countinteger
Field representing the total count of requested data. This field is only included in the response when true is set for the withCount parameter.
Field representing the actual range applied to the query. The same kind of values used in the request's range parameters are returned. A Date-based request returns fromDate and toDate, a Block-based request returns fromBlock and toBlock, and a Ledger-based request returns fromLedger and toLedger; different kinds are never mixed in a single response. When all range parameters are omitted, a default window of the last 30 days is applied and fromDate, toDate are returned. Block and Ledger values are always returned as heights (numbers), even if a hash or tag (latest, earliest) was provided in the request.
fromDatestring
Field representing the start of the query range in Date mode. Returned in ISO 8601 format.
toDatestring
Field representing the end of the query range in Date mode. Returned in ISO 8601 format.
fromBlockinteger
Field representing the start block height of the query range in Block mode.
toBlockinteger
Field representing the end block height of the query range in Block mode.
fromLedgerinteger
Field representing the start ledger index of the query range in Ledger mode.
toLedgerinteger
Field representing the end ledger index of the query range in Ledger mode.
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.
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/token/getTokenTransfersByAccount' \
  -H 'Content-Type: application/json' \
  -H 'X-API-KEY: nodit-demo' \
  -d '{
    "accountAddress": "rMwjYedjc7qqtVWGkcvvLtAp8MuyesLb1Yk",
    "relation": "from",
    "fromDate": "2025-01-01T00:00:00+00:00",
    "toDate": "2025-01-31T00:00:00+00:00",
    "page": 1,
    "rpp": 10
  }'