Get OI OHLC History
Get Open Interest OHLC (candlestick) history data for a specific exchange and trading pair. Returns open, high, low, close values for open interest over time intervals. Supports 1m to 1w intervals. Ideal for: open interest trend analysis, OI divergence detection, futures market analysis, trading signals.
Catalog action Blockchain Data
Get Open Interest OHLC (candlestick) history data for a specific exchange and trading pair. Returns open, high, low, close values for open interest over time intervals. Supports 1m to 1w intervals. Ideal for: open interest trend analysis, OI divergence detection, futures market analysis, trading signals.
At a Glance
| Field | Value |
|---|---|
| Action ID | coinglass-get-oi-ohlc-history |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | coinglass, open-interest, ohlc, futures, derivatives, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
exchange | string | Yes | Futures exchange name (e.g., 'Binance', 'OKX', 'Bybit'). Use the supported-exchange-pair API to get valid exchanges. |
symbol | string | Yes | Trading pair symbol (e.g., 'BTCUSDT', 'ETHUSDT'). Check supported pairs via the supported-exchange-pair API. |
interval | string | Yes | Data aggregation time interval. Supported values: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 1w. |
limit | number | No | Maximum number of results to return (default: 1000, max: 4500). |
startTime | number | No | Start timestamp in seconds (e.g., 1641522717). |
endTime | number | No | End timestamp in seconds (e.g., 1641522717). |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
exchange | string | Yes | Exchange name. |
symbol | string | Yes | Trading pair symbol. |
interval | string | Yes | Time interval. |
candles | array | Yes | Array of OHLC candle data points |
Examples
json{ "type": "coinglass-get-oi-ohlc-history", "payload": { "exchange": "example-exchange", "symbol": "ETH", "interval": "1m" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/coinglass-get-oi-ohlc-history/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "exchange": "example-exchange", "symbol": "ETH", "interval": "1m" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.