Events & Markets

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 one or more markets, which are the outcomes you can trade.

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:

Field	Description
`id`	Unique identifier
`title`	The prediction question
`slug`	URL-friendly identifier
`status`	Current state: `open`, `stopped`, `resolved`, `cancelled`, `paused`, or `reversed`
`category`	Array of category objects the event belongs to
`markets`	Array of outcome markets
`bet_end_date`	When betting closes
`resolve_date`	When the event was resolved
`resolution_mode`	How markets resolve within the event (see below)
`description`	Full question details and resolution criteria

Event statuses

open

The event is active and accepting bets. You can place, modify, and cancel orders.

stopped

Trading has stopped — bet_end_date has passed — but the event has not yet resolved. No new orders are accepted.

resolved

The outcome has been determined. Winning wagers are paid out and losing wagers are settled. The event is read-only.

cancelled

The event was cancelled and will not resolve normally.

paused

Trading is temporarily paused on this event.

reversed

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.” Every market is binary: it resolves to exactly one of two sides — long or short. You never get a third outcome on a single market.

Position	Meaning
`long`	One side of the binary market — the side `price` refers to
`short`	The opposite side

When the market resolves to long, long holders are paid and short holders lose. When it resolves to short, short holders are paid and long holders lose.

Position labels

Display labels for each side come from long_label and short_label. The position_labels field indicates the label style:

`position_labels`	Long side	Short side
`yesno`	Yes	No
`updown`	Up	Down
`custom`	Value of `long_label`	Value of `short_label`

Always read long_label and short_label when rendering UI — they hold the strings to show for each side, including for yesno and updown. With yesno or updown, long/short map to a positive vs negative claim (Yes/No, Up/Down). With custom, the two sides are named outcomes — not necessarily yes/no. For example, an NBA game with no ties is one event (“Bulls vs. Lakers”) with a single market. Long stands for Bulls and short for Lakers:

{
  "id": 501,
  "title": "Bulls vs. Lakers",
  "price": 0.58,
  "status": "active",
  "position_labels": "custom",
  "long_label": "Bulls",
  "short_label": "Lakers"
}

Here betting position: "long" is betting on the Bulls; position: "short" is betting on the Lakers.

Price is always the long side

The market price is the current implied probability of the long position (0–1). In the Bulls vs. Lakers example, 0.58 means a 58% chance long (Bulls) wins. The implied short price is 1 - price (here, 0.42 for the Lakers). When you place orders, position: "long" or position: "short" selects which side you trade. See Orders for how side (bid/ask) combines with position.

Market fields

Field	Description
`id`	Unique identifier
`title`	The outcome this market represents
`price`	Current implied probability of long (0–1)
`status`	Market status: `active`, `resolved`, `paused`, `stopped`, `cancelled`, or `reversed`
`position_labels`	Label style: `yesno`, `updown`, or `custom`
`long_label`	Display label for the long side
`short_label`	Display label for the short side

Resolution modes

Events use a resolution_mode field that determines how many markets can resolve to long (win):

exclusive
non_exclusive

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. Each candidate is its own binary market (long = that candidate wins, short = they do not).

Browsing and filtering events

Use GET /events/ to list events. The endpoint supports the following filters:

Parameter	Description
`categories`	Filter by one or more category IDs
`tag`	Filter by tag name
`search`	Full-text search on event titles (max 100 chars)
`currency_mode`	`play_money` or `real_money` — filters events by the trading mode
`resolved_only`	Set to `true` to return only resolved events
`pending_resolution`	Set to `true` to return events awaiting resolution
`live`	Set to `true` to return only currently live events

For live or in-play markets, use the live=true filter on GET /events/ to discover active events, then poll GET /events/{id}/ for updated details.

# 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.

Get Started

Core Concepts

Guides

Events

Event statuses

Markets

Position labels

Price is always the long side

Market fields

Resolution modes

Browsing and filtering events

​Events

​Event statuses

​Markets

​Position labels

​Price is always the long side

​Market fields

​Resolution modes

​Browsing and filtering events

Events

Event statuses

Markets

Position labels

Price is always the long side

Market fields

Resolution modes

Browsing and filtering events