Total Supply/Circulating Supply API Endpoint Requirement
Last updated: October 2, 2026
CoinGecko supports fetching circulating and total supply via REST API endpoint. However, the CoinGecko team will always prioritize deriving total and circulating supply via supply disclosures from the team and fetching circulating/token supply via on chain sources.
Requirements:
- Simple REST API endpoint with decimals included.
- Must be an HTTPS endpoint (HTTP endpoints are not accepted).
- Endpoint should be publicly accessible without any form of authentication (password/API keys)
- Should not require api key (publicly accessible)
- Adequate rate limits to support polling once every 30 minutes
- Should be in JSON format.
Example endpoint: https://api.coingecko.com/api/v3/supply/eth
Note:
If your API endpoints are protected by CloudFlare, our requests may be flagged as automated, preventing us from retrieving supply data.
If your API endpoints are protected by CloudFlare, our requests may be flagged as automated, preventing us from retrieving supply data.
When we send requests to your API, we include the following headers:
{
"X-Requested-With" => "com.coingecko",
"User-Agent" => "CoinGecko +https://coingecko.com/"
}
To ensure smooth data retrieval, please configure your CloudFlare Web Application Firewall (WAF) to allow these requests.