# Analytics Requests

Use `POST /analytics/resource/{experienceId}` for experience analysis requests. It accepts filters and all other request settings in the JSON payload.

For store-level analytics, use the sitewide endpoints:

* `POST /analytics/sitewide/snapshot` — summary KPI metrics with period-over-period percent changes, with optional audience segmentation
* `POST /analytics/sitewide/timeseries` — metric-over-time data with configurable granularity and optional audience segmentation
* `POST /analytics/sitewide/order-distribution` — order value histogram (KDE/CDF) and unit mix breakdown

The legacy `GET /analytics/resource/{experienceId}` endpoint is deprecated, is available during the beta only as a compatibility path, and will be removed when the beta version ends.

`GET /experiences-list` supports optional `limit`, `page`, `status`, and `category` query parameters. `page` is 1-indexed (`page >= 1`). Valid `status` values: `pending`, `started`, `ended`, `paused`. Valid `category` values: `experiment`, `personalization`.

`GET /experiences/{experienceId}` returns a wrapped response body in the shape `{ "experience": { ... } }`.


---

# Agent Instructions: 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:

```
GET https://docs.intelligems.io/developer-resources/external-api-dev/intelligems-external-api/analytics-requests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.