Retrieves the transactions where this address was either the originator or a recipient.
Note that transactions are returned in descending order by default (block number and transaction index), which means the most recent transactions are on page 0, and the oldest transactions are on the last page.
If you intend to traverse all the transactions, it is recommended to specify the flag direction=ascending
, which will guarantee that the pagination is stable and will not change with the arrival of new transactions.
The id of the blockchain
bitcoin-mainnet
, bitcoin-abc-mainnet
, ethereum-mainnet
, litecoin-mainnet
address to retrieve transactions for
Filter by transactions for this block number.
Filter by transactions for this "from" address.
Filter by transactions for this "to" address
Indicates whether or not to include log information for each transaction, if available (false|true).
Decodes transactions input via known ABIs.
Indicates whether or not to include token transfers information for each transaction, if available (false|true).
Indicates whether or not to include price data with the results. Options: true, false.
Filter by transactions which happened after this date.
Filter by transactions which happened before this date.
The validation method to be added to the response: none
, basic
, full
. Default: none
. <a href="https://docs.amberdata.io/reference#section-validation-method">More Details.</a>
The order in which to return the results (ascending or descending). By default, records are returned in descending order, so the most recent records are returned first.
The page number to return.
The number of records per page (maximum 1000)
200
The response is of type object
.