> For the complete documentation index, see [llms.txt](https://developer.nexx360.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.nexx360.io/platform-apis/reporting-api/reporting-v3.md).

# Reporting v3

<mark style="color:green;">`POST`</mark> `/v3/api`

Use this method to get your reporting data

You must specify which table you want to query using the 'table' property.

You must also provide a 'startDate' and an 'endDate'. The API will return data between these two dates (inclusive).

#### :red\_circle: <mark style="color:red;">**V3 data becomes available starting on 2026-03-01**</mark>

#### **Headers**

| Name          | Value           |
| ------------- | --------------- |
| Authorization | `Basic <token>` |

#### Optional features

Every endpoint below accepts the following optional properties on the request body:

* `filters` — restrict rows by dimension or metric value. Dimension filters become `WHERE` conditions, metric filters become `HAVING` conditions.

  ```typescript
  filters: [
    { field: "ssp", op: "eq", value: "appnexus" },
    { field: "country", op: "in", value: ["FR", "DE"] },
    { field: "domain", op: "like", value: "%news%" },
    { field: "impressions", op: "gt", value: 100 }
  ]
  ```
* `orderBy` — sort the result rows. `field` references a dimension or metric alias (or its name when no alias is set). `dir` is `ASC` or `DESC`.

  ```typescript
  orderBy: [
    { field: "impressions", dir: "DESC" },
    { field: "country", dir: "ASC" }
  ]
  ```
* `pageSize` + `offset` — paginate the response. `pageSize` defaults to 1000 (max 10000). `offset` defaults to 0 (max 1\_000\_000). Always pair these with an `orderBy` to get a stable order across pages.

  ```typescript
  pageSize: 100,
  offset: 200
  ```

#### Filter operators

| Operator | Meaning                | Value type       | Notes                                                                                                |
| -------- | ---------------------- | ---------------- | ---------------------------------------------------------------------------------------------------- |
| `eq`     | equal                  | string \| number | `=`                                                                                                  |
| `neq`    | not equal              | string \| number | `!=`                                                                                                 |
| `gt`     | greater than           | string \| number | `>`                                                                                                  |
| `gte`    | greater than or equal  | string \| number | `>=`                                                                                                 |
| `lt`     | less than              | string \| number | `<`                                                                                                  |
| `lte`    | less than or equal     | string \| number | `<=`                                                                                                 |
| `like`   | case-insensitive match | string           | Raw SQL `ILIKE` pattern — write `%` and `_` yourself (e.g. `"%news%"`, `"news.%"`). Dimensions only. |
| `nlike`  | negated `like`         | string           | Same pattern rules as `like`.                                                                        |
| `in`     | value in list          | array            | Max 1000 items.                                                                                      |
| `nin`    | value not in list      | array            | Max 1000 items.                                                                                      |

{% hint style="info" %}
`like` and `nlike` only apply to dimensions (string columns). They are rejected on metric fields. All other operators work on both dimensions and metrics.
{% endhint %}

{% content-ref url="/pages/ypH3XFNwJyB76njnv3Sp" %}
[Impressions](/platform-apis/reporting-api/reporting-v3/impressions.md)
{% endcontent-ref %}

{% content-ref url="/pages/iuXSgbWvkQmHcBx5wI6F" %}
[Auctions](/platform-apis/reporting-api/reporting-v3/auctions.md)
{% endcontent-ref %}

{% content-ref url="/pages/O79aCAs2TpHoo8LKGmsf" %}
[Bids](/platform-apis/reporting-api/reporting-v3/bids.md)
{% endcontent-ref %}

{% content-ref url="/pages/o1IGVveXKuoUATqnOPaT" %}
[Vast Events](/platform-apis/reporting-api/reporting-v3/vast-events.md)
{% endcontent-ref %}

{% content-ref url="/pages/DADtwD4unmxm68iq4DkU" %}
[Viewed](/platform-apis/reporting-api/reporting-v3/viewed.md)
{% endcontent-ref %}

{% content-ref url="/pages/KYGREefw89qlKlHiY44l" %}
[Deals](/platform-apis/reporting-api/reporting-v3/deals.md)
{% endcontent-ref %}

{% content-ref url="/pages/Hu41Y9qlRkMDxuzO2R9i" %}
[Deal Forecast](/platform-apis/reporting-api/reporting-v3/deal-forecast.md)
{% endcontent-ref %}


---

# 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.nexx360.io/platform-apis/reporting-api/reporting-v3.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.