Docs

Preview

A preview of the lateas data API. Three read endpoints, one bearer key, one normalized schema across venues.

Authentication

Every request carries an API key as a bearer token:Authorization: Bearer $LATEAS_KEY. Keys are self-serve; usage is metered per request and per GB streamed.

Quickstart

shell

# 1. Set your key
export LATEAS_KEY=sk_live_…

# 2. List canonical events
curl https://api.lateas-data.com/v1/inventory?category=Crypto \
  -H "Authorization: Bearer $LATEAS_KEY"

Endpoints

GET/v1/inventory

Canonical cross-venue events. Filter by category, venue, status, resolution window.

GET /v1/inventory?category=Crypto&venue=polymarket

{ "data": [ { "canonical_event_id": "evt_…", "legs": [ … ] } ],
  "next": null }

GET/v1/historical

Books, trades, BBOs and volumes over a time range. Cursor-paginated; bulk export for large windows.

GET /v1/historical?venue=kalshi&market_id=BTC-31AUG
        &type=book&start=2026-08-01&end=2026-08-13

{ "data": [ { "ts_recv": 1756…, "price": 62000000, "size": 1400 } ] }

GET/v1/live

Server-sent events stream of live books/trades/BBOs. Subscribe by venue or market_id.

GET /v1/live?venue=polymarket  (text/event-stream)

event: bbo
data: { "market_id": "0xab…", "bid": 0.61, "ask": 0.63, "ts": 1756… }

Mockup. The API isn't live yet. See the API overview for the data surfaces.