XRP Market Data
This namespace contains endpoints to retrieve metrics related to XRP Market Data.
This endpoint returns metrics related to XRP's Price. Price OHLCV data consists of five metrics. open, the opening price at the beginning of the window, close, USD closing price at the end of the window, high, the highest USD price in a given window, low, the lowest USD price in a given window, and volume, the total token volume traded in 24h.
Supported Exchanges By Market
Spot
spot
All Exchange*, Binance, Binance US, Bitfinex, Kucoin, Coinbase Advanced, Kraken, HTX Global
Perpetual
perpetual
All Exchange*, Binance, Deribit, Bitmex, OKX
(*) Default exchange
Supported Pairs By Exchange
◦ Spot
All Exchanges
all_exchange
xrp_usd*
Binance
binance
xrp_usdt*
xrp_fdusd
xrp_btc
xrp_eth
xrp_bnb
xrp_rub
xrp_tusd
Binance US
binance_us
xrp_usdt*
Coinbase Advanced
coinbase_advanced
xrp_eur
xrp_usdt
xrp_usd*
Bitfinex
bitfinex
xrp_usdt
xrp_btc
xrp_usd*
HTX Global
htx_global
xrp_usdt*
Kucoin
kucoin
xrp_usdc
xrp_tusd
xrp_btc
xrp_eth
xrp_usdt*
Kraken
kraken
xrp_usdt
xrp_eur
xrp_aud
xrp_eth
xrp_btc
xrp_usd*
◦ Perpetual
All Exchanges
all_exchange
xrp_usd*
xrp_usdt
Binance
binance
xrp_usd*
Deribit
deribit
xrp_usdc*
Okx
okx
xrp_usdt*
Bitmex
bitmex
xrp_usdt
xrp_usd*
Supported Windows By Market
Spot
min, hour, day*
Perpetual
min, hour, day*
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
A market type from the table that we support. See here
spotExample: spotA exchange from the table that we support. See here.
all_exchangeExample: binanceCurrently we support day, hour, and min.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonPrice OHLCV Data
curl "https://api.cryptoquant.com/v1/xrp/market-data/price-ohlcv?window=day&from=20191001&limit=2"Price OHLCV Data
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"open": null,
"high": null,
"low": null,
"close": null,
"volume": null
},
{
"date": "2019-10-01",
"open": null,
"high": null,
"low": null,
"close": null,
"volume": null
}
]
}
}This endpoint returns XRP Perpetual Open Interest from derivative exchanges.
All Exchanges
all_exchange
all_symbol*
Binance
binance
xrp_usdt
xrp_usd
all_symbol*
Bybit
bybit
xrp_usdt
xrp_usd
all_symbol*
Bitmex
bitmex
xrp_usd*
HTX Global
htx_global
xrp_usdt*
Kraken
kraken
xrp_usd*
OKX
okx
xrp_usdt
xrp_usd
all_symbol*
Bitfinex
bitfinex
xrp_usdt*
Supported exchanges for Open Interest are available in Discovery section. Note we unify the unit of return value to USD for each exchange where its contract specification may vary.
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
A pair symbol (ticker) from the table that we support. See here
all_symbolExample: xrp_usdtCurrently we support day, hour, and min.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonOpen Interest in USD
curl "https://api.cryptoquant.com/v1/xrp/market-data/open-interest?window=day&from=20191001&exchange=bitmex"Open Interest in USD
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"open_interest": null
},
{
"date": "2019-10-01",
"open_interest": null
}
]
}
}Funding rates represents traders' sentiments of which position they bet on in perpetual swaps market. Positive funding rates implies that many traders are bullish and long traders pay funding to short traders. Negative funding rates implies many traders are bearish and short traders pay funding to long traders.
All Exchanges
all_exchange
all_symbol*
Binance
binance
xrp_usdt
xrp_usd
all_symbol*
Bybit
bybit
xrp_usdt
xrp_usd
all_symbol*
Bitmex
bitmex
xrp_usd*
HTX Global
htx_global
xrp_usd*
OKX
okx
xrp_usdt
xrp_usd
all_symbol*
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
A pair symbol (ticker) from the table that we support. See here
all_symbolExample: xrp_usdtCurrently we support day, hour, and min.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonFunding Rates in percentage
curl "https://api.cryptoquant.com/v1/xrp/market-data/funding-rates?window=day&from=20191001&exchange=bitmex"Funding Rates in percentage
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"funding_rates": null
},
{
"date": "2019-10-01",
"funding_rates": null
}
]
}
}Taker Buy/Sell Stats represent takers' sentiment of which position they are taking in the market. This metric is calculated with perpetual swap trades in each exchange. taker_buy_volume is volume that takers buy. taker_sell_volume is volume that takers sell. taker_total_volume is the sum of taker_buy_volume and taker_sell_volume. taker_buy_ratio is the ratio of taker_buy_volume divided by taker_total_volume. taker_sell_ratio is the ratio of taker_sell_volume divided by taker_total_volume. taker_buy_sell_ratio is the ratio of taker_buy_volume divided by taker_sell_volume. Note we unify the unit of return value to USD for each exchange where its contract specification may vary.
All Exchanges
all_exchange
all_symbol*
Binance
binance
xrp_usdt*
Bybit
bybit
xrp_usd*
Bitmex
bitmex
xrp_usd*
HTX Global
htx_global
xrp_usd*
OKX
okx
xrp_usd*
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
Currently we support day, hour, and min.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonTaker Buy, Sell volume and ratio
curl "https://api.cryptoquant.com/v1/xrp/market-data/taker-buy-sell-stats?window=day&from=20191001&exchange=bitmex"Taker Buy, Sell volume and ratio
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"taker_buy_volume": null,
"taker_sell_volume": null,
"taker_buy_ratio": null,
"taker_sell_ratio": null,
"taker_buy_sell_ratio": null
},
{
"date": "2019-10-01",
"taker_buy_volume": null,
"taker_sell_volume": null,
"taker_buy_ratio": null,
"taker_sell_ratio": null,
"taker_buy_sell_ratio": null
}
]
}
}Liquidations are sum of forced market orders to exit leveraged positions caused by price volatility. Liquidations indicate current price volatility and traders' sentiment which side they had been betting. Note that Binance's liquidation data collection policy has changed since 2021-04-27, which makes the distribution of the data has changed after that.
All Exchanges
all_exchange
all_symbol*
Binance
binance
xrp_usdt
xrp_usd
all_symbol*
Bybit
bybit
xrp_usdt
xrp_usd
all_symbol*
Bitmex
bitmex
xrp_usd*
HTX Global
htx_global
xrp_usdt*
OKX
okx
xrp_usdt
xrp_usd
all_symbol*
Bitfinex
bitfinex
xrp_usdt*
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
A XRP pair symbol from the table that we support. See here
all_symbolExample: xrp_usdCurrently we support day, hour, and min.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonAmount of long/short liquidations orders
curl "https://api.cryptoquant.com/v1/xrp/market-data/liquidations?window=day&from=20191001&exchange=binance"Amount of long/short liquidations orders
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"long_liquidations": null,
"short_liquidations": null,
"long_liquidations_usd": null,
"short_liquidations_usd": null
},
{
"date": "2019-10-01",
"long_liquidations": null,
"short_liquidations": null,
"long_liquidations_usd": null,
"short_liquidations_usd": null
}
]
}
}This endpoint returns metrics related to market capitalization. First, we provide market_cap, which is total market capitalization of XRP, calculated by multiplying the total supply with its USD price. Go to Data Guide‣
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
Currently, we support day and hour.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonmarket_cap, realized_cap, average_cap, delta_cap, thermo_cap
curl "https://api.cryptoquant.com/v1/xrp/market-data/capitalization?window=day&from=20191001&limit=2"market_cap, realized_cap, average_cap, delta_cap, thermo_cap
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"market_cap": null
},
{
"date": "2019-10-01",
"market_cap": null
}
]
}
}Estimated Leverage Ratio indicates how much leverage is used by users on average. It is defined as the ratio of open interest divided by the reserve of an exchange. This information measures traders' sentiment whether they take a high risk or low risk. Go to User Guide‣
Note: This endpoint does not support Point-In-Time (PIT) accuracy due to periodic updates to wallet address clustering. Historical data may change as new exchange wallets are discovered, added, and validated.
For each API request, include this HTTP header:
Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.
Currently, we support day, hour, and 10min.
dayExample: dayThis defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.
20191001T100000This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.
20191001T103025The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.
100Example: 100A format type about return message type. Supported formats are json, csv.
jsonExample: jsonestimated levereage ratio
curl "https://api.cryptoquant.com/v1/xrp/market-data/estimated-leverage-ratio?exchange=binance&window=day&from=20191001&limit=2"estimated levereage ratio
{
"status": {
"code": 200,
"message": "success"
},
"result": {
"window": "day",
"data": [
{
"date": "2019-10-02",
"estimated_leverage_ratio": null
},
{
"date": "2019-10-01",
"estimated_leverage_ratio": null
}
]
}
}Last updated
Was this helpful?