contractAddress
: [string] - contract address for the NFT collectionwithMetadata
: [boolean] - (optional) if set to true
, returns NFT metadata; otherwise will only return tokenIds. Defaults to false
.startToken
: [string] - (optional) an offset used for pagination. Can be a hex string, or a decimal.limit
: [int] - (optional) sets the total number of NFTs returned in the response.
Defaults to 100.startToken
: startToken
param is used to paginate results.startToken
is specified, the query will start from the lowest tokenId. Each response will return a nextToken
that can be passed back to the API as a startToken
to return the next page of results for the given NFT collection (if applicable). You can also use any tokenId from the collection as the startToken
, and the results in the response will start from that offset.
See the 'examples' section for an example of how to use this parameter to fetch all of the NFTS in a collection.nfts
: list of objects that represent NFTs stored under the queried contract address. id
tokenId
: [string] Hexadecimal token ID for NFTtokenMetadata
tokenType
: "ERC721
" or "ERC1155
"tokenUri
:raw:
uri representing the location of the NFT's original metadata blob. This is a backup for you to parse when the metadata
field is not automatically populated.gateway:
public gateway uri for the raw uri above.metadata
: relevant metadata for NFT contract. This is useful for viewing image url, traits, etc. without having to follow the metadata url in tokenUri
to parse manually.
For more info on NFT responses: check out the NFT API FAQ.nextToken
: [string] an offset used for paginationyour-api-key
/getNFTs...startToken
and nextToken
fields are designed to allow users to fetch all of the NFTs in a collection using the following pattern: