> For the complete documentation index, see [llms.txt](https://sway-technologies.gitbook.io/sway-charts-api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sway-technologies.gitbook.io/sway-charts-api-documentation/rest-api-specification/cash-transaction/position.md).

# Position

| Field                | Value                                                                                     | Type                                                                                                                          |
| -------------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **account**          | Unique code of the account                                                                | [Account code](/sway-charts-api-documentation/rest-api-specification/getting-started/data-types-and-formats.md), **required** |
| **version**          | Numeric version of the account.                                                           | [Number](/sway-charts-api-documentation/rest-api-specification/getting-started/data-types-and-formats.md), **required**       |
| **positionCode**     | Unique code of a position                                                                 | String, **required**                                                                                                          |
| **symbol**           | Symbol of the position’s instrument                                                       | String, **required**                                                                                                          |
| **quantity**         | Current quantity of the position in units (not in lots); unsigned value                   | [Number](/sway-charts-api-documentation/rest-api-specification/getting-started/data-types-and-formats.md), **required**       |
| **quantityNotional** | Current quantity notional of the position in notional units (not in lots); unsigned value | [Number](/sway-charts-api-documentation/rest-api-specification/getting-started/data-types-and-formats.md), **required**       |
| **side**             | Side of the position. Either `BUY` (long) or `SELL` (short)                               | String, **required**                                                                                                          |
| **openTime**         | Timestamp in UTC when this position was opened                                            | Timestamp, **required**                                                                                                       |
| **openPrice**        | Price at which the position was opened                                                    | [Number](/sway-charts-api-documentation/rest-api-specification/getting-started/data-types-and-formats.md), **required**       |
| **lastUpdateTime**   | Timestamp in UTC when this position was last updated                                      | Timestamp]\(#dates-times), **required**                                                                                       |


---

# 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://sway-technologies.gitbook.io/sway-charts-api-documentation/rest-api-specification/cash-transaction/position.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.