Skip to main content
POST
get_wallet_transactions

Reading the result

The response example uses made-up values and shows selected fields. Fields vary by network and available data.
  • data contains transaction rows. direction is relative to the queried wallet; amount is the absolute token amount.
  • peer identifies the counterparty. tx_hash and chain identify the on-chain transaction; a transaction can include several transfers.
  • summary covers the returned rows. Check pagination before treating the result as complete. Row details vary by network and available data.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
address
string
required

Wallet address to analyze on the selected network.

network
string
required

Network to query, for example ethereum. See Supported Networks for coverage.

from_date
string

Start of the requested date range, in YYYY-MM-DD format. Omit to use the default date range.

to_date
string

End of the requested date range, in YYYY-MM-DD format. Omit to use the default date range.

page
integer
default:1

Page number to retrieve, starting at 1.

records_per_page
integer
default:20

Number of records to request per page.

Response

Recent transactions for a wallet from chain-native sources. Supports paging. Fields vary by network and available data. Check for status: no_data, status: error, or an error field even when HTTP status is 200. See Errors & status.

Response fields depend on the network and available data. The example shows selected fields; see Reading the result for details.