Menu

Live GEX vs Settled GEX: Why Your Options API Returns Two Different Numbers for the Same Symbol
πŸ–ΌοΈ

Live GEX vs Settled GEX: Why Your Options API Returns Two Different Numbers for the Same Symbol

DEV CommunityΒ·tomasz dobrowolskiΒ·5 months ago
#D7FYB3oe
#api#python#finance#flow#settled
Reading 0:00
15s threshold

Here is a bug I see in client code at least once a month:

# DO NOT do this gex_now = api . get ( " /v1/flow/summary/SPY " )[ " live_gex " ] gex_open = api . get ( " /v1/exposure/gex/SPY " )[ " net_gex " ] intraday_move = gex_now - gex_open # ❌ meaningless

Enter fullscreen mode

Exit fullscreen mode

net_gex and live_gex look interchangeable. They are not. They come from two different surfaces of the API, computed against two different open interest numbers, answering two different questions. Subtracting one from the other gives you a quantity that means nothing β€” not "intraday gamma move", not "change since open", just noise. This post is the canonical explainer of where each number comes from and how to keep them apart.

Two questions, two numbers

Dealer-positioning analytics has exactly one input that matters: how many contracts are open at each strike, and on which side dealers sit.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.