> For the complete documentation index, see [llms.txt](https://docs.volven.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volven.io/modules/ui-overview/orders.md).
# Orders
Manage and view your open and historical orders.
Algorithmic trading tends to generate high quantity of orders. In Volven Terminal you can easily view and manage all open and historical orders across all exchanges in one format.
{% hint style="info" %}
You can search for product, exchange and order type. You can also filter based on order status and order type.
{% endhint %}
| Default Columns | Purpose |
| --------------- | --------------------------------------------- |
| Exchange | Which exchange the trade was executed |
| Status | Buy or Sell order, and order status |
| Product | Pair traded with text on hover |
| Type | Order type (for example Limit, Market) |
| Size | Size of the trade |
| Price Limit | Price limit of the order |
| Order Value | Quote value of the trade |
| Filled | Gauge that fills and shows percentage of fill |
| Time Placed | The time of the trade |
| Actions | Cancel button to cancel the order |
---
# 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.volven.io/modules/ui-overview/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.
