> 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/orders.md).
# Orders
The Orders component provides a general overview of all orders associated with the Current Account over the last 7 days.
### Orders Component
The orders component contains the following information:
* **Time** - The time at which the position was entered.
* **Symbol** - The symbol associated with the contract
* **Size** - The number of contracts purchased during the trade.
* **Order Action** - Indicates whether the order is a Buy or a Sell. Possible values are *Buy* and *Sell*.
* **Order Type** - The order type. Possible values are *Market*, *Limit*, *Stop Market*, *Trailing Stop*, and *Stop Limit*.
* **Limit Price** - The limit price for the order. If the order is not a limit order, no value will be shown.
* **Stop Price** - The stop price for the order. If the order is not a stop market order, no value will be shown.
* **Execute Price -** The average entry price for the position when the order was filled.
* **Status** - The status of the order. Possible values are *Cancelled*, *Filled*, *Open*, and *Rejected*.
* **Cancel** - This button allows the user to cancel the open order at the current market price.
To add Orders to your layout, first add it as a [component](/components.md).
#### Export Orders
To export the data in the Orders component, click the button at the bottom left of the component.
---
# 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://help.topstepx.com/components/orders.md?ask=&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.
