API Reference¶
Lavender Gateway exposes its Greeks through multiple API families. All return the same underlying data — they differ only in wire format and parameter naming.
API Families¶
| API | Path | Use Case |
|---|---|---|
| Lavender API | /l1/ |
Primary API — extended Greeks, field groups, term structure, filtering |
| Alpaca Compatible | /v1beta1/ |
Speaks the Alpaca options snapshots protocol |
| AlphaVantage Compatible | /query |
Speaks the AlphaVantage Realtime Options protocol |
| Intrinio Compatible | /options/chain/ |
Speaks the Intrinio options chain protocol |
| LiveVol Compatible | /allaccess/ |
Speaks the LiveVol option quotes protocol |
| MarketData.app Compatible | /v1/options/ |
Speaks the MarketData.app chain and quotes protocol |
| Orats Compatible | /datav2/ |
Speaks the Orats strikes data protocol |
| Polygon.io Compatible | /v3/snapshot/ |
Speaks the Polygon.io option snapshots protocol |
| ThetaData Compatible | /v3/option/, /v2/bulk_snapshot/ |
Speaks the ThetaData v3 and v2 option snapshot protocols |
| Tradier Compatible | /v1/markets/ |
Speaks the Tradier option chains protocol |
The compatibility layers let you run Lavender alongside your existing vendor — same wire format your code already expects. Use it as a second opinion, a redundant source, or to access Lavender's extended Greeks through a familiar interface.
The Lavender native API (/l1/) is the recommended starting point for new integrations — it exposes the full feature set including field groups, term structure support, and 12 filter parameters.
Common Behavior¶
Authentication: No API key required on REST calls. Entitlement is configured at the gateway level — see Authentication.
Error responses return an appropriate HTTP status code:
| Code | Meaning |
|---|---|
400 |
Missing or invalid parameters |
404 |
Unknown endpoint or symbol |
502 |
Upstream data unavailable |