> For the complete documentation index, see [llms.txt](https://quantinfra.gitbook.io/quantinfra-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantinfra.gitbook.io/quantinfra-docs/static-data/assets-exchanges-trading-sessions-commission.md).

# Assets, exchanges, trading sessions, commission

## Asset

When defining a contract, its asset defines the underlying asset for the contract. The usage of assets is reserved for future versions, so that positions in different contracts with the same underlying asset can be aggregated for risk calculation purposes.

## Exchange

<table><thead><tr><th width="218.4453125">Property</th><th>Description</th></tr></thead><tbody><tr><td>ExchangeId</td><td>Unique ID</td></tr><tr><td>Name</td><td></td></tr><tr><td>Timezone</td><td>Uses <a href="https://nodatime.org/2.0.x/api/NodaTime.DateTimeZoneProviders.html">NodaTime TZDB provider</a></td></tr></tbody></table>

## Trading session

Trading sessions are linked to an exchange.

All days and times are in the exchange's time zone.

A single contract (contract template, to be precise) can have multiple trading sessions.

<table><thead><tr><th width="218.4453125">Property</th><th>Description</th></tr></thead><tbody><tr><td>TradingSessionId</td><td>Unique ID</td></tr><tr><td>Name</td><td></td></tr><tr><td>Days</td><td>Collection of intervals, each interval being defined as (Start Day Of Week, Start Time, End Day Of Week, End Time)</td></tr><tr><td>Is24x7</td><td>Denotes that the trading session doesn't actuall start or end</td></tr><tr><td>IsRth</td><td>Denotes that this is the primary trading session</td></tr></tbody></table>

## Commissions

One contract (contract template, to be precise) can be subject to several commissions. If several commissions are configured, each trade will contain the amount of each particular commission in addition to the total amount.

<table><thead><tr><th width="218.4453125">Property</th><th>Description</th></tr></thead><tbody><tr><td>CommissionId</td><td>Unique ID</td></tr><tr><td>Name</td><td></td></tr><tr><td>Description</td><td></td></tr><tr><td>FixedPerShare</td><td>Commission is calculated as FixedPerShare * TradeVolume</td></tr><tr><td>Floating</td><td>Commission is calculated as TradeValue * Floating</td></tr><tr><td>Currency</td><td>Commission currency</td></tr><tr><td>CommissionStructureType</td><td><ul><li>Broker</li><li>Exchange</li><li>Slippage</li><li>Other</li></ul></td></tr><tr><td>BrokerId</td><td>For broker commissions</td></tr><tr><td>ExchangeId</td><td>For exchange commissions</td></tr></tbody></table>


---

# 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://quantinfra.gitbook.io/quantinfra-docs/static-data/assets-exchanges-trading-sessions-commission.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.