---
title: "Query dimension values"
method: POST
path: "/v6/dimensions/values/query"
tags: ["Dimensions"]
---

# Query dimension values

`POST /v6/dimensions/values/query`

These contain the dimension values that your user tracks against. For example, if you defined a dimension of "Location", your user could define their dimension values as "NA Branch", "Asia Branch", "EU Branch".

## Request body

- DimensionValueQueryParam
  - `cursor` string, nullable — Cursor from the previous paginated response
  - `limit` integer — Page size, i.e. number of items to return per page

## Response `200`

Success

- DimensionValuePaginatedResponse — Paginated response for dimension values
  - `result` 'SUCCESS' | 'FAILURE' — Result status
  - `data` DimensionValueGetDto[] — List of dimension values
    - `id` string, required — Id of the dimension value
    - `dimension` DimensionSubParam, required — Associated dimension
      - `id` string — Id of the dimension
      - `rootId` string — Id of the root dimension
      - `name` string — Name of the dimension
      - `requiredness` 'REQUIRED' | 'NOT_REQUIRED' — Requiredness of the dimension
    - `name` string, required — Name of the dimension value
    - `children` DimensionValueGetDto[], required
  - `cursor` ResponseCursor — Cursor to be used in your subsequent paginated request. Only populated if there are more pages available.
    - `after` string — After cursor - Fetches entities after this cursor. Useful for paging forwards.
    - `before` string — Before cursor - Fetches entities before this cursor. Useful for paging backwards.

## Other responses

- `400` — Bad request
- `401` — Not authenticated
- `403` — Not authorized
- `404` — Endpoint not found
- `500` — Internal server error

---

[API](https://skmtc.net/tight/apis/tight-api.md) · [All operations](https://skmtc.net/tight/apis/tight-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tight/tight-api/revisions/e9f0790a89af/schema)