Skip to main content
An event is a prediction question that you can bet on — for example, “Who will win the 2024 US Presidential Election?” or “Will Bitcoin exceed $100,000 by end of year?” Each event has multiple markets, which represent the possible outcomes you can bet on.
The API uses the term markets for what were previously called “Outcomes” in older versions of the API. Events were previously called “Questions.”

Events

An event defines the question, the resolution criteria, and the timeframe. Key fields on an event object include:
FieldDescription
idUnique identifier
titleThe prediction question
slugURL-friendly identifier
statusCurrent state: open, closed, or resolved
categoriesTopic categories the event belongs to
marketsArray of outcome markets
close_timeWhen trading stops
resolution_dateWhen the event resolves
descriptionFull question details and resolution criteria

Event statuses

The event is active and accepting bets. You can place, modify, and cancel orders.
Trading has stopped — close_time has passed — but the event has not yet resolved. No new orders are accepted.
The outcome has been determined. Winning wagers are paid out and losing wagers are settled. The event is read-only.

Markets

Each market is a single outcome within an event. For example, the event “Who will win the 2024 US Presidential Election?” might have markets for “Candidate A”, “Candidate B”, and “Other.” Key fields on a market object include:
FieldDescription
idUnique identifier
titleThe outcome this market represents
slugURL-friendly identifier
priceCurrent implied probability (0–1)
The price field reflects the market’s current probability. A price of 0.65 means the market is trading at a 65% chance of that outcome occurring.

Market correlation types

Events use one of two correlation types that determine how prices across markets within the same event relate to each other.
All market prices within the event sum to 1. When you buy shares in one outcome, the prices of all other outcomes shift accordingly — just like a traditional prediction market.Example: An event with three markets at prices 0.50, 0.30, and 0.20 (sum = 1.00). If you buy heavily into the first market, its price rises while the others fall to maintain the sum.Use this type for mutually exclusive outcomes where exactly one will resolve true.

Browsing and filtering events

Use GET /events/ to list events. The endpoint supports the following filters:
ParameterDescription
categoriesFilter by one or more category IDs
tagFilter by tag name
searchFull-text search on event titles (max 100 chars)
currency_modeplay_money or real_money — filters events by the trading mode
resolved_onlySet to true to return only resolved events
pending_resolutionSet to true to return events awaiting resolution
liveSet to true to return only currently live events
# List events in a category using play money
GET /events/?categories=5&currency_mode=play_money

# List resolved events
GET /events/?resolved_only=true&currency_mode=play_money
Use currency_mode=play_money while developing and testing your integration to avoid real financial exposure.