> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/enumerations/bet-settlements-and-statuses.md).

# Bet Settlements & Statuses

### Bet Settlement

| **Id** | **Value** | **Description**                |
| ------ | --------- | ------------------------------ |
| -1     | Canceled  | The bet settlement is canceled |
| 1      | Loser     | The bet has lost               |
| 2      | Winner    | The bet has won                |
| 3      | Refund    | There should be a refund       |
| 4      | HalfLost  | Half of the bet has lost       |
| 5      | HalfWon   | Half of the bet has won        |

### Bet Status

Bets and markets share this enumeration. The same IDs apply to the bet `Status` and `BetStatusId` fields and to the market status (see [Market Status](#market-status)).

| **Id** | **Value** | **Description**                                                                                          |
| ------ | --------- | -------------------------------------------------------------------------------------------------------- |
| 1      | Open      | The bet is open (bets can be placed)                                                                     |
| 2      | Suspended | The bet is temporarily unavailable (bets cannot be placed) and is very likely to reopen                  |
| 4      | Closed    | The bet is closed. Treat it as final and remove it from your UI. In rare cases a provider can revert it. |
| 3      | Settled   | The bet is settled (resulted), and a settlement is determined (see the settlement enumeration above)     |

**Closed is not supported on the `Status` field.** When a bet closes, `Status` carries Suspended (2) instead. Only `BetStatusId` carries Closed (4).

Closed and `Settlement` are independent. On a settlement message, a bet can carry a settlement outcome regardless of its `BetStatusId` value.

{% hint style="warning" %}
The `Status` field will be deprecated on **1 March 2027**. `BetStatusId` replaces it. Until that date, TRADE sends both fields on every message, so existing integrations keep working unchanged. Migrate your display and removal logic to `BetStatusId` before then.
{% endhint %}

TRADE sends `BetStatusId=4` (Closed) when a bet permanently closes, such as a participant eliminated from a "World Cup Winner" outright market. Closed is also available at the market level (see [Market Status](#market-status) below). See [Bet Status Lifecycle](/u/trade/concepts/bet-status-lifecycle.md) for the full state machine and scope.

### Market Status

Markets use the same enumeration as bets, with the same IDs. A market's status reflects the status of its bets:

| **Id** | **Value** | **Description**                                                                         |
| ------ | --------- | --------------------------------------------------------------------------------------- |
| 1      | Open      | At least one bet in the market is open                                                  |
| 2      | Suspended | All bets in the market are suspended                                                    |
| 3      | Settled   | All bets in the market are settled                                                      |
| 4      | Closed    | All bets in the market are closed. Treat the market as final and remove it from your UI |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lsports.eu/u/trade/enumerations/bet-settlements-and-statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.