Skip to main content
A wager represents a position you hold in a market. When an order fills (fully or partially), the resulting shares you own become a wager. You can think of a wager as a record of your stake in a particular outcome. Wagers are read-only — they are created automatically when orders execute, not by direct API calls.

​
How wagers relate to orders and events

  • One order can produce one or more wagers as it fills over time.
  • A wager is always linked to a specific market (outcome) within an event.
  • Multiple wagers on the same market are aggregated into your net position.

​
Wager statuses

A purchased wager means your position is active. It will transition to won, lost, or sold once the event resolves or you sell your shares.

​
Fetching your wagers

Use GET /wagers/ to list wagers. You can also fetch wagers for a specific event via GET /events/{id}/wagers/.

​
Filtering wagers

The /wagers/ endpoint supports several filters:

​
Wager resolution

When an event resolves, the API automatically settles all wagers associated with it:
  • Wagers on the winning market transition to won. Any payout is credited to your account.
  • Wagers on losing markets transition to lost. The staked amount is not returned.
  • If you sold your position before resolution (via an ask order), the wager transitions to sold regardless of the outcome.
Use GET /events/{id}/wagers/ to retrieve wager history for a specific event across all users, useful for displaying market participation data in your application.