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

This endpoint allows you to retrieve Open, High, Low, and Close (OHLC) data for a specific coin.

We've introduced three new fields atl, atl_change_percentage, and atl_date to the responses of /coins/markets endpoint.

These additions provide valuable data on the all-time low (atl) price, percentage change since the all-time low, and the date of the all-time low for improved analysis and insights.

Example of responses:

[
  {
  "id": "bitcoin",
  "symbol": "btc",
  
  "ath": 69045,
  "ath_change_percentage": -38.01241,
  "ath_date": "2021-11-10T14:24:11.849Z",
  "atl": 67.81, 👈
  "atl_change_percentage": 63017.26399, 👈
  "atl_date": "2013-07-06T00:00:00.000Z", 👈
  "roi": null,
  "last_updated": "2024-02-05T07:23:50.583Z"
	},
  ......
]

Starting from April 14th, 2020, there's a crucial update to the /coins/{id}/tickers API endpoint. Previously, the converted_last value represented the converted price per coin in USD. Now, it will accurately reflect the market price of the base currency itself.

For example, if querying coins/tether/tickers, and there's a BTC/USDT ticker pair, the old converted_last might show 6491.51 USD. After the update, it will return 1, representing the actual market price of Tether.

If you utilize converted_last for calculations, be aware of potential breaking changes and take necessary actions. If it's solely for display, no action is required, as this update ensures a more accurate representation of the intended value.

Example of responses:

{
  "name": "Tether",
  "tickers": [
   {
    "base": "BTC",
    "target": "USDT",
    ......
    "converted_last": {
      "btc": 0.00002336, //USDT price in BTC
      "eth": 0.00043493, // USDT price in ETH
      "usd": 0.99901 👈 //showing USDT price instead of Bitcoin Price
    },
    ......
    "coin_id": "bitcoin",
    "target_coin_id": "tether"
    },
    ......
  ]

}
  

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.