> For the complete documentation index, see [llms.txt](https://developer.barchart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.barchart.com/market-replay-docs/reference/symbols-and-notation.md).

# Symbols and notation

Use the right symbol format for the endpoint and asset type.

## Equities

Use the plain listing symbol.

Examples:

* `AAPL`
* `IBM`
* `CSCO`

## Futures contracts

Use the contract symbol when you want a specific expiry.

Examples:

* `ESH09`
* `ESU09`
* `NGH12`

## Futures root notation

Use the root when the endpoint supports nearby behavior.

Examples:

* `ES`
* `YM`
* `RS`

For endpoints that support nearby offsets, you can use root notation with a nearby number.

Examples:

* `ES1`
* `YM*3`
* `RS*1`

{% hint style="info" %}
Nearby notation picks a contract relative to the current front month.
{% endhint %}

## `*` notation

Some endpoints support `*` notation for futures.

Example:

* `RS*1`

When used, the response can prepend a `SYMBOL` or `CONTRACT` field so you can see which active contract each row belongs to.

## Nearby minute queries

`querynearbyminutes.ashx` uses only the root symbol.

If you pass a full contract, the month and year are ignored.

Example:

* `ES`

## EOD nearby series

For EOD nearest series, you can express the nearby offset in two ways:

* `symbol=ES1`
* `symbol=YM*3`

Or use:

* `symbol=ES`
* `nearby=2`

## Futures options in `queryeod.ashx`

For end-of-day futures options through `queryeod.ashx`, use this pattern:

```
UNDERLYING_MONTHYEAR|STRIKEC_OR_P
```

Example:

* `NGH12|600C`

## Futures options EOD endpoint

The dedicated futures options EOD endpoint does not use `symbol`.

It uses:

* `root`
* `date`

Example:

```
root=CK&date=2023-04-14
```

## Symbols lists

Some endpoints use `symbols` instead of `symbol`.

Use a comma-delimited list.

Examples:

* `symbols=IBM,AAPL`
* `symbols=ES,NG,CL`

This applies to:

* `queryevents.ashx`
* `queryminutedaterange.ashx`
* `queryeoddaterange.ashx`

## Quick checks

Before sending a request, confirm:

* the endpoint expects `symbol`, `symbols`, or `root`
* the symbol matches the asset type
* nearby notation is supported by that endpoint

## Related

* [Tick queries](/market-replay-docs/api-query-types/tick-queries.md)
* [Minute queries](/market-replay-docs/api-query-types/minute-queries.md)
* [End-of-day queries](/market-replay-docs/api-query-types/end-of-day-queries.md)
* [Futures options EOD](/market-replay-docs/api-query-types/futures-options-eod.md)


---

# 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://developer.barchart.com/market-replay-docs/reference/symbols-and-notation.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.