> 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/defend/bet-monitor/bets.md).

# Bets

The Bets screen provides a real-time view of all betting activity on your platform. Use this view to monitor bets as they're placed, investigate suspicious activity, and take action when needed.

***

## Access

Navigate to **DEFEND** → **Bet Monitor** → **Bets** in the platform sidebar.

***

## Interface Overview

### Bet Table

The main table displays all bets with the following columns:

| Column            | Description                                 |
| ----------------- | ------------------------------------------- |
| **Time**          | When the bet was placed                     |
| **Player ID**     | Unique identifier for the bettor            |
| **Fixture**       | The event being bet on                      |
| **Market**        | The specific market (e.g., 1X2, Over/Under) |
| **Selection**     | The outcome selected by the player          |
| **Odds**          | The odds at time of bet placement           |
| **Stake**         | The amount wagered                          |
| **Potential Win** | Maximum payout if bet wins                  |
| **Status**        | Current bet status (Open, Settled, Voided)  |

### Filters

Refine the bet list using available filters:

* **Time Range** — Today, Last 7 days, Custom range
* **Sport** — Filter by sport type
* **League** — Filter by specific competition
* **Market Type** — Filter by market category
* **Status** — Open, Settled, Voided
* **Risk Level** — Low, Medium, High

### Search

Use the search bar to find specific bets by:

* Player ID
* Fixture ID
* Bet ID

***

## Bet Details

Click on any bet row to view detailed information:

### Bet Information

* Full bet slip details
* Placement timestamp
* IP address and device info
* Bet history for this player

### Player Quick View

* Player risk profile
* Betting history summary
* Applied limits

### Fixture Context

* Current score and status
* Market odds at bet time vs current
* Other bets on this fixture

***

## Actions

### From Bet Details

| Action           | Description                     |
| ---------------- | ------------------------------- |
| **View Player**  | Navigate to full player profile |
| **View Fixture** | Open fixture details in TRADE   |
| **Flag Bet**     | Mark bet for review             |
|                  |                                 |
|                  |                                 |

### Bulk Actions

Select multiple bets to:

* Export to CSV
* Flag for review
* Add to watchlist

***

## Real-Time Updates

The Bets view updates automatically as new bets are placed. You can:

* **Pause** — Stop auto-refresh to analyze current data
* **Resume** — Continue real-time updates
* **Refresh** — Manually fetch latest data

***

## Related

* [Bet Monitor Overview](/u/defend/bet-monitor.md) — Bet monitoring concepts
* [Risk Controls](/u/defend/risk-controls.md) — Configure betting limits
* [Player Intelligence](/u/defend/step-4-player-management.md) — Player risk management


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lsports.eu/u/defend/bet-monitor/bets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.