# Use the /v1 data endpoints

Raw SQL gives you everything, but most integrations want a handful of well-shaped answers. The `/v1` endpoints are that: pre-shaped, contract-stable JSON for the questions partners actually ask, so your integration does not break when the warehouse evolves underneath.

## What is on /v1

**Identity and accounts**

- `GET /v1/me` confirms who the token belongs to.
- `GET /v1/accounts` lists the Amazon accounts you can query.

**Advertising performance**

- `GET /v1/ads/account-summary` for topline spend, sales, and efficiency.
- `GET /v1/ads/account-pacing` for where the month is heading.
- `GET /v1/ads/campaign-performance` per campaign.
- `GET /v1/ads/search-terms` for search-term rows.
- `GET /v1/ads/asin-performance` per ASIN.

**Retail**

- `GET /v1/retail/sales` and `GET /v1/retail/traffic` for ordered revenue, units, sessions, and conversion.

**Brand Analytics**

- `GET /v1/brand-analytics/search-query-performance` for weekly Search Query Performance. Accounts without SQP data return a normal response with an availability note rather than an error.

**Brand memory** (the why behind the numbers, covered in full in [Work with brand memory](/knowledge-base/builder-platform/how-to/work-with-brand-memory))

- `GET /v1/timeline` reads the brand change log, filterable by brand, family, kind, date window, and stake facets. `POST /v1/timeline/event` appends an event such as a launch, price test, or stockout, and `POST /v1/timeline/event/[id]/corroborate` confirms a stake. Appending needs the timeline write scope, which is opt-in at mint time.
- `GET /v1/context/docs` and `GET /v1/context/doc` read brand context documents. Context is authored through the [plugin's brand setup](/knowledge-base/plugin/how-to/set-up-a-brand); `/v1` reads it.

## Conventions that hold everywhere

- Parameters are `snake_case`; list responses paginate with a cursor.
- Money comes with an explicit currency.
- Date windows anchor to the latest complete Amazon data day, so "last 7 days" means seven days you can trust, not a partial today.
- Errors return `{ "error": { "code", "message" } }` with stable codes worth branching on.

## Related

- [Query the warehouse](/knowledge-base/builder-platform/how-to/query-the-warehouse) (when /v1 does not have the shape you need)
- [Get access](/knowledge-base/builder-platform/getting-started/get-access)
- Full parameter-level reference: [mcp.mixshift.io/developers](https://mcp.mixshift.io/developers)