> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futuur.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events & Markets

> Understand events (predictions) and markets (outcomes) in Futuur.

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.

<Note>
  The API uses the term `markets` for what were previously called "Outcomes" in older versions of the API. Events were previously called "Questions."
</Note>

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

<AccordionGroup>
  <Accordion title="open">
    The event is active and accepting bets. You can place, modify, and cancel orders.
  </Accordion>

  <Accordion title="stopped">
    Trading has stopped — `bet_end_date` has passed — but the event has not yet resolved. No new orders are accepted.
  </Accordion>

  <Accordion title="resolved">
    The outcome has been determined. Winning wagers are paid out and losing wagers are settled. The event is read-only.
  </Accordion>

  <Accordion title="cancelled">
    The event was cancelled and will not resolve normally.
  </Accordion>

  <Accordion title="paused">
    Trading is temporarily paused on this event.
  </Accordion>

  <Accordion title="reversed">
    A previous resolution was reversed. Check the event for updated resolution details.
  </Accordion>
</AccordionGroup>

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

| Field             | Description                                                                          |
| ----------------- | ------------------------------------------------------------------------------------ |
| `id`              | Unique identifier                                                                    |
| `title`           | The outcome this market represents                                                   |
| `price`           | Current implied probability (0–1)                                                    |
| `status`          | Market status: `active`, `resolved`, `paused`, `stopped`, `cancelled`, or `reversed` |
| `position_labels` | Label 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):

<Tabs>
  <Tab title="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.
  </Tab>

  <Tab title="non_exclusive">
    Multiple markets can resolve to long. Each market has independent resolution rules.

    **Example:** An event asking "Which of these features will ship in Q1?" where several outcomes can be true at the same time.
  </Tab>
</Tabs>

## 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/`](/api-reference/events/list) to discover active events, then poll [`GET /events/{id}/`](/api-reference/events/retrieve) for updated details.

```bash theme={null}
# 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
```

<Tip>
  Use `currency_mode=play_money` while developing and testing your integration to avoid real financial exposure.
</Tip>