We have made updates to the include_tickers parameter for /derivatives/exchanges/{id} endpoint.

Please refer to the documentation for a comprehensive list of available values for this parameter

We have introduced finance and derivatives endpoints to our API.

Feel free to explore these new features, and your feedback and suggestions are highly encouraged.

We have added a new endpoint, /exchanges/{id}/volume_chart.

This endpoint is designed to provide volume chart data related to the specified exchange, with the information presented in BTC.

Example of responses:

[
  [
    1707030000000,
    "141206.9308600928467152" 👈 value in BTC
  ],
  [
    1707030600000,
    "141639.1493761186305005" 👈 value in BTC
  ],
  ......
 ]

We've implemented an enhancement to the /coins/{id}/tickers and /exchanges/{id}/tickers endpoints.

Now, users have the flexibility to use the optional order parameter, which defaults to trust_score_desc.

This addition allows users to customize the sorting order of tickers based on trust score, providing a more tailored experience for data retrieval.

We have added trust_score field to /coins/{id}/tickers and /exchanges/{id}/tickers endpoints

Example of responses:

/coins/{id}/tickers endpoint

{
  "name": "Bitcoin",
  "tickers": [
    {
      "base": "BTC",
      "target": "USDT",
      ......
      "trust_score": "green", 👈
      ........
      "coin_id": "bitcoin",
      "target_coin_id": "tether"
    },
    ...
  ]
},

/exchanges/{id}/tickers endpoint

{
  "name": "Binance",
  "tickers": [
    {
      "base": "USDC",
      ......
      "trust_score": "green", 👈
      ......
      "coin_id": "usd-coin",
      "target_coin_id": "tether"
		},
    {...},
    {...},
  ]
  
},

We have introduced two new fields, last_traded_at and last_fetched_at, to the ticker data.

The existing timestamp field, which currently reflects the last_traded_at value, will be retained for compatibility.

However, please be advised that the timestamp field may be deprecated in the future.

We recommend updating your application to make use of the newly added last_traded_at and last_fetched_at fields for improved accuracy and compatibility.

Example of responses:

/coins/{id}/tickers endpoint

{
  "name": "Bitcoin",
  "tickers": [
    {
      "base": "BTC",
      "target": "USDT",
      ......
      "last_traded_at": "2024-02-05T04:36:55+00:00", 👈
      "last_fetch_at": "2024-02-05T04:36:55+00:00",  👈
      ......
      "coin_id": "bitcoin",
      "target_coin_id": "tether"
    },
    ...
  ]
},

/exchanges/{id}/tickers endpoint

{
  "name": "Binance",
  "tickers": [
    {
      "base": "USDC",
      ......
      "last_traded_at": "2024-02-05T04:49:34+00:00", 👈
      "last_fetch_at": "2024-02-05T04:49:34+00:00",  👈
      ......
      "coin_id": "usd-coin",
      "target_coin_id": "tether"
		},
    {...},
    {...},
  ]
  
},

Added coin_ids optional params to /exchanges/{id}/tickers endpoint. Users can specify the coin_ids to get the exchanges tickers for a particular coin.

Added exchange_ids optional params to /coins/{id}/tickers endpoint. Users can specify the exchange_ids to get the coin tickers on a particular exchange.

We have introduced a new endpoint: /exchanges/list.

This addition expands the functionality of our API, allowing users to retrieve a list of available exchanges on CoinGecko with id and name easily.

To minimize bandwidth usage, the /coins/markets endpoint will now automatically default to retrieving data for the top 100 coins by market cap when the 'ids' parameter is left blank.

This implies that the Order parameters will automatically default to market_cap_desc, ensuring a descending order based on market cap. The Per_Page parameters will default to 100, optimizing the response by providing data for the 100 results of coins per page if no coin's ids are mentioned.

This enhancement aims to streamline the user experience while conserving bandwidth resources.

Recognizing the limitations of the paginated /coins feature, particularly its inability to query for specific coins, we have temporarily hidden it from the documentation to prevent confusion for new users.

Rest assured, there are no plans to remove or deprecate it in the near future.

Instead, we encourage you to transition to the more versatile /coins/list and coins/{id} options for a more tailored and efficient experience.