# Bet history

You can check the bet history both in the bot application and on your web dashboard.\
\
In the bot application, the bet history can be found in the first part highlighted in the red rectangle. If you wish to clear the local bet history, you can use the **CLEAR** button. Please note that even if you clear the local history, the bet history is still saved on our website, and you can access it through the web dashboard.

<figure><img src="/files/fwblVADZ2dd0qPsmywyD" alt=""><figcaption></figcaption></figure>

The image below displays a screenshot of the bet history on the web dashboard.

<figure><img src="/files/SsJM5PHdQdRnz9wa4ijD" alt=""><figcaption></figcaption></figure>

On the [bet history](https://betmatic.app/punter/bet/history) page, you can search the bet history and even download it.

## Features

The bet history page includes several useful features:

* **Filtering Options**: Use various filters to find specific bets
* **Label Column**: View and edit [Strategy Labels](/documentation/bet-engine/strategy-labels.md) for each bet to track performance across different strategies
* **CSV Export**: Download your complete bet history including strategy labels for detailed analysis
* **Detailed View**: Click on any bet row to view comprehensive bet details

We highly recommend using our web portal to review the bet history, as it provides several filtering options and the ability to organize bets by strategy labels. Additionally, you have the option to download the history as a CSV file with all strategy labels included, enabling you to run your own analysis on different betting strategies.


---

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

```
GET https://betmatic.gitbook.io/documentation/bet-engine/notifications/notification-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.