improved
Included new fields
June 10th, 2019
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"
},
{...},
{...},
]
},