---
title: "Query dimensions"
method: POST
path: "/v6/templates/dimensions/query"
tags: ["Templates"]
---

# Query dimensions

`POST /v6/templates/dimensions/query`

Query dimensions for the authenticated user. Use these to configure any dimensions that your users need to track against. These are what your users will see and can assign transactions to (e.g., Location, Job, Department, etc.). Dimensions can be hierarchical (e.g., Region -> Location -> Building).

## Response `200`

Success

- DimensionPaginatedResponse — Paginated response for dimensions
  - `result` 'SUCCESS' | 'FAILURE' — Result status
  - `data` DimensionGetDto[] — List of dimensions
    - `id` string, required — Id of the dimension
    - `name` string, required — Name of the dimension
    - `status` 'ACTIVE' | 'INACTIVE' | 'REMOVED', required — Status of the dimension
    - `requiredness` 'REQUIRED' | 'NOT_REQUIRED', required — Requiredness of the dimension
    - `child` DimensionGetDto, required — recursive
  - `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)