> For the complete documentation index, see [llms.txt](https://help.topstepx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.topstepx.com/components/trades.md).

# Trades

## Trades Component

<figure><img src="/files/5qKEvud1tJfpJSmIQEIH" alt=""><figcaption></figcaption></figure>

The Trades component contains the following information:

* **Symbol** - The symbol associated with the contract.
* **Size** - The volume of the contract that was traded.
* **Time** - Date and time when the initial trade filled.
* **Entry** **Price** - The fill price of the contract during the initial trade (opened).
* **Exit** **Price** - The fill price of the contract when the trade was paired (closed).
* **P\&L** - Profit or loss associated with the trade. A Green value indicates a profit. A Red value indicates a loss.
* **Fees** - Round turn exchange and regulatory fees associated with the trade.

To add Trades to your layout, first add it as a [component](/components.md).

#### Export Trades

To export the data in the Trades component, click the button at the bottom left of the component.

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


---

# 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://help.topstepx.com/components/trades.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.