Instruments and status
1Instruments and status
Which instruments exist and in which data types — the /v1/instruments registry; whether sources are healthy — /v1/status.
Rate-limit group — instruments. Start with the registry: it shows what an instrument is called and which routes have data for it.
Instrument registry
/v1/instrumentsAll instruments from all sources under one canonical name. The sources column shows where it exists: candles, footprint, densities, screener.
| Parameter | Meaning |
|---|---|
venue |
exchange: binance, okx, … |
market |
spot or perp. Dated futures and options are not available yet |
source |
only instruments with data of this type: candles, footprint, densities, screener |
q |
case-insensitive symbol substring: q=btc |
limit |
rows per page, 1–10 000, default 1000 |
cursor |
cursor from next_cursor |
curl -s "https://market-api.lootx.trade/v1/instruments?venue=binance&market=perp&q=BTC" \
-H "Authorization: Bearer $LOOTX_API_KEY"{
"columns": ["instrument", "venue", "market", "symbol", "sources"],
"rows": [
["binance:perp:BTCUSDT", "binance", "perp", "BTCUSDT", ["candles", "footprint", "densities", "screener"]],
["binance:perp:BTCUSDC", "binance", "perp", "BTCUSDC", ["candles", "footprint", "densities"]]
],
"next_cursor": null,
"updated_at": 1793750400000
}updated_at — the last time the gateway received the list from at least one source; 0 means never. The registry refreshes every 5 minutes and shows what the sources are currently collecting, not all exchange listings. A new pair appears once a source starts collecting it; for some sources this happens after a daily turnover threshold.
Source status
/v1/statusWhether the data sources behind the gateway are responding and with what latency. Useful for your own monitoring: if ok: false, 502/504 errors on routes for that source are expected.
{
"ok": true,
"ts": 1793750400000,
"upstreams": [
{ "name": "data", "ok": true, "latency_ms": 12, "http_status": 200 },
{ "name": "clusters", "ok": true, "latency_ms": 18, "http_status": 200 }
]
}/v1/status has no table, so no CSV — only JSON and protobuf. The route is not in any rate-limit group and only consumes general limits.
https://docs.lootx.trade/en/market-api/instruments