> 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/concepts/bet-status-lifecycle.md).

# Bet Status Lifecycle

Suspended alone cannot tell you when to permanently remove a bet from your UI. It is normal for a bet to suspend and resume several times during a fixture. The `BetStatusId` field adds a fourth value, **Closed**, that gives you a reliable removal signal for that bet.

## State Machine

A bet moves through these states:

`Open (1) ⟷ Suspended (2) ⟷ Closed (4) → Settled (3)`

| **Status** | **Will it reopen?** | **UI guidance**               |
| ---------- | ------------------- | ----------------------------- |
| Open       | N/A                 | Show the bet, enable betting  |
| Suspended  | Very likely         | Show the bet, disable betting |
| Closed     | Rarely              | Remove the bet from your UI   |
| Settled    | No                  | Show the result               |

Closed is available at both the bet level and the market level. Treat it as final and remove the bet (or the market) from your UI. In rare cases a provider can revert it.

`Status` and `BetStatusId` share the same [enumeration](/u/trade/enumerations/bet-settlements-and-statuses.md#bet-status), with one difference: `Status` does not carry Closed. When a bet closes, `Status` reports Suspended (2) instead, so only `BetStatusId` gives you the removal signal.

## What a Closed Bet Looks Like

In an outright market, an eliminated participant arrives with `BetStatusId` set to Closed (4), while `Status` falls back to Suspended (2):

```json
{
  "Id": "213192246116247002",
  "Name": "Global Agenda",
  "Status": 2,
  "BetStatusId": 4,
  "Price": "15",
  "ProviderBetId": "0",
  "LastUpdate": "2026-07-20T23:27:48.7569313Z",
  "ParticipantId": 53894728
}
```

## Scope

TRADE sends `BetStatusId=4` (Closed) whenever a bet permanently closes. In outright markets, for example, individual bets close one at a time as participants are eliminated (such as a team eliminated from a "World Cup Winner" market), while the market itself stays relevant until the tournament resolves.

Closed is also available at the market level. Markets use the same enumeration as bets, so the IDs are identical: when all bets in a market are closed, the market status is Closed (4). See [Market Status](/u/trade/enumerations/bet-settlements-and-statuses.md#market-status).

## Migration

`BetStatusId` is delivered alongside the existing `Status` field, so current integrations keep working without changes. `Status` will be deprecated on **1 March 2027**. Migrate your display and removal logic to `BetStatusId` before then.

See [Bet Settlements & Statuses](/u/trade/enumerations/bet-settlements-and-statuses.md#bet-status) for the full enumeration, and [Market](/u/trade/integration/message-structure/market.md) / [Settlement](/u/trade/integration/message-structure/settlement.md) for where the field appears on the wire.


---

# 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/concepts/bet-status-lifecycle.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.