The Prediction Market Events APIs help developers work with top-level event discovery and event metadata across supported prediction platforms.
Use these endpoints to build event hubs, landing pages, category feeds, and search-driven navigation.
Key Benefits of the Events APIs
- Event-first discovery – Organize markets around shared questions or outcome sets.
- Cross-platform browsing – Pull event data across supported prediction venues.
- Search and filtering – Power event exploration with search and platform-aware filters.
- Market rollups – Surface event-level volume, liquidity, and nested market context.
Events API Endpoints
The Events APIs offer three core endpoints for browsing and retrieving prediction events.
List Prediction-Market Events
GET /v4/data/prediction/events
List prediction-market events across supported platforms.
Useful for category pages, discovery feeds, and event-level navigation with optional nested market data.
Get a Prediction-Market Event by ID
GET /v4/data/prediction/events/{id}
Retrieve a single event by its platform-native identifier.
Useful for event detail pages, direct links, and loading the parent object for related markets.
Unified Search
GET /v4/data/prediction/search
Search across prediction entities such as events, tags, and profiles.
Useful for search bars, autocomplete, and discovery workflows that begin with user intent rather than a known identifier.
Supported Platforms
- Polymarket —
polymarket - Kalshi —
kalshi
Use Cases for Developers
- Build event landing pages with rollups across related markets.
- Create search and browse experiences for prediction-market discovery.
- Group markets into human-readable themes like elections, sports, or crypto.
- Improve navigation with event-level metadata before showing market-level pricing data.
{`
Events API FAQs
What is an event in the Prediction Market API?
An event is a top-level grouping for one or more related markets that share a common question set or theme, such as an election, sports match, or macroeconomic outcome.
When should I use the events list instead of the markets list?
Use the events list when you want a broader discovery layer with grouped context. Use the markets list when you need tradeable market-level detail like prices, liquidity, or orderbooks.