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, stopped, resolved, cancelled, paused, or reversed
categoryArray of category objects the event belongs to
marketsArray of outcome markets
bet_end_dateWhen betting closes
resolve_dateWhen the event was resolved
resolution_modeHow markets resolve within the event (see below)
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 — bet_end_date 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.
The event was cancelled and will not resolve normally.
Trading is temporarily paused on this event.
A previous resolution was reversed. Check the event for updated resolution details.

​
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
priceCurrent implied probability (0–1)
statusMarket status: active, resolved, paused, stopped, cancelled, or reversed
position_labelsLabel style: yesno, updown, or custom
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.

​
Resolution modes

Events use a resolution_mode field that determines how many markets can resolve to long (win):
Only one market within the event can resolve to long. This is the default for mutually exclusive outcomes where exactly one result wins.Example: A presidential election event where only one candidate can win.

​
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
For live or in-play markets that update frequently, poll GET /events/{id}/live_data/ instead of the authenticated retrieve endpoint. 
# 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.