> 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/apis.md).

# Market Replay API

Retrieve point-in-time historical market data through simple HTTP queries.

Welcome to Barchart's **Market Replay Technical Documentation.** 

Market Replay's API provides access to a comprehensive historical market data archive. This platform delivers point-in-time quote, trade, OHLC, and market statistics data across global asset classes. 

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question…</button>

<button type="button" class="button secondary" data-action="ask" data-query="How do I deploy my first project" data-icon="rocket-launch">Deploy your first project</button>

## Available API Endpoints

Use the endpoint that matches your data granularity and workflow. All endpoints require `username` and `password`.

| Endpoint                    | Intended design                                                                                                                       |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `queryticks.ashx`           | Returns tick-level trades, quotes, or both for one symbol within a single trading day for up to 365 days from today's date.           |
| `queryminutes.ashx`         | Returns intraday OHLCV bars for a symbol. Use `interval` to aggregate consecutive minutes into larger bars.                           |
| `querynearbyminutes.ashx`   | Returns intraday OHLCV bars for the active nearby futures contract. Use it with a futures root symbol for continuous nearby analysis. |
| `queryformtminutes.ashx`    | Returns stock minute bars that include Form T trades. Use it when pre-market and post-market activity matters.                        |
| `queryeod.ashx`             | Returns daily or aggregated OHLCV history. It supports equities, futures, options, nearby series, and continuation series.            |
| `queryminutedaterange.ashx` | Returns the first and last available minute record for each requested symbol. Use it to plan minute-data backfills.                   |
| `queryeoddaterange.ashx`    | Returns the first and last available end-of-day record for each requested symbol. Use it to plan EOD backfills.                       |
| `queryevents.ashx`          | Returns stock splits, dividends, and earnings events for one or more symbols. Use it to support adjustments and event analysis.       |
| `futuresoptions`            | Returns an end-of-day futures options chain in CSV format for one root symbol and date.                                               |
| `futuresoptions/json`       | Returns an end-of-day futures options chain in JSON format for one root symbol and date. It can include enabled aggregate statistics. |

## Popular tasks

Market Replay provides point-in-time historical market data through simple HTTP queries.

Retrieve trades, quotes, intraday OHLC bars, end-of-day history, and corporate events. Use it for backtesting, research, operational reconciliation, compliance, and historical data backfills.

{% hint style="info" %}
New to Market Replay? Start with [Quickstart](/market-replay-docs/getting-started/quickstart.md). It makes a minute-data request in five minutes.
{% endhint %}

## Start here

* [Quickstart](/market-replay-docs/getting-started/quickstart.md) — make your first authenticated request.
* [Python example](/market-replay-docs/getting-started/python-example.md), [JavaScript example](/market-replay-docs/getting-started/javascript-example.md), and [curl examples](/market-replay-docs/getting-started/curl-examples.md) — adapt a working request to your stack.

## Choose a query type

* [Tick queries](/market-replay-docs/api-query-types/tick-queries.md) — retrieve tick-level trades and quotes.
* [Minute queries](/market-replay-docs/api-query-types/minute-queries.md) — retrieve intraday OHLC bars and futures variants.
* [End-of-day queries](/market-replay-docs/api-query-types/end-of-day-queries.md) — retrieve daily and aggregated bars.
* [Events and date range queries](/market-replay-docs/api-query-types/events-queries.md) — find available history and stock events.
* [Futures options EOD](/market-replay-docs/api-query-types/futures-options-eod.md) — retrieve options chains for a root and date.

## Reference

Every request authenticates with your Market Replay `username` and `password`. Most endpoints return comma-delimited text.

* [Authentication](/market-replay-docs/reference/authentication.md) — authenticate requests and protect credentials.
* [Symbols and notation](/market-replay-docs/reference/symbols-and-notation.md) — format equity, futures, nearby, and options symbols.
* [Query parameter cheat sheet](/market-replay-docs/reference/query-parameter-cheat-sheet.md) — compare common parameters by endpoint.
* [Response formats](/market-replay-docs/reference/response-formats.md) — parse CSV and JSON responses.
* [Errors and troubleshooting](/market-replay-docs/reference/errors-and-troubleshooting.md) — resolve common request and entitlement issues.


---

# 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://developer.barchart.com/market-replay-docs/apis.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.