List Wallet Transactions
Through this endpoint customers can list Transactions from and to their Wallet. The data returned will include transactionId
, direction
of the transaction - incoming or outgoing, amount
and more.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
Requirednetwork string
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "goerli" are test networks.
-
RequiredwalletId string
Represents the unique ID of the specific Wallet.
Query parameters
-
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user. -
Optionallimit integer
Defines how many items should be returned in the response per page basis.
-
Optionaloffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Response schema
Content-Type: application/json
The request has been successful.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2023-04-25 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.Example : yourExampleString -
Requireddata object
-
Requiredlimit integer
Defines how many items should be returned in the response per page basis.
Example : 50 -
Requiredoffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Example : 0 -
Requiredtotal integer
Defines the total number of items returned in the response.
Example : 100 -
Requireditems arrayExample : Array ( )
-
Requireddirection string
Defines the direction of the transaction, e.g. incoming.
Example : incoming -
Requiredfee object
-
Requiredamount string
Defines the fee for the transaction.
Example : 0.00003 -
RequiredconvertedAmount string
Defines the converted amount of the transaction's fee.
Example : 1.50 -
RequiredexchangeRateUnit string
Defines the exchange rate for the transaction's unit.
Example : USD -
Requiredsymbol string
Defines the unit of the transaction's fee.
Example : ETH
-
-
OptionalfungibleTokens array
Represents fungible tokens'es detailed information
-
Requiredamount string
Defines the amount of the fungible tokens.
Example : 0.254 -
RequiredconvertedAmount string
Defines the tokens' converted amount value.
Example : 0.0034 -
RequiredexchangeRateUnit string
Represents token's exchange rate unit.
Example : USD -
Requiredname string
Defines the token's name as a string.
Example : Tether USD -
Requiredrecipient string
The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one
Example : 0x229f7172eab232d09d2de05a3e3b7b79c9abfe3b -
Requiredsender string
Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender.
Example : 0x1b7aa44088a0ea95bdc65fef6e5071e946bf7d8f -
Requiredsymbol string
Defines the symbol of the fungible tokens.
Example : ETH -
RequiredtokenDecimals integer
Defines the decimals of the token, i.e. the number of digits that come after the decimal coma of the token.
Example : 6 -
Requiredtype string
Defines the specific token type.
Example : ERC-20
-
-
OptionalinternalTransactions array
-
Requiredamount string
Defines the specific amount of the transaction.
Example : 0.001 -
RequiredconvertedAmount string
Represents the converted amount.
Example : 4.30365936483792 -
RequiredexchangeRateUnit string
Defines the base asset symbol to get a rate for.
Example : USD -
RequiredoperationId string
Represents the unique internal transaction ID in regards to the parent transaction (type trace address).
Example : call_0 -
Requiredrecipient string
Represents the recipient address with the respective amount.
Example : 0x07344b7649c5ff096b0317957d9a208931d04d5e -
Requiredsender string
Represents the sender address with the respective amount.
Example : 0x4b8ec9e58a8b08f3803f84fb52d0a50e84444592 -
Requiredsymbol string
Represents the unique unit symbol.
Example : ETH
-
-
OptionalnonFungibleTokens array
Represents non-fungible tokens'es detailed information.
-
RequiredconvertedAmount string
Defines the tokens' converted amount value.
Example : 0.034 -
RequiredexchangeRateUnit string
Represents token's exchange rate unit.
Example : USD -
Requiredname string
Defines the token's name as a string.
Example : Axie Infinity -
Requiredrecipient string
Defines the address to which the recipient receives the transferred tokens.
Example : 0xdac17f958d2ee523a2206206994597c13d831ec7 -
Requiredsender string
Defines the address from which the sender transfers tokens.
Example : 0x65b895f400dae5541d70cbbec07527210158f6e2 -
Requiredsymbol string
Defines the symbol of the non-fungible tokens.
Example : AXS -
RequiredtokenId string
Represents tokens' unique identifier.
Example : 13383 -
Requiredtype string
Defines the specific token type.
Example : ERC-721
-
-
Requiredrecipients array
Represents a list of recipient addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list.
-
Requiredaddress string
The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.
Example : 0x6f61e3c2fbb8c8be698bd0907ba6c04b62800fe5 -
Requiredamount string
Represents the amount received to this address.
Example : 0.00427167 -
Optionallabel string
Defines a plain text string as a label for the recipient.
Example : yourStringHere
-
-
Requiredsenders array
Represents a list of sender addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list.
-
Requiredaddress string
Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender.
Example : 0x6f61e3c2fbb8c8be698bd0907ba6c04b62800fe5 -
Requiredamount string
Represents the total amount sent by this address including the fee.
Example : 0.0001 -
Optionallabel string
Defines a plain text string as a label for the sender.
Example : yourStringHere
-
-
Requiredstatus string
Defines the status of the transaction, if it is confirmed or unconfirmed.
Example : confirmed -
Requiredtimestamp integer
Defines the exact date/time in Unix Timestamp when this transaction was mined, confirmed or first seen in Mempool, if it is unconfirmed.
Example : 1622466746 -
RequiredtransactionId string
Represents the unique TD of the transaction.
Example : b3ddf04d74e5bd57f3ccb5375db6f39d228ed98cfa1ae9bf959b9406fc975f01 -
Requiredvalue object
-
Requiredamount string
Defines the transaction amount.
Example : 0.001 -
RequiredconvertedAmount string
Defines the converted amount of the transaction as a string.
Example : 150 -
RequiredexchangeRateUnit string
Defines the exchange rate's unit.
Example : USD -
Requiredsymbol string
Defines the unit of the transaction's amount.
Example : ETH
-
-
-