> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/data-warehouse/introduction.md).

# Introduction

This guide outlines various methods within the system's API for retrieving data about user accounts, product data, campaign details, and more, and will assist you in leveraging the full capabilities of data warehouse API.

The endpoints described in this guide are specifically designed to support users in configuring their own custom scenarios. These APIs can be utilized in the following ways:

**1. Reporting Purposes**

* Extract real-time data on user accounts, product and order details, or campaign performance directly from the system. Create custom reports or dashboards to track key performance indicators (KPIs), analyze trends, and support decision-making processes.

**2. Integration with Search Engines**

* Retrieve essential data such as product details, pricing, and stock levels from the system to feed into your own search engine infrastructure.

Each section of this documentation details the structure of API requests and responses, ensuring clarity and ease of use. The data retrieved through the API is always up-to-date, encompassing all records up to the exact moment the request is executed. This ensures that users have access to the most current information for their reporting needs.

**NOTE:** All methods described in this documentation should be executed using the `GET` method. It is also essential to include an `authorization` key in the header for each request, formatted as `Token <token>`.


---

# 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://apidocs.akinon.com/commerce-openapis/data-warehouse/introduction.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.
