Chart data
Time series of one chart, newest first (limit default 100, max 500)
/openapi/v1/analyses/{chart_name}Returns the historical series for one chart. Use GET /analyses to discover valid chart_name values and the series each chart carries.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| chart_name | string | Required | Chart name from GET /analyses. Unknown names return 404 / 400401 |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | Optional | Number of rows. Default 100, maximum 500. Values above the maximum are silently clamped to 500 (no error) |
| start_time | long | Optional | ⚠️ Currently not usable — see Known issues |
| end_time | long | Optional | ⚠️ Currently not usable — see Known issues |
Request Example
curl "https://openapi.sosovalue.com/openapi/v1/analyses/fgi_indicator?limit=30" \ -H "x-soso-api-key: $SOSO_API_KEY"
Response Example
[
{
"timestamp": "1785859200000",
"crypto_fear_&_greed_index": 27
},
{
"timestamp": "1785772800000",
"crypto_fear_&_greed_index": 31
}
]Response Fields
| Field | Type | Description |
|---|---|---|
| timestamp | String | Millisecond epoch, returned as a quoted string (not a JSON number) |
| (series keys) | Number | One key per series declared by the chart. Names vary per chart — see Chart List |
Ordering and defaults
| Behaviour | Value |
|---|---|
| Row order | Newest first (descending by timestamp) |
| Default rows | 100 |
| Maximum rows | 500 (higher values clamped, no error) |
| Granularity | Daily for most charts; binance_btcusdt_futures_long_short_ratio_1h / _4h / _12h follow their own interval |
timestamp is a string — parse it before doing arithmetic:
const ms = Number(row.timestamp);
Series keys may contain characters that are not valid identifiers (&, /, parentheses, full-width parentheses, leading digits). Always access them as string keys:
row["crypto_fear_&_greed_index"] // ✅ row["long/short_ratio"] // ✅ row["24h_vol"] // ✅ row["daily_block_rewards_(btc)"] // ✅
Rows omit null series — always guard key access
A row carries only the series that have a value at that timestamp. Null values are omitted rather than emitted as null, so the key set differs from row to row.
[
{ "timestamp": "1785801600000", "all": 48920485803, "binance": 9450137248, "btc_price": 64106.56 },
{ "timestamp": "1785715200000", "all": 47611038221, "binance": 9302115880 }
]The second row has no btc_price. Measured over 60 rows per chart, 15 of the 30 charts have at least one series that appears in only some rows:
| chart_name | Sparse series (rows present / 60) |
|---|---|
tvl_of_different_type_of_chain | all 50 layer_2 50 others 50 |
total_crypto_hk_btc_etf_fund_flow | 1d_btc_inflow 36 total_btc_in_hk_etf 36 total_net_assets 36 |
total_crypto_hk_eth_etf_fund_flow | 1d_eth_inflow 36 total_eth_in_hk_etf 36 total_net_assets 36 |
bitcoin_futures_volume_open_interest | open_interest 39 volume 39 |
total_crypto_spot_btc_eth_etf_fund_flow_1d | bitcoin_daily_total_net_inflow 40 ethereum_daily_total_net_inflow 40 |
total_crypto_eth_etf_fund_flow | bitcoin_etf 40 ethereum_etf 40 |
btc_transactions | number_of_transactions 59 30_day_average_number_of_transactions 59 |
btc_hashrate, btc_mining_difficulty | btc_price 59 |
btc_active_addresses | number_of_active_addresses 59 |
btc_new_addresses | number_of_new_addresses 59 |
binance_btcusdt_futures_long_short_ratio_1h / _4h / _1d | btc_price 59 |
binance_btcusdt_futures_long_short_ratio_12h | btc_price 58 |
This is expected behaviour, not a defect — but it means an unguarded access will throw on some rows:
// ❌ throws whenever the key is absent rows.map(r => r.btc_price.toFixed(2)); // ✅ rows.map(r => (r.btc_price != null ? Number(r.btc_price).toFixed(2) : null));
When charting, treat an absent key as a gap in the series rather than as zero.
Known issues
Verified against production on 2026-08-05.
The newest row may be incomplete
Series inside one chart can update on different cadences, and rows are ordered newest first. When one series is a day ahead of the others, data[0] carries only that series.
Measured on bitcoin_futures_volume_open_interest over 400 rows:
| series | rows | newest |
|---|---|---|
btc_price | 400 | 2026-08-12 |
open_interest | 276 | 2026-08-11 |
volume | 276 | 2026-08-11 |
So data[0] = {timestamp, btc_price} and data[0].open_interest is absent — reading the "latest value" off row 0 yields nothing even though the series has 276 populated rows.
Do not read a metric off data[0]. Scan forward to the first row that actually contains the key you need:
def latest(rows, key):
return next((r for r in rows if key in r), None)The same shape appears outside the charts API — see ETF Historical Data › The most recent row is not settled yet.
Series declared but never returned
Five charts advertise series in GET /analyses that are absent from every row (checked across 60 rows each):
| chart_name | Declared but never returned | Effect |
|---|---|---|
btc_miner_revenue | daily_block_rewards_(btc) daily_total_fees_(btc) | Both metric series missing — only the btc_price overlay remains, so the chart carries no miner-revenue data |
ahr_999_indicator | fixed_investment_zome buy_at_the_buttom | Threshold bands unavailable; btc_price and ahr999 work. (Both names are also misspelled — "zome"/"buttom".) |
total_crypto_market_cap | 24h_vol | See the next section |
usd_inflows_into_cryptocurrency_markets | fiat_backed_stablecoin_inflows | The other 8 series work |
total_crypto_spot_etf_fund_flow | — (extra key field_2 is returned but not declared) | An undeclared placeholder-named key appears in rows |
Do not treat the fields array from GET /analyses as a guarantee. Read the first page of data and use the keys actually present.
start_time / end_time return an empty array
Passing either parameter — any value, milliseconds or seconds, alone or together — returns HTTP 200 with data: []. This includes ranges that provably cover the entire dataset:
# Returns 100 rows curl -H 'x-soso-api-key: YOUR_KEY' \ 'https://openapi.sosovalue.com/openapi/v1/analyses/fgi_indicator' # Returns 0 rows — the range spans 1970 → 2096 curl -H 'x-soso-api-key: YOUR_KEY' \ 'https://openapi.sosovalue.com/openapi/v1/analyses/fgi_indicator?start_time=0&end_time=4000000000000'
The parameters are parsed — a non-numeric value such as start_time=2026-05-29 returns HTTP 400 — so this is a filtering defect, not an unrecognised parameter. It reproduces on every chart tested.
Workaround: omit both parameters, use limit to size the window, and filter client-side. Rows are ordered newest-first, so limit=N returns the most recent N points.
Impact: an integration written against the parameter documentation receives an empty array together with a success status — a silent failure. Treat both parameters as unavailable until fixed.
total_crypto_market_cap does not return 24h_vol
The chart advertises three series but rows carry only two:
{
"timestamp": "1785686400000",
"total_crypto_market_cap": 2177813849402.85,
"market_cap": 40122576829.22
}24h_vol is absent. Note also that market_cap holds a value two orders of magnitude below total_crypto_market_cap (≈ 40 B vs ≈ 2.18 T) — consistent with a 24-hour volume figure rather than a capitalisation, and comparable to altcoin_volume in altcoin_market_cap_volume. Do not assume market_cap is a capitalisation series until the naming is confirmed.
Errors
| HTTP | code | Cause |
|---|---|---|
| 400 | 400001 | Non-numeric limit / start_time / end_time |
| 404 | 400401 | Unknown chart_name |
{
"code": 400401,
"message": "Resource not found: chart_name=no_such_chart"
}See Error Responses for the full code table.
Examples
# Latest 30 points of the Fear & Greed Index curl -sS -H 'x-soso-api-key: YOUR_KEY' \ 'https://openapi.sosovalue.com/openapi/v1/analyses/fgi_indicator?limit=30' # BTC futures open interest broken down by exchange curl -sS -H 'x-soso-api-key: YOUR_KEY' \ 'https://openapi.sosovalue.com/openapi/v1/analyses/futures_open_interest?limit=7'