PolygonScan API Overview
The PolygonScan API provides programmatic access to the Polygon blockchain, allowing developers to build applications that query on-chain data without running their own node. The API uses a RESTful architecture and is closely modeled after the Etherscan API, making it familiar for Ethereum developers working with Polygon.
Current API Status
The PolygonScan API is currently operational across all key endpoint categories. Response times are within normal parameters. Developers can access the API after registering for a free API key at polygonscan.com.
Key API Endpoint Categories
- Transaction Details: Retrieve full information about a specific transaction using its hash, including status, gas used, input data, and internal transactions.
- Address Balance: Query the current POL balance and token holdings for any wallet address.
- Token Information: Access ERC-20 and ERC-721 token metadata, total supply, holder counts, and transfer history.
- Smart Contract Verification: Verify source code for smart contracts, retrieve ABI, and access read/write contract functions.
- Block Data: Retrieve block information including miner, timestamp, transaction count, and gas used.
- Gas Tracker: Query current gas price recommendations for safe, standard, and fast transaction confirmation speeds.
API Rate Limits and Authentication
Free tier API keys support up to 5 calls per second and up to 100,000 calls per day. For applications requiring higher throughput, PolygonScan offers paid API plans. All requests must include your API key as a query parameter. Requests without a valid key are rate-limited more aggressively and may return error responses during periods of high API load.
How to Check API Status Independently
If you are experiencing API errors, check whether the issue is global or isolated to your key. A simple diagnostic call to the PolygonScan API using a basic endpoint — such as querying the latest block number — will confirm whether the API is responding normally. If the call succeeds but your usual queries fail, the issue may be specific to certain endpoints or your API key configuration.