---
title: "Get result segment axes (v2)"
method: GET
path: "/api/v1/research/result-segment-axes-v2/{id}"
tags: ["research"]
---

# Get result segment axes (v2)

`GET /api/v1/research/result-segment-axes-v2/{id}`

## Request

- Base URL: `https://point11.ai`
- URL: `https://point11.ai/api/v1/research/result-segment-axes-v2/{id}`
- Auth: one of:
  - HTTP bearer
  - OAuth 2 (authorization code, authorization URL `https://auth.point11.ai/oauth2/authorize`, token URL `https://auth.point11.ai/oauth2/token`)

Get which axes one Research campaign's results breakdown (research_result_segments_get_v4) lists an entry on, without counting a figure: audience, channel, store and product (revenue line) when the campaign's customers carry one, and tone and topic when the respondents of the range from to to (the days research_results_get_v7's range names) take one, read from every accepted answer of those days, so after a study's edit a tone or topic can come from answers to the earlier study alone. Omit from and to before the campaign's first interview to read the customers' axes alone. A campaign your organization does not own is not found.

## Path parameters

- `id` string, uuid, required: The campaign id from research.campaigns.list.v1.

## Query parameters

- `from` string, date: The range's first UTC day, as research.results.get.v5's range names it: tones and topics are read over its days. Omit it and to before the campaign's first interview.
- `to` string, date: The range's last UTC day, as research.results.get.v5's range names it.

## Headers

- `Point11-Organization` string, uuid

## Response `200`

Success.

- ResearchResultSegmentAxesGetV2Response
  - `campaignId` string, uuid, required
  - `axes` string[], required: The axes research.result-segments.get.v4 lists an entry on, in its order: audience, channel, store, product, sentiment, topic.

## Other responses

- `400`: The input, query, or Idempotency-Key is invalid.
- `401`: The bearer is missing, expired, or not accepted.
- `403`: The credential lacks the operation's scope or role, or the operation needs a different door.
- `404`: The resource or organization does not exist for this caller.
- `405`: This path takes another HTTP method, named in `Allow`.
- `409`: The request conflicts with current state or with prior use of its Idempotency-Key.
- `413`: The request, or the answer it asks for, is too large; narrow it.
- `429`: The credential's rate budget is spent; retry after `Retry-After` seconds.
- `500`: An unexpected server failure; retry later. Only `request_id` identifies it.
- `503`: A dependency is temporarily unavailable; retry after `Retry-After` seconds.
- `default`: Another status a product answers for its own refusal (for example `415` for an unsupported attachment); branch on `code`.

---

[API](https://skmtc.dev/point11/apis/point11-api.md) · [All operations](https://skmtc.dev/point11/apis/point11-api/llms.txt) · [OpenAPI document](https://skmtc.dev/point11/apis/point11-api/revisions/36a84c7aca11?raw)