Skip to main content
GET
/
multi
/
gex
/
levels
GEX levels across multiple symbols (bundled)
curl --request GET \
  --url https://api.example.com/multi/gex/levels \
  --header 'X-API-Key: <api-key>'
{
  "data": {
    "results": {},
    "requested": [
      "<string>"
    ],
    "served": [
      "<string>"
    ],
    "missing": [
      "<string>"
    ],
    "invalid": [
      "<string>"
    ]
  },
  "meta": {
    "version": "<string>",
    "timestamp": "<string>",
    "request_id": "<string>",
    "symbol": "<string>",
    "spot_price": 123,
    "computed_at": "<string>",
    "freshness_seconds": 123,
    "source": [
      "<string>"
    ],
    "exchanges_filtered": [
      "<string>"
    ],
    "rate_limit": {},
    "extra": {}
  },
  "success": true
}

Documentation Index

Fetch the complete documentation index at: https://docs.backquant.com/llms.txt

Use this file to discover all available pages before exploring further.

Bundled multi-symbol read. Up to 8 symbols per request. Returns per-symbol entries + a served / missing / invalid breakdown.

​
See also

Multi-symbol bundling

What is GEX?

Authorizations

​
X-API-Key
string
header
required

Your BackQuant API key (same key as v1)

Headers

​
X-API-Key
string | null

Query Parameters

​
symbols
string
required

Comma-separated symbols, e.g. BTCUSDT,ETHUSDT,SOLUSDT,HYPEUSDT.

Example:
{
  "all-four": {
    "value": "BTCUSDT,ETHUSDT,SOLUSDT,HYPEUSDT"
  }
}
​
exchanges
string | null

Comma-separated venue filter

​
include
string | null

Optional sections: expected_move,max_pain,ranked,zones

Response

Successful Response

​
data
MultiGexLevelsData · object
required
​
meta
V2Meta · object
required

The meta block returned alongside every v2 response.

Every field after version/timestamp is optional because endpoints attach different combinations — e.g. /v2/status skips symbol, the chain endpoint sets extra.filter_hash, etc. Listing them here means SDKs get a typed accessor for each instead of a generic meta: dict.

​
success
boolean
default:true