As part of our commitment to improving data quality and enhancing the consistency of asset information, we are rolling out an asset standardization initiative at CoinGecko.

What is asset standardization?
Standardization involves refining how we classify and display assets. By systematically organizing asset listings into more precise categories - such as native, bridged, or wrapped tokens each following specific naming conventions, we aim to eliminate confusion and enhance data reliability.

What changes should I expect?
The most notable change is that non-native token contracts previously grouped under native asset listings will now be assigned their own distinct pages.

For example, a bridged version of USDT that might have been aggregated under the original, native USDT page, will now be featured on a dedicated page specifically for that bridged variant.

Additionally, there may be varying levels of changes in various aggregated data points of the standardized assets, including trading volume, supply, market cap rankings, etc., due to misplaced contracts being transitioned away from the original page to accurately reflect their true metrics.

Focus for Q3 2024
Our efforts this quarter will concentrate on three major assets:

• Wrapped Bitcoin (WBTC)
• Wrapped Ethereum (WETH)
• Dai (DAI)

For full list of FAQs, please refer [here](https://support.coingecko.com/hc/en-us/articles/35555248857497-CoinGecko-Asset-Issuance-Standardisation-Initiative-Updates-and-FAQ)

How does this affect my current API setup?
The following CoinGecko API endpoints will be impacted, with full details tracked in this spreadsheet. We encourage you to make the necessary adjustments and enable edit notifications on the Google Sheets, to receive real-time updates when non-native token contracts have been successfully standardized.

NOTE: No changes are necessary if you do not need data for non-native token contracts that will be separated away from the native tokens. For a finalised list of token contracts and API IDs that have been separated from its native asset page and listed individually, please refer to this spreadsheet.

Simple

• /simple/price
• /simple/token_price/{id}

Coins

• /coins/markets
• /coins/{id}
• /coins/{id}/tickers
• /coins/{id}/history
• /coins/{id}/market_chart
• /coins/{id}/market_chart/range
• /coins/{id}/ohlc
• /coins/{id}/ohlc/range
• /coins/{id}/circulating_supply_chart
• /coins/{id}/circulating_supply_chart/range
• /coins/{id}/total_supply_chart
• /coins/{id}/total_supply_chart/range

Contract

• /coins/{id}/contract/{contract_address}
• /coins/{id}/contract/{contract_address}/market_chart
• /coins/{id}/contract/{contract_address}/market_chart/range

Exchange

• /exchanges/{id}/tickers
• /exchanges/{id}/volume_chart
• /exchanges/{id}/volume_chart/range

We've introduced a new endpoint /coins/{id}/ohlc/range.

This endpoint allows you to get the OHLC chart (Open, High, Low, Close) of a coin within a range of timestamp based on particular coin id.

Please note that this endpoint is available exclusively for paid plan subscribers only.

We've expanded functionality to include support for the interval=hourly parameter within the /coins/{id}/ohlc endpoint.

Users can use this parameter to retrieve OHLC (Open/High/Low/Close) data on a hourly interval for up to 90 days of the date range.

Example of endpoint request:

https://pro-api.coingecko.com/api/v3/coins/bitcoin/ohlc?vs_currency=usd&days=1&interval=hourly&x_cg_pro_api_key=YOUR_API_KEY

We've now enhanced the /coins/list endpoint to include inactive coins

• You may access the inactive coins by specifying status=inactive in your query
• Example of endpoint request:
  https://pro-api.coingecko.com/api/v3/coins/list?include_platform=false&status=inactive&x_cg_pro_api_key=YOUR_API_KEY

Additionally, historical data for inactive coins can be queried using their IDs in the following endpoints:

• /coins/{id}/history
• /coins/{id}/market_chart
• /coins/{id}/market_chart/range
• /coins/{id}/contract/{contract_address}/market_chart
• /coins/{id}/contract/{contract_address}/market_chart/range

Please note that these features are available exclusively for paid plan subscribers only

We've introduced a new endpoint /key for conveniently monitoring your account's API usage, including rate limits and remaining credits.

Example of responses:

{
  "plan": "Other",
  "rate_limit_request_per_minute": 1000,
  "monthly_call_credit": 1000000,
  "current_total_monthly_calls": 307,
  "current_remaining_monthly_calls": 999693
}

• image_url is now returned in the token response for pools and tokens endpoints:

  Example of responses:

  JSON

   "data": {
      "id": "eth_0xdac17f958d2ee523a2206206994597c13d831ec7",
      "type": "token",
      "attributes": {
        "address": "0xdac17f958d2ee523a2206206994597c13d831ec7",
        "name": "Tether USD",
        "symbol": "USDT",
        "image_url": "https://assets.coingecko.com/coins/images/325/small/Tether.png?1696501661", 👈
        ......
        "market_cap_usd": "100719721661.467"
      },
      "relationships": {}
  }
  

• We've added sorting parameters such as order= h24_volume_usd_desc and order= h24_tx_count_desc for /pools endpoints

• The 'token' parameter within the /ohlcv endpoint can now accept a token address, provided it exists in the queried pool, to return OHLCV data
  Example of endpoint request (token=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2):
  https://pro-api.coingecko.com/api/v3/onchain/networks/eth/pools/0x06da0fd433c1a5d7a4faa01111c044910a184553/ohlcv/day?token=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2&x_cg_pro_api_key=YOUR_API_KEY

• /ohlcv endpoint now includes the base and target token metadata in the response
  Example of responses:

  JSON

  {
    "data": {
      "id": "46303eb4-fba1-44f3-a3c8-c542e4cd5d1a",
      "type": "ohlcv_request_response",
      "attributes": {
        "ohlcv_list": []
      }
    },
    "meta": {
      "base": {
        "address": "0xdac17f958d2ee523a2206206994597c13d831ec7",
        "name": "Tether USD",
        "symbol": "USDT",
        "coingecko_coin_id": "tether"
      },
      "quote": {
        "address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
        "name": "Wrapped Ether",
        "symbol": "WETH",
        "coingecko_coin_id": "weth"
      }
    }
  }
  

Trending Pools endpoint, /networks/{network}/trending_pools is now available to fetch a list of pools that are trending as seen on GeckoTerminal based on web visits and on-chain activities.

Added new endpoint to search for pools /search/pools based on keywords passed into query.

We've included a new field "whitepaper" under "links" section for /coins/{id} endpoint

Example of responses:

{
  "id": "bitcoin",
  ......
  "links": {
    "homepage": [],
    "whitepaper": "https://bitcoin.org/bitcoin.pdf", 👈
    "blockchain_site": [],
    "official_forum_url": [],
    "chat_url": [],
    "announcement_url": [],
    "twitter_screen_name": "bitcoin",
    "facebook_username": "bitcoins",
    "bitcointalk_thread_identifier": null,
    "telegram_channel_identifier": "",
    "subreddit_url": "https://www.reddit.com/r/Bitcoin/",
    "repos_url": {}
  },
  .......
}

The following data is now deprecated for /coins/{id} endpoint:

• coingecko_rank
• coingecko_score
• developer_score
• community_score
• liquidity_score
• public_interest_score
• public_interest_stats
• alexa_rank
• bing_matches