Added interval hourly params to /coins/id/ohlc
We've expanded functionality to include support for the interval=hourly parameter within the /coins//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
Added support for inactive coins in /coins/list and historical data endpoints
🗓️ April 30, 2024
We've now enhanced the /coins/list endpoint to include inactive coins
- You may access the inactive coins by specifying
status=inactivein 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
- Example of endpoint request:
Additionally, historical data for inactive coins can be queried using their IDs in the following endpoints:
Please note that these features are available exclusively for paid plan subscribers only
Introduced /key endpoint
🗓️ March 27, 2024
We've introduced a new endpoint /key for conveniently monitoring your account's API usage, including rate limits and remaining credits.
Example of responses:
Multiple Improvements (Onchain/GT)
🗓️ February 28, 2024
- image_url is now returned in the token response for pools and tokens endpoints:
Example of responses:
- We've added sorting parameters such as order=
h24_volume_usd_descand order=h24_tx_count_descfor /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:
- The 'token' parameter within the /ohlcv endpoint can now accept a token address, provided it exists in the queried pool, to return OHLCV data