> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/cloud-delivery/cefi-spot-market-data/raw-order-book-snapshot.md).

# Raw order book snapshot

{% hint style="info" %}

### This data is included in the following Kaiko packages

* Level 1 & Level 2 Data \[Level 2 Aggregations Tier]
* Level 1 & Level 2 Data \[Level 2 Tick-Level Tier]
  {% endhint %}

## What is this dataset?

The raw data on which our Level 2 Aggregations such as market depth , bid/ask spread, and price slippage are built. Details a point-in-time view of the bids and asks on an exchange's order book to 10% depth. Used to build your own custom level 2 aggregations. At least one snapshot per minute.

### File structure details

* File Name: \[kaiko\_legacy\_slug]\_\[instrument\_symbol]\_\[date].csv<br>
  * Files are created on a daily basis.
  * example: oe\_btcusdt\_2023-05-30.csv
* Cut-off time: `00:00:00 UTC`
  * We use the timestamp when we send the Orderbook snapshot REST API requests to exchanges in order to cut-off the data points between days.
* Column Delimiter: , (comma)
* Decimal Mark (in numbers): . (dot)

| Column                                                                                 | Description                                                                                                                                                  | Example         |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------- |
| `date`                                                                                 | The timestamp when we send the REST API requests to exchanges in Unix Timestamp (in milliseconds)                                                            | `1676246400344` |
| `type`                                                                                 | Type(side) of the limit orders on the orderbook snapshot. a: ask. b: bid.                                                                                    | `a`             |
| `price`                                                                                | Quoted price                                                                                                                                                 | `21779.5`       |
| `amount`                                                                               | Amount of limit orders at the specific price (can be in base\_asset, quote\_asset or the number of contracts).                                               |                 |
| <p><code>exchange</code></p><p><br><strong>BigQuery and Snowflake only</strong></p>    | <p>Exchange <code>code.</code></p><p><br>See <a href="https://docs.kaiko.com/kaiko-rest-api/data-feeds/reference-data/exchange-codes">Exchange codes</a></p> | `cbse`          |
| <p><code>instrument</code><br><br><br><strong>BigQuery and Snowflake only</strong></p> | <p>Exchange <code>code.</code></p><p><br>See <a href="https://docs.kaiko.com/kaiko-rest-api/data-feeds/reference-data/exchange-codes">Exchange codes</a></p> | `btc-usd`       |


---

# 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://docs.kaiko.com/cloud-delivery/cefi-spot-market-data/raw-order-book-snapshot.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.