Realtime Options Public API v1
Realtime Options Pro includes authenticated, read-only Public API v1 access to four aggregated analytics endpoints: Buy/Sell Pressure, Algo Flow, 0DTE Flow & Gamma Exposure, and Greeks by Strike. Each account has one revocable bearer key and an account-specific per-minute limit. It is not a raw exchange feed, unrestricted option-chain API, execution API or redistribution product.

- Eligibility
- Active Pro subscription
- Endpoints
- Buy/Sell Pressure, Algo Flow, 0DTE Flow & Gamma Exposure, and Greeks by Strike
- Version
- Four GET endpoints under /api/public/v1/market
- Authentication
- One revocable bearer API key per account
- Rate limit
- Account-specific requests per minute
What does Public API v1 provide?
Public API v1 exposes four read-only research integrations. GET /api/public/v1/market/buy-sell-pressure returns aggregated pressure or delta analytics. GET /api/public/v1/market/algo-flow returns aggregated Algo Flow analytics. GET /api/public/v1/market/zero-dte-gex returns short-expiry gamma exposure and premium by strike. GET /api/public/v1/market/greeks-by-strike returns gamma, vanna and charm across the dashboard's selected strikes.
Read the supporting context
The v1 contract is deliberately narrow. Existing response fields and endpoint semantics remain stable unless the versioned documentation says otherwise. The authenticated API Access screen is the authority for the endpoints enabled on an account.
| Included | Not included |
|---|---|
| Aggregated Buy/Sell Pressure analytics | Raw OPRA trades or quotes |
| Aggregated Algo Flow analytics | Unrestricted option-chain data |
| 0DTE Flow & Gamma Exposure by strike | Strict same-day-only feed or guaranteed pin levels |
| Gamma, vanna and charm by selected strike | Unrestricted chain export or confirmed dealer positions |
| Read-only authenticated GET requests | Order placement or broker connectivity |
| Account-specific rate limit | Redistribution or sublicensing rights |
How do the 0DTE GEX and Greeks by Strike APIs match the dashboard?
The two exposure endpoints reuse the dashboard handlers and preserve their data arrays and original metadata. Public v1 adds version, endpoint, normalized parameters and generatedAt. Supply one ticker with 1–8 letters or periods and an optional valid YYYY-MM-DD US Eastern session date. The default ticker is SPY; omitting date selects the latest available session. Unsupported, repeated or malformed filters return INVALID_QUERY.
Read the supporting context
0DTE uses ticker, while Greeks uses symbol. The GEX/Premium, Raw/Scaled and Gamma/Vanna/Charm controls select returned fields locally; they are not query parameters. Empty results use data: [] rather than fabricated exposure. Examples and the complete response field reference are in the authenticated External API section.
| Endpoint | Query parameters | Response | Research use case |
|---|---|---|---|
| GET /api/public/v1/market/zero-dte-gex | ticker=SPY; optional date=YYYY-MM-DD | ||
| GET /api/public/v1/market/greeks-by-strike | symbol=SPY; optional date=YYYY-MM-DD |
What exposure-data limitations should an API client handle?
The 0DTE widget initially uses today/tomorrow expirations and can broaden to nearby dates when no data is found. Its legacy dex field is callValue + putValue in USD, a premium proxy rather than execution-signed delta shares. gammaFlip labels the total GEX sign; it is not a gamma-flip price. Greeks by Strike uses stored or derived Greeks where available and legacy proxies for missing inputs. Exposure is modeled research context, not a verified dealer-position feed or prediction.
Read the supporting context
Open interest retains its daily snapshot cadence. Net Greek exposure and largest positive/negative strikes are calculated over the returned rows, not the entire options chain. Repeated polling cannot make daily OI intraday or guarantee fresh values: generatedAt identifies payload generation, and cached results retain that timestamp.
Who can create an API key?
API access is available to eligible Pro accounts. The authenticated API Access screen shows the account's status, enabled endpoints and per-minute limit. An account can hold one key at a time, and that key can be created, rotated or revoked. Store the secret like any other bearer credential.
Read the supporting context
All four endpoints share one account-specific quota (default 20 requests per minute). Authentication, Pro eligibility and endpoint permission are checked before cache access. Requests that pass those checks consume quota even if their query is invalid. RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset expose the allowance and seconds until reset; a 429 response includes Retry-After. Losing Pro access, revoking the key or restricting an endpoint blocks subsequent calls.
What is outside the API licence and product boundary?
Public API v1 is not a raw or direct exchange feed. It does not provide unrestricted trades, quotes, every strike in a chain, bulk historical export, order entry, broker routing or account execution. It also does not grant permission to republish, resell or redistribute the source market data or analytics output.
Read the supporting context
Organizations that require machine-scale raw feeds, custom historical datasets or onward distribution should contract with an appropriately licensed market-data vendor. Realtime Options provides a limited programmatic analytics surface for research integrations.
How does API timing compare with the dashboard?
The Pro product is described as near-real-time because licensed vendor delivery and application processing add normal latency. The API exposes aggregated analytics under the same research-only boundary; it is not designed for latency-sensitive execution. The three-day trial uses 15-minute delayed dashboards and does not unlock Pro API access.
Read the supporting context
Open interest retains its cleared daily cadence wherever it appears in research context. More frequent requests cannot convert a daily field into live open interest.
Common questions
Does Realtime Options have a public API?
Yes. Active Pro accounts can use authenticated, read-only Public API v1 for aggregated Buy/Sell Pressure, Algo Flow, 0DTE Flow & Gamma Exposure, and Greeks by Strike analytics, subject to the account's enabled endpoints and current rate limit.
Which Public API v1 endpoints are available?
Public API v1 provides GET /api/public/v1/market/buy-sell-pressure, GET /api/public/v1/market/algo-flow, GET /api/public/v1/market/zero-dte-gex and GET /api/public/v1/market/greeks-by-strike. Active Pro accounts use a bearer key and a shared account-specific per-minute limit; available endpoints depend on account permissions.
Can I get 0DTE GEX through the Realtime Options API?
Yes. GET /api/public/v1/market/zero-dte-gex accepts ticker (default SPY) and optional date in YYYY-MM-DD format. It returns the dashboard's strike-level gamma exposure, scaled GEX, call/put premium, volume, open interest and summary metadata. It initially targets today/tomorrow expirations and can fall back to nearby dates, so it is not a strict same-day-only feed.
Can I get gamma, vanna and charm by strike through the API?
Yes. GET /api/public/v1/market/greeks-by-strike accepts symbol (default SPY) and optional date in YYYY-MM-DD format. It returns strike, gamma, vanna and charm together across up to 20 dashboard-selected strikes, plus spot and Greek-source coverage metadata. The exposures may use stored Greeks, derived Greeks or legacy proxies when inputs are missing.
Is the API a raw options market-data feed?
No. It returns defined aggregated analytics. It is not a direct exchange feed, unrestricted option-chain API, raw quote or trade feed, or bulk historical export service.
How many API keys can an account create?
One key can be active per account. The authenticated account owner can rotate or revoke it from the API Access screen.
Can the API place or manage options trades?
No. The API and dashboards are read-only. Realtime Options is not a broker, does not connect to brokerage execution and does not place, route or manage orders.


