Polygon, formerly known as Matic Network, is an extended solution that provides various tools to accelerate and reduce the cost and complexity of transactions on blockchain networks. However, the significant activity on its blockchain nearly paralyzed Ethereum due to escalating transaction costs and congested traffic. The primary purpose of Polygon's inception is to help Ethereum address congestion issues within the chain. It achieves this through a multi-layered platform with numerous side chains, effectively offloading the main platform to scale Ethereum in a efficient and cost-effective manner, providing a simpler framework for building interconnected networks.

On the other hand, another significant use of Polygon is to enhance user experience. Ethereum's transaction fees are prohibitively expensive for ordinary users and the speed is slow. Polygon's high performance, low fees, and speed can address common user issues. The NFT ecosystem on Polygon is thriving, gradually becoming the preferred destination for NFTs from Web2 companies.

According to NFTScan data, as of November 10th, the Polygon network has cumulatively issued 699,833,880 NFT assets, comprising 1,527,885 NFT Collections. There have been 2,515,848,185 NFT tranfer, involving 82,664,934 wallet addresses. The total transaction volume is 976,263,373 MATIC.

Polygon NFTScan: https://polygon.nftscan.com/

Step 1: Create a NFTScan Developer Account

Before utilizing the NFTScan API, visit the NFTScan developer platform and create an account. Go to the official NFTScan website and click on the “Sign Up” button under NFTScan API.

NFTScan Developer: https://developer.nftscan.com/user/signup

Once logged in, find your unique API KEY on the Dashboard. Visit the API documentation and input your API KEY in the designated location. Follow the documentation’s instructions to start using the API services.

In the API documentation, developers can find multiple interface modes to choose from based on their requirements. Additionally, developers can monitor their API usage statistics in the Dashboard, which helps in keeping track of historical data. Furthermore, NFTScan offers each registered developer 1M CU of API calls, which can be used for requesting all NFT API interfaces, and these CU never expire.

Step 2: View Ethereum API Documentation

After successfully registering a developer account and obtaining an API Key, you need to review the NFTScan API documentation. The API documentation contains all available API endpoints and parameters, as well as detailed information on how to build requests and handle responses. Please read the API documentation carefully and make sure you understand how to use the API to obtain the data you need. NFTScan API services are dedicated to helping developers improve their experience in obtaining NFT data analysis.

Currently, NFTScan has the largest and most comprehensive NFT Collection database on the web, supporting full NFT data for 19 blockchains including Ethereum, Solana, BNBChain, Bitcoin, TON, Polygon, zkSync, Aptos, Linea, Base, Avalanche, Arbitrum, Optimism, Scroll, Fantom, Moonbeam, PlatON, Cronos, and Gnosis. The covered NFT data is extensive and diverse, providing a complete set of interfaces to obtain ERC721 and ERC1155 assets as well as transaction, project, and market statistics information. NFTScan now supports more than 60 public interfaces for EVM-compatible chains and a group of equivalent interfaces for Solana, Aptos, Bitcoin, and TON, largely meeting developers’ needs for indexing various types of NFT data.

This comprises three primary model interfaces, each with an overview and explanation of core API fields to assist developers in accessing and utilizing data for their Dapp services under development.

1/ Assets API: "Assets" represent the most critical data fields within NFT, uniquely identifying and describing digital assets. Developers can extract "Assets" data from NFTs on the Polygon to gain comprehensive insights and construct relevant applications. The "Assets" object provides unique identification for digital assets and data about their entire lifecycle, serving as a foundation for developers to understand and utilize NFTs.

2/ Transactions API: The transaction model represents the complete transaction data for an NFT asset on the blockchain, offering developers a full view of an NFT's transaction history. This includes NFT minting, transfers, sales, and other transaction activities, providing developers with an opportunity to deeply understand the flow and evolution of NFT assets within the Polygon ecosystem. NFTScan continuously aggregates NFT transaction market and related contract information from various blockchain networks. Currently, NFTScan has compiled data for tracking and understanding NFT market dynamics, aiding developers in building NFT-based applications and tools.

3/ Collections API: NFTScan retrieves off-chain data related to NFT Collections, including descriptions, social media, and other fundamental information. This data is obtained from the most popular NFT markets provided through various blockchain networks. Additionally, floor price information is centralized data derived from order information on NFT markets, and it can be accessed via API.

1/ Retrieve Assets Series

Here, we use the Get NFTs by contract interface:"/v2/assets/{contract_address}"to retrieve details of NFTs under a specific contract address. The path parameter includes the contract_address as a selection, and in this case, we are querying NFTs from Owlpha.

Clicking "Try it" returns the following data. The data response displays the basic and metadata information for all items in the selected NFT Collection. In this case, we have chosen Owlpha, and the data shows a total of 3333 items under the project, sorted by token_id. For example, item with id 0:

2/ Retrieve Transactions Series

Here, we use the Get transactions by contract interface:"/v2/transactions/{contract_address}"to retrieve NFT transaction records for a specific NFT contract address. Query parameters allow the selection of NFT event types (Mint/Transfer/Sale/Burn), separated by ';'.

Similarly, here, we retrieve the transaction records for Owlpha's NFTs. Based on the Mint event type, the response data includes all key data for items minted in this NFT Collection, such as transaction hash, From and To addresses, block information, gas consumption, transaction timestamp, and other fundamental data characteristics of NFT transactions.

3/ Retrieve Collections Series

Here, we use the Get an NFT collection interface:"/v2/collections/{contract_address}"to retrieve details for the collection with the address 0x12aa01f646fe5c993c66c9c86eddad4e514f6cbc named Owlpha.

4/ Collection Statistics

Here, we use the Collection Top Holder interface:"/v2/statistics/collection/holder/{contract_address}"to mainly return the distribution of holdings within an NFT Collection, which can be referred to at NFTScan Holders: https://www.nftscan.com/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d?module=Holders

5/ Account Statistics Series

6/ Analytic Statistics Series

This series of interfaces are typically used to obtain various data analysis and statistical information on the NFTScan Polygon network. Interfaces like Trade Ranking, Mint Amount, and others allow developers or users to query, analyze, and retrieve statistical data related to specific datasets or metrics. They can be used for various purposes, including market analysis, trend tracking, investment decisions, and understanding the nature of specific data.

Reference: https://polygon.nftscan.com/analytics

7/ Refresh Metadata

Interfaces like Refresh Metadata can assist developers or users in submitting backend tasks to refresh metadata. Once reviewed, these tasks will refresh the specified item or the entire contract metadata.

8/ Other

Once developers find the necessary Polygon API interfaces and parameters in the NFTScan API documentation, they can use their chosen programming language (such as Python, Java, JavaScript, etc.) to write API request code. Here is an example demonstrating how to use Python to request transaction records for an NFT contract address. In this example, the contract address used is 0x12aa01f646fe5c993c66c9c86eddad4e514f6cbc,and the NFT interface is "/v2/transactions/{contract_address}".

In the above example, we constructed the API endpoint and contract address, then used the requests.get method to initiate a GET request to retrieve transaction records for the NFT contract address. If the request is successful, developers can extract transaction information from the JSON data in the API response and handle it accordingly.

NFTScan is the world’s largest NFT data infrastructure, including a professional NFT explorer and NFT developer platform, supporting the complete amount of NFT data for 19 blockchains including Ethereum, Solana, BNBChain, Arbitrum, Optimism, and other major networks, providing NFT API for developers on various blockchains.

Official Links:

NFTScan: https://nftscan.com

Developer: https://developer.nftscan.com

Twitter: https://twitter.com/nftscan_com

Discord: https://discord.gg/nftscan