Get NFTs from contract with metadata
Commonly used to get NFT token IDs with metadata from a collection. Useful for building NFT card displays.
Processing: Realtime
Path Parameters
The chain name eg: eth-mainnet
.
The requested contract address. Passing in an ENS
, RNS
, Lens Handle
, or an Unstoppable Domain
resolves automatically.
Query Parameters
Omit metadata.
Number of items per page. Omitting this parameter defaults to 50.
0-indexed page number to begin pagination.
Filters NFTs based on a specific trait. If this filter is used, the API will return all NFTs with the specified trait. Accepts comma-separated values, is case-sensitive, and requires proper URL encoding.
Filters NFTs based on a specific trait value. If this filter is used, the API will return all NFTs with the specified trait value. If used with "traits-filter", only NFTs matching both filters will be returned. Accepts comma-separated values, is case-sensitive, and requires proper URL encoding.
By default, this endpoint only works on chains where we've cached the assets and the metadata. When set to true
, the API will fetch metadata from upstream servers even if it's not cached - the downside being that the upstream server can block or rate limit the call and therefore resulting in time outs or slow response times on the Covalent side.