> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/definitions/mifir/core-market-data.md).

# core market data

*In force · MiFIR Article 2(1), point (36b) · Consolidated version of 23 November 2025 · Checked against EUR-Lex on 30 Sep 2026 ·* [*Official source*](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014R0600-20251123)

### Definition

> **(36b)** ‘**core market data**’ means:
>
> **(a)** all of the following data on a given share or ETF at any given timestamp:
>
> **(i)** for continuous order books, the European best bid and offer with the corresponding volume;
>
> **(ii)** for auction trading systems, the price at which the trading algorithm would be best satisfied and the volume potentially executed at that price by participants in that system;
>
> **(iii)** the transaction price and volume executed at that price;
>
> **(iv)** for transactions, the type of trading system and the applicable waivers and deferrals;
>
> **(v)** except for the information referred to in points (i) and (ii), the market identifier code uniquely identifying the trading venue and, for other execution venues, the identifier code identifying the type of execution venue;
>
> **(vi)** the standardised instrument identifier that applies across execution venues;
>
> **(vii)** the timestamp information on the following, as applicable:
>
> **—** the execution of the transaction and any amendment thereto,
>
> **—** the entry of the best bids and offers into the order book,
>
> **—** the indication, in an auction trading system, of the prices or volumes,
>
> **—** the publication by the trading venues of the elements listed in the first, second and third indents,
>
> **—** the dissemination of core market data;
>
> **(b)** all of the following data on a given bond or OTC derivative at any given timestamp:
>
> **(i)** the transaction price and quantity or size executed at that price;
>
> **(ii)** the market identifier code uniquely identifying the trading venue and, for other execution venues, the identifier code identifying the type of execution venue;
>
> **(iii)** for bonds, the standardised instrument identifier that applies across execution venues;
>
> **(iv)** for OTC derivatives, the identifying reference data as referred to in Article 27(1), second subparagraph;
>
> **(v)** the timestamp information on the following:
>
> **—** the execution of the transaction and any amendment thereto,
>
> **—** the publication of the transaction by the trading venues,
>
> **—** the dissemination of core market data;
>
> **(vi)** the type of trading system and the applicable waivers and deferrals;

### Source

[MiFIR, Article 2(1), point (36b)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014R0600-20251123).


---

# 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://www.headlesslaw.com/definitions/mifir/core-market-data.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.