> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Funding Rate History

Retrieves historical funding rate OHLC data for a specific exchange and trading pair. Returns open, high, low, close funding rates for each interval. Supports multiple time intervals and date ranges. Ideal for: funding rate trend analysis, backtesting strategies, identifying funding rate patterns.

![Get Funding Rate History logo](https://ai-icon.b3.fun/logo/coinglass)
Catalog action Blockchain Data

Retrieves historical funding rate OHLC data for a specific exchange and trading pair. Returns open, high, low, close funding rates for each interval. Supports multiple time intervals and date ranges. Ideal for: funding rate trend analysis, backtesting strategies, identifying funding rate patterns.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `coinglass-get-funding-rate-history` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `coinglass`, `futures`, `derivatives`, `perpetual`, `ohlc`, `history`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `exchange` | `string` | Yes | Futures exchange name \(e.g., Binance, OKX, Bybit, dYdX\). |
| `symbol` | `string` | Yes | Trading pair symbol \(e.g., BTCUSDT, ETHUSDT\). |
| `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 |
| --- | --- | --- | --- |
| `exchange` | `string` | Yes | Exchange name. |
| `symbol` | `string` | Yes | Trading pair symbol. |
| `interval` | `string` | Yes | Time interval. |
| `candles` | `array` | Yes | Array of funding rate OHLC candles. |

## Examples

**Workflow node**

```json
{
  "type": "coinglass-get-funding-rate-history",
  "payload": {
    "exchange": "example-exchange",
    "symbol": "ETH",
    "interval": "1m"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/coinglass-get-funding-rate-history/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "exchange": "example-exchange",
    "symbol": "ETH",
    "interval": "1m"
  }
}'
```

**Use expressions for dynamic values**

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.