Get Coin Aggregated Orderbook History
Get aggregated historical orderbook bid/ask volume data for a coin across all exchanges within a price range. Returns combined ask/bid volumes and USD amounts over time for market-wide liquidity analysis. Ideal for: cross-exchange liquidity analysis, market-wide depth monitoring, aggregate buy/sell pressure detection.
Catalog action Blockchain Data
Get aggregated historical orderbook bid/ask volume data for a coin across all exchanges within a price range. Returns combined ask/bid volumes and USD amounts over time for market-wide liquidity analysis. Ideal for: cross-exchange liquidity analysis, market-wide depth monitoring, aggregate buy/sell pressure detection.
At a Glance
| Field | Value |
|---|---|
| Action ID | coinglass-get-orderbook-coin |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | coinglass, aggregated, liquidity, futures, derivatives, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
symbol | string | Yes | Coin symbol (e.g., 'BTC', 'ETH'). This aggregates orderbook data across all exchanges. |
range | string | Yes | Price range percentage for bid/ask aggregation (e.g., '0.5' for +/-0.5%, '1' for +/-1%, '2' for +/-2%). |
interval | string | Yes | Time interval for data points (e.g., '1h', '4h', '12h', '1d'). |
exchangeList | string | No | Comma-separated exchange names to aggregate (e.g., 'Binance,OKX,Bybit'). Defaults to major exchanges if omitted. |
limit | number | No | Maximum number of results to return (default: 1000). |
startTime | number | No | Start timestamp in milliseconds (e.g., 1641522717000). |
endTime | number | No | End timestamp in milliseconds (e.g., 1641522717000). |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
symbol | string | Yes | Coin symbol. |
range | string | Yes | Price range percentage used for aggregation. |
entries | array | Yes | Array of aggregated orderbook bid/ask history entries across all exchanges |
Examples
json{ "type": "coinglass-get-orderbook-coin", "payload": { "symbol": "ETH", "range": "example-range", "interval": "example-interval" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/coinglass-get-orderbook-coin/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "symbol": "ETH", "range": "example-range", "interval": "example-interval" }}'
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.