Downloads - API Spec & Sample Responses

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.

Download everything (.zip) api.md historical.md

Individual endpoint samples (18 files)

tickers.json 154 KB symbols.json 154 KB stock-summary.json 7 KB exposure-summary.json 1 KB exposure-gex.json 133 KB exposure-dex.json 63 KB exposure-vex.json 63 KB exposure-chex.json 65 KB exposure-levels.json 323 B exposure-narrative.json 1 KB exposure-zero-dte.json 29 KB maxpain.json 132 KB volatility.json 21 KB adv-volatility.json 558 KB vrp.json 2 KB surface.json 45 KB options.json 78 KB account.json 237 B

How to use these

Feed the spec to an LLM

Download api.md (live endpoints) and historical.md (point-in-time replay) and drop them into Claude, ChatGPT, Cursor, or your own agent's system prompt. Both 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

Every endpoint below is mirrored on historical.flashalpha.com with a required ?at=yyyy-MM-ddTHH:mm:ss query parameter. The response shape is identical to live - that's why we only ship one sample bundle. See the Historical API docs for coverage and field-level caveats.

What's in the .zip

api.md - full live-API spec in Markdown
historical.md - full Historical API spec
18 *.json files, one per endpoint, real live responses for SPY

Samples are regenerated periodically. Shape stability is guaranteed; specific values (spot price, IV, OI, etc.) drift with the market.