List transactions

get

https://glacier-api.avax.network/v1/chains/{chainId}/addresses/{address}/transactions

Returns a list of transactions where the given wallet address had an on-chain interaction for the given chain. The ERC-20 transfers, ERC-721 transfers, ERC-1155, and internal transactions returned are only those where the input address had an interaction. Specifically, those lists only inlcude entries where the input address was the sender (from field) or the receiver (to field) for the sub-transaction. Therefore the transactions returned from this list may not be complete representations of the on-chain data. For a complete view of a transaction use the /chains/:chainId/transactions/:txHash endpoint.

Filterable by block ranges.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

chainId

string

required

A supported evm chain id, chain alias or blockchain id. Use the /chains endpoint to get a list of supported chain ids.

address

string

required

A wallet address.

Query Params

pageToken

string

A page token, received from a previous list call. Provide this to retrieve the subsequent page.

pageSize

integer

1 to 100

Defaults to 10

The maximum number of items to return. The minimum page size is 1. The maximum pageSize is 100.

startBlock

number

The block range start number, inclusive. If endBlock is not defined when startBlock is defined, the end of the range will be the most recent block.

endBlock

number

The block range end number, exclusive. If startBlock is not defined when endBlock is defined, the start of the range will be the genesis block.

sortOrder

string

enum

The order by which to sort results. Use "asc" for ascending order, "desc" for descending order. Sorted by timestamp or the sortBy query parameter, if provided.

Allowed:

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful response

400Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.

401When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.

403When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.

404The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist.

429This error is returned when the client has sent too many, and has hit the rate limit.

500The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration.

502This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.

503The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected.