> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xenia.team/llms.txt
> Use this file to discover all available pages before exploring further.

# List Location Attributes

> Lists the workspace's attribute definitions. Array order **is** the display order used in the Xenia UI. Each item carries a `body` whose `type` is the attribute type; the two select types also carry their `options`. Requires the **Public API** and **Location Attributes** workspace features plus `CAN_MANAGE_LOCATIONS`.



## OpenAPI

````yaml GET /api/v1/mgt/enterprise/workspaces/{workspaceId}/location-attributes
openapi: 3.1.0
info:
  title: Xenia Team API - List Location Attributes
  description: >-
    Returns every location-attribute definition for the workspace in display
    order, each with the `external_id` your system previously supplied (or
    `null` if the attribute was created inside Xenia). This is the
    reconciliation read for the Enterprise Location API: call it to map your own
    attribute keys onto Xenia attribute ids.
  version: 1.0.0
servers:
  - url: https://api.xenia.team
security: []
paths:
  /api/v1/mgt/enterprise/workspaces/{workspaceId}/location-attributes:
    get:
      tags:
        - Enterprise Locations
      summary: List Location Attributes
      description: >-
        Lists the workspace's attribute definitions. Array order **is** the
        display order used in the Xenia UI. Each item carries a `body` whose
        `type` is the attribute type; the two select types also carry their
        `options`. Requires the **Public API** and **Location Attributes**
        workspace features plus `CAN_MANAGE_LOCATIONS`.
      parameters:
        - name: workspaceId
          in: path
          required: true
          description: >-
            UUID of the workspace. Must be the workspace your API key is bound
            to.
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Attribute definitions in display order.
          content:
            application/json:
              example:
                data:
                  - id: 1f6c9e0a-2b7d-4d5e-9a11-8c3f5b6d7e88
                    name: Region
                    description: Operational region
                    body:
                      type: single_select
                      options:
                        - id: b0a1c2d3-4e5f-4a6b-8c9d-0e1f2a3b4c5d
                          label: Southwest
                          color: '#7C5CFC'
                        - id: c1b2a3d4-5e6f-4a7b-8c9d-1e2f3a4b5c6d
                          label: Midwest
                          color: '#22B8CF'
                    createdBy: dfea8b8a-5b22-4668-b68d-dc641eb3a101
                    createdAt: '2026-07-02T09:14:22.108Z'
                    externalId: REGION
                  - id: 2a7d0f1b-3c8e-4e6f-9b22-9d4a6c7e8f99
                    name: Drive Thru Lanes
                    description: ''
                    body:
                      type: number
                    createdBy: dfea8b8a-5b22-4668-b68d-dc641eb3a101
                    createdAt: '2026-07-02T09:15:03.412Z'
                    externalId: null
                extra_meta:
                  message: ''
        '401':
          description: >-
            Unauthorized - invalid client credentials, or the `workspaceId` in
            the path is not the workspace your key is bound to (`Client does not
            belong to this workspace`).
        '403':
          description: >-
            Forbidden - route not allow-listed for API keys, the key's user
            lacks `CAN_MANAGE_LOCATIONS`, the workspace lacks the **Public API**
            feature, or Location Attributes is not enabled for the workspace
            (`Location attributes are not enabled for this workspace`).
        '422':
          description: Unprocessable Entity - `workspaceId` is not a UUID.
        '500':
          description: Internal Server Error.
      security:
        - clientKey: []
          clientSecret: []
components:
  securitySchemes:
    clientKey:
      type: apiKey
      in: header
      name: x-client-key
    clientSecret:
      type: apiKey
      in: header
      name: x-client-secret

````