Exposure Sheet vs Separate GEX/DEX/VEX/CHEX Calls: When to Use the Combined Endpoint

You can read dealer gamma, delta, vanna, and charm one endpoint at a time, or pull them together from /v1/exposure/sheet/SPY in a single request. The math behind each greek is identical either way - the question is how many calls you make, who aligns the strikes, and which extra fields you need. Here is the decision.

The Rule of Thumb

If you only remember one sentence: reading two or more greeks means one sheet call, not two-to-four separate calls.

One Call vs Four

The per-greek endpoints each return their own per-strike array. To assemble a combined view you would call all four, then join them on strike yourself - and handle the case where a strike appears in one array but not another. The sheet does that join server-side and returns one row per strike with every greek already populated.

The tradeoff is tier: the sheet is Growth and above, while GEX on its own starts on the Free tier. If your whole product reads a single greek, the per-greek endpoint is cheaper to reach. The moment you read two, the sheet is fewer requests and less client code.

What the Sheet Adds

Beyond aligning the four greeks, the sheet returns three things the per-greek endpoints do not:

• DAG (delta-adjusted gamma) - a delta-weighted gamma column returned per strike (dag) and as a chain total (net_dag), surfaced alongside the four greeks so you can read gamma in delta-adjusted terms without computing it yourself.
• Gamma peaks - the peaks array surfaces the wall strikes directly, each with its net_gex, a normalized strength, and a side of call_wall or put_wall, so you do not scan the whole rowset to find them.
• Line-in-the-Sand strike (LIS) - the lis object flags a single inflection strike with its magnitude: the level the sheet identifies as the key pivot in the exposure profile.

The response also carries chain totals (net_gex, net_dex, net_dag, and the rest) and, when you pass ?expiration=, OPEX / triple-witching flags. If you were calling four endpoints and then computing walls and a delta-adjusted-gamma column yourself, the sheet replaces both the calls and that post-processing.

In Code

The four per-greek endpoints are first-class methods on the official SDKs (pip install flashalpha); the combined sheet is one REST call. The contrast in Python:

from flashalpha import FlashAlpha
import requests

fa = FlashAlpha("YOUR_API_KEY")

# The long way: four SDK calls, then align the four arrays on strike yourself
gex  = fa.gex("SPY")
dex  = fa.dex("SPY")
vex  = fa.vex("SPY")
chex = fa.chex("SPY")
# ...you still have to join gex/dex/vex/chex per strike in your own code...

# The combined way: one request, every greek already aligned per strike,
# plus totals, net_dag, the Line-in-the-Sand strike, and the gamma peaks
sheet = requests.get(
    "https://lab.flashalpha.com/v1/exposure/sheet/SPY",
    headers={"X-Api-Key": "YOUR_API_KEY"},
).json()

print(sheet["totals"]["net_gex"], sheet["lis"]["strike"])
for wall in sheet["peaks"]:
    print(wall["side"], wall["strike"], wall["strength"])

SDKs are available for Python, JavaScript, C#, Go, and Java; the per-greek methods (gex, dex, vex, chex) exist in each. See the Python SDK reference for the full method list.

When the Separate Endpoints Win

The combined sheet is not always the right call. Reach for a single per-greet endpoint when:

• One greek drives your logic. A gamma-flip alert only needs /v1/exposure/gex (or /v1/exposure/levels); pulling vanna and charm you never read is wasted payload.
• You are on the Free or Basic tier. GEX is Free+, the other three are Basic+, and the sheet is Growth+. If you have not upgraded to Growth, the per-greek endpoints are how you reach this data.
• You want the lightest possible response. A single per-strike array is smaller over the wire than the full four-greek sheet, which matters for high-frequency polling of one metric.

Frequently Asked Questions

Related Reading

• Exposure Sheet API reference - parameters, response fields, and examples
• GEX/DEX/VEX/CHEX: an 8-year backtest vs VIX - what the four greeks add over GEX alone
• Why GEX isn't enough: vanna and charm - the case for reading all four exposures together
• Interactive API Playground