> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/windows/options-board.md).

# Options board

This table shows all options for the selected instrument with the specified expiration date.

<figure><img src="https://2207507098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOSB2AVpWygd626dcnm1c%2Fuploads%2FyJt2JOZZ5apvUgUsna3p%2FOpions%20boards.png?alt=media&amp;token=13f083a5-f8a7-4e8a-821c-f90ffb662ae8" alt=""><figcaption><p>Options board in the Tiger.com terminal</p></figcaption></figure>

To display data in a table:

* **Select a base asset. As a base asset, in the terminal you can now choose only futures of the Russian market.** &#x20;
* Enter the expiration date. Weekly, monthly, and quarterly options are traded on the Moscow Exchange.
* Select the number of strikes.

After selecting a series, the table displays all the options in this series. The left side of the table contains information on Call options, and the right side on Put options. The strikes in the column are taken from the Moscow Exchange service, and the rest of the data are from the terminal to which you connected.

| Column                            | Description                                                                    |
| --------------------------------- | ------------------------------------------------------------------------------ |
| <p>Call OI<br></p>                | <p>Open interest for Call option. <br></p>                                     |
| <p>Call ask<br></p>               | <p>Number of orders to sell the Call option.<br></p>                           |
| <p>Call demand<br></p>            | <p>Number of orders to buy the Call option. <br></p>                           |
| <p>Call last price<br></p>        | <p>The last price at which the trade was made.<br></p>                         |
| <p>Call theoretical price<br></p> | <p>The theoretical option price received from the data provider. <br></p>      |
| <p>Strike<br></p>                 | <p>Option strike. <br></p>                                                     |
| <p>Volatility<br></p>             | <p>The theoretical option volatility received from the data provider. <br></p> |
| <p>Put theoretical price<br></p>  | <p>The theoretical option price received from the data provider.<br></p>       |
| <p>Put ask<br></p>                | <p>Number of orders to sell the Put option.<br></p>                            |
| <p>Put demand  <br></p>           | <p>Number of orders to buy the Put option.<br></p>                             |
| <p>Put last price<br></p>         | <p>The last price at which the trade was made.<br></p>                         |
| <p>Put OI <br></p>                | <p>Open interest for Put option.<br></p>                                       |

By clicking on a specific strike with the right mouse button, you can open a DOM for the selected option and place orders there.


---

# 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://support.tiger.com/english/windows/options-board.md?ask=<question>&goal=<user_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.
