Downloads
The full API spec in Markdown and a real JSON response from every endpoint. Feed the spec to your LLM. Wire the samples into mocks, SDK tests, or fixtures.
Downloads for AI agents & integration
Full API spec in Markdown plus a real response from every endpoint. Feed the spec to your LLM, wire the JSON samples into mocks or tests.
Backtesting? Pair these with the Historical API bundle: historical-gex.json, historical-vrp.json, etc., or the OpenAPI at historical.openapi.json.
Individual endpoint samples (70 files)
How to use these
Feed the spec to an LLM
Download api.md (live endpoints), historical.md (point-in-time replay), or risk-engine.md (Risk Engine open beta - every flag and error code) and drop them into Claude, ChatGPT, Cursor, or your own agent's system prompt. All files are designed to be complete, self-contained references.
Wire samples into tests or mocks
Each JSON file under /docs/samples/ is a real response the live API returned for SPY. Use them as:
- Fixtures for SDK unit tests
- Mock payloads for UI development
- Schema inputs for codegen
- Reference when building client-side types
# Python example - load a sample
import json, urllib.request
url = "https://flashalpha.com/docs/samples/exposure-gex.json"
sample = json.loads(urllib.request.urlopen(url).read())
Historical endpoints use the same shape (plus dedicated samples + OpenAPI)
The analytics endpoints (52 replay routes; earnings, screener and structures are live-only) are mirrored on historical.flashalpha.com with a required ?at=yyyy-MM-ddTHH:mm:ss query parameter (Alpha tier). Response shapes are identical to live, so the same SDK code works against both. Two extra artifacts make backtest and codegen workflows easier:
historical.openapi.json- OpenAPI 3.1 spec withhistorical.flashalpha.comas the server andatmarked required on every analytics path. Feed to Swagger UI, openapi-generator, or any LLM doing code synthesis.historical-*.json- real captures fromhistorical.flashalpha.com, frozen atat=2024-08-05T10:30:00(the August 2024 carry-unwind / VIX spike). Every numeric value is what the API actually returned for that timestamp - not illustrative or fabricated. Use them as a reproducible point fixture for tests; pull a fresh capture for any other moment. Files: coverage, GEX, VRP, max pain, exposure summary, option chain (single expiry, full greeks +svi_vol), stock summary. Plushistorical-stock-prices.json- daily OHLC bars backing the realized / forecast vol endpoints (a rolling window viadays=N, notat=-frozen).
See the Historical API docs for coverage and field-level caveats.
What's in the .zip
api.md- full live-API spec in Markdownhistorical.md- full Historical API spec- 70 live
*.jsonfiles, one per live endpoint, real responses forSPY(earnings samples useGME; realized/forecast useAAPL) - covers market data (stockquote,optionquote,surface-svi), exposure analytics (includingexposure-sheet,term-structure,basket,oi-diff), volatility/VRP (skew-term,spot-vol-correlation,volatility-realized,volatility-forecast,dispersion,expected-move,vrp-history), macro + universe, pricing helpers (pricing-greeks,pricing-iv,pricing-kelly), the 25-endpoint Flow Analytics + Raw Flow Data surface (includingflow-signals,flow-stocks-bars), earnings, multi-legstructures, thescreener, and reference data - 8
historical-*.jsonfiles for the point-in-time Historical API (incl.historical-stock-prices- rolling daily OHLC) historical.openapi.json- OpenAPI 3.1 spec for the Historical API
Live samples are regenerated periodically; shape stability is guaranteed and specific values drift with the market. Historical samples are real captures from historical.flashalpha.com at a frozen at= anchor (currently 2024-08-05T10:30:00) - every value is what the API actually returned at that minute. They are reproducible test fixtures, not illustrative or fabricated.