NFTs by Wallet(s)

This endpoint is commonly used to pass specific wallet addresses to get back the metadata of the NFTs held by them:
To supply multiple values, provide them comma separated in the query params, e.g., chains=polygon,ethereum&wallet_addresses=0xa12,0xb34. ENS addresses can also be provided for the wallet_addresses.
NFTs are sorted by most recently acquired to least recently acquired.
Query Params
string
required
Defaults to polygon,ethereum

Name of the chain(s), comma-separated for multiple values (e.g., polygon,ethereum)

string
required
Defaults to 0xfa6E0aDDF68267b8b6fF2dA55Ce01a53Fad6D8e2

Owner wallet address(es), comma-separated for multiple values (e.g., 0xa12,0xb34). Limit of 20 addresses.

string
enum

Include a field "queried_wallet_balances" that includes the quantity owned and acquired dates of each passed wallet address on each NFT response body (useful for NFTs with many owners, such as ERC1155s) (pass queried_wallet_balances=1)

Allowed:
string

NFT contract addresses to filter on. Limit of 20 addresses.

string

List of Collection IDs to filter on, comma-separated. Limit of 40 collection IDs.

string
enum

Include the total distinct count of tokens in the response (pass count=1)

Allowed:
string

Used to retrieve the next page of results

int32
Defaults to 50

Limit. Defaults to 50, capped at 50.

Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json