Skip to main content
[PRO TIP: Sequence Indexer also returns token metadata]When using the Sequence Indexer, pass "includeMetadata": true to your request to query token metadata for any ERC20, ERC721 or ERC1155 contract. See below how to fetch contract-level metadata directly.

Fetch contract metadata of any ERC20, ERC721 or ERC1155 contract address

Sequence Metadata GetContractInfoBatch Method:
  • Request: POST /rpc/Metadata/GetContractInfoBatch
  • Content-Type: application/json
  • Body (in JSON):
    • chainID (string) — the chain id, as a name or number (ie. “1” or “mainnet”, “137” or “polygon”, etc.)
    • contractAddresses (string of strings) — array of contract addresses
Example: GetContractInfoBatch of some contracts on Polygon using an AQAAAAAAAF_JvPALhBthL7VGn6jV0YDqaFY
This code requires an API Access Key from Sequence Builder.

Contract-level Metadata Standards

Additionally, OpenSea added something called contractURI (https://docs.opensea.io/docs/contract-level-metadata).

Search Contract Metadata

Fetch contract-level info metadata for any ERC20, ERC721 or ERC1155 contract address based on a search criteria

Sequence Metadata SearchContracts Method:
  • Request: POST /rpc/Metadata/SearchContracts
  • Content-Type: application/json
  • Body (in JSON):
    • chainID optional (string) — the chain id, as a number (ie. “1” for “mainnet”, “137” for “polygon”, etc.)
    • chainIDs optional (string) — a list of chain ids, as a number (ie. “1” for “mainnet”, “137” for “polygon”, etc.)
    • q (string) — either a search parameter to search contarct info, or, plainly a contract address to search for

Example: SearchContracts of some queries / a contract on Polygon using an AQAAAAAAAF_JvPALhBthL7VGn6jV0YDqaFY
This code requires an API Access Key from Sequence Builder.