Events API

Primary events feed: clustered RSS and news feeds, with optional Polymarket and Kalshi rows merged as first-class events. Reads are deterministic and regulator-friendly—built for prediction markets, analytics, and B2B data products.

Eventa uses the same /v1/events/* clustered feed—our multilingual curated slice plus filtered proposals. When Eventa ingestion is enabled, clusters reflect that rotating global mix over time.

Endpoints

GET /v1/events/latest — Latest RSS/clustered events; optional country/date filters. To merge venue rows into this list, pass include_polymarket=true or include_kalshi=true. Canonical standalone lists: GET /v1/markets/polymarket, GET /v1/markets/kalshi—see Markets API for full field notes.
GET /v1/events/trending — Events ordered by trend score
GET /v1/events/by-country?country=US — Events for a country
GET /v1/events/by-category?category=politics — Events by category
GET /v1/events/{event_id} — Single event by ID
GET /ready — Health: ingestion freshness and status (ready / degraded); HTTP 200 for probes

Authentication: X-API-Key header or api_key query parameter.

Response fields

Each event includes: event_id, title, category, country, trend_score, resolution_date, confidence, sources_count. With include_polymarket=true, Polymarket rows may add implied_probability and polymarket_clob_midpoint. With include_kalshi=true, Kalshi rows add implied_probability (YES last or mid). LLM-synthesized articles: GET /v1/news/latest. No prose—structured only.

Use cases

Prediction markets (resolution and trend data), analytics dashboards, B2B data feeds. Data is clustered from multiple sources with an audit trail.

How freshness works

A cold request may enqueue ingestion work; responses still return the latest materialized snapshot, and the pipeline keeps refreshing in the background. For capacity planning, treat the feed as eventually consistent with continuous updates rather than a single synchronous scrape per call.

API docs For prediction markets Get access