POSTGet Native Token Transfers By Account
https://web3.nodit.io/v1/bitcoin/mainnet/native/getNativeTokenTransfersByAccountRetrieves the native token transfer history associated with a specific address. The token type may vary depending on the selected chain. (e.g., For Bitcoin, you can query BTC transfer history.)
Parameter to specify the target chain for the query.
Parameter to specify the network of the target chain. Supported networks may vary depending on the chain.
Parameter specifying the account address to query.
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.
Parameter specifying the starting block for the query. You can enter one of the following formats:
- block number: Enter block number as a decimal string.
- block hash: 64-character hexadecimal (excluding "0x").
- block tag: Use "earliest" or "latest" to specify the first block or the most recent block.
Notes:
- This field cannot be used together with
fromDateandtoDate. - If provided without fromBlock, results are queried from genesis block to this block.
- toBlock value cannot be less than fromBlock value.
- If fromBlock and toBlock have the same value, only that block is queried.
- "earliest" for toBlock is only allowed when fromBlock is "earliest".
- If
fromBlockandtoBlockare not provided, the API queries data from the latest 30 days.
Parameter specifying the ending block for the query. You can enter one of the following formats:
- block number: Enter block number as a decimal string.
- block hash: 64-character hexadecimal (excluding "0x").
- block tag: Use "earliest" or "latest" to specify the first block or the most recent block.
Notes:
- This field cannot be used together with
fromDateandtoDate. - If provided without fromBlock, results are queried from genesis block to this block.
- toBlock value cannot be less than fromBlock value.
- If fromBlock and toBlock have the same value, only that block is queried.
- "earliest" for toBlock is only allowed when fromBlock is "earliest".
- If
fromBlockandtoBlockare not provided, the API queries data from the latest 30 days.
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
fromDateandtoDateare not provided, the API queries data from the latest 30 days.
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
fromDateandtoDateare not provided, the API queries data from the latest 30 days.
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.
rpp stands for results per page and specifies the page size. You can specify a number greater than 0 and up to 100.
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.
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.
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.
Field representing the number of results per page specified in the rpp parameter.
A field for cursor pagination. This value must be provided in the next request to load the next page of data.
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 start of the query range in Date mode. Returned in ISO 8601 format.
Field representing the end of the query range in Date mode. Returned in ISO 8601 format.
Field representing the start block height of the query range in Block mode.
Field representing the end block height of the query range in Block mode.
Field representing the start ledger index of the query range in Ledger mode.
Field representing the end ledger index of the query range in Ledger mode.
Array containing detailed information for each sender in the transaction. Each object includes the sender's address, amount sent, and sender index.
예: [object Object]
Index of the sender; uniquely identifies the sender in the transaction. Starts at 0; assigned sequentially when multiple senders exist.
예: 0
Address of the sender. The address used by the sender to send Bitcoin in the transaction; follows P2PKH, P2SH, Bech32, or Bech32m format.
예: 2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1
Amount sent by the sender in the transaction, displayed in BTC units. Amount allows up to 8 decimal places.
예: 0.0873472
Array containing detailed information for each recipient in the transaction. Each object includes the recipient's address, amount received, and recipient index.
예: [object Object],[object Object]
Index of the recipient; uniquely identifies the recipient in the transaction. Starts at 0; assigned sequentially when multiple recipients exist.
예: 0
Address of the recipient. The address used by the recipient to receive Bitcoin; follows P2PKH, P2SH, Bech32, or Bech32m format.
예: 2MzakdGTEp8SMWEHKwKM4HYv6uNCBXtHpkV
Amount received by the recipient in the transaction, displayed in BTC units. Amount allows up to 8 decimal places.
예: 0.00144
Transaction fee; the amount paid by the sender to include the transaction in the blockchain network. Amount is displayed in BTC units.
예: 0.0016932
Unique hash value of the transaction. A 64-character hexadecimal string generated from transaction data; uniquely identifies the transaction.
예: 1ec73b0f61359927d02376b35993b756b1097cb9a857bec23da4c98c4977d2b2
Unique ID of the transaction. A value that uniquely identifies each transaction; displayed as a 64-character hexadecimal string.
예: 4b66461bf88b61e1e4326356534c135129defb504c7acb2fd6c92697d79eb250
Indicates the height of the block containing the transaction. Integer value representing the order in the blockchain.
예: 100000
Unique hash value of the block containing the transaction. A 64-character hexadecimal string generated using the SHA-256 algorithm; uniquely identifies the block.
예: 0000000000000000000a8ed7f3e6c1c2d21cbb5f
Creation time of the block containing the transaction. Value in UNIX timestamp format; represents when the block was created in UTC, in seconds.
예: 1400000000