Get Funding Rate OI Weight
Retrieves open interest-weighted funding rate OHLC data aggregated across all exchanges. Weights funding rates by each exchange's open interest for more accurate market representation. Ideal for: market-wide funding sentiment analysis, OI-adjusted funding strategies, cross-exchange comparisons.
Catalog action Blockchain Data
Retrieves open interest-weighted funding rate OHLC data aggregated across all exchanges. Weights funding rates by each exchange's open interest for more accurate market representation. Ideal for: market-wide funding sentiment analysis, OI-adjusted funding strategies, cross-exchange comparisons.
At a Glance
| Field | Value |
|---|---|
| Action ID | coinglass-get-funding-rate-oi-weight |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | coinglass, open-interest, futures, derivatives, perpetual, ohlc, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
symbol | string | Yes | Coin symbol (e.g., BTC, ETH). |
interval | string | Yes | Time interval for OHLC data. |
limit | number | No | Maximum number of results (default: 1000, max: 4500). |
startTime | number | No | Start timestamp in seconds. |
endTime | number | No | End timestamp in seconds. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
symbol | string | Yes | Coin symbol. |
interval | string | Yes | Time interval. |
candles | array | Yes | Array of OI-weighted funding rate OHLC candles. |
Examples
json{ "type": "coinglass-get-funding-rate-oi-weight", "payload": { "symbol": "ETH", "interval": "1m" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/coinglass-get-funding-rate-oi-weight/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "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.