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

# Get configured lookup values for a column

> Returns a list of `{value, label}` pairs for the specified column and table as configured in `api_model.value_lookups`. Returns 404 when no lookup values are configured for this combination.



## OpenAPI

````yaml https://api.trassets.ai/openapi.json get /meta/{api_table}/values/{column}
openapi: 3.1.0
info:
  title: Trassets Data API
  description: >

    The **Trassets Data API** exposes customer real-estate and market data as a
    REST API —

    objects, units, contracts, meters and bookings, machine-readable and stably
    versioned under `/v1/`.


    ## Quickstart


    ```bash

    export TRASSETS_API_KEY="sk_live_…"

    curl "https://api.trassets.ai/v1/realestates/objects?limit=1" \
      -H "X-API-Key: $TRASSETS_API_KEY"
    ```


    ## Authentication


    Send your API key on every request as the `X-API-Key` header.

    The key determines the customer scope and access tiers.

    Trassets stores only an HMAC-SHA-256 hash — the plaintext key is never shown
    again after creation.


    ## Endpoint Types


    ### Category Endpoints — `/{category}/{api_table}`


    Normalized master data and business queries. Use these for day-to-day
    integrations.


    - **Pagination:** Offset-based (`limit` / `offset` query parameters)

    - **Data character:** Normalized, business-ready data

    - **Use case:** Business queries, dashboards, incremental data fetches


    ### Raw Endpoints — `/raw/{table_name}`


    Full table access for bulk sync and export.


    - **Pagination:** Cursor-based (`cursor` query parameter from `next_cursor`
    in response)

    - **Data character:** Raw source data, unfiltered

    - **Use case:** Bulk sync, full exports, data warehousing


    ## Pagination


    - **Category endpoints**: `X-Total-Count`, `X-Has-More`, `X-Next-Offset`
    response headers.

    - **Raw endpoints**: `next_cursor` in response body. Stable under concurrent
    writes.


    ## Error format


    Errors follow [RFC 7807](https://datatracker.ietf.org/doc/html/rfc7807)
    (`application/problem+json`):

    `type`, `title`, `status`, `detail`, `instance`.


    | Status | Meaning |

    |--------|---------|

    | 400 | Missing required filter |

    | 401 | Invalid API key |

    | 403 | Missing access tier |

    | 404 | Unknown endpoint |

    | 429 | Rate limit (500 req/h per API key; see `Retry-After` header) |

    | 500 | Internal error |


    ## Versioning Policy


    This API will adopt URL versioning (`/v1/`) in an upcoming release. Breaking
    changes will then be

    introduced under a new version prefix. Until versioning is in place, the API
    may receive breaking changes.


    ## Field Glossary


    The following fields appear across multiple endpoints:


    | Field | Description |

    |---|---|

    | `entrance` | Street name and house number, e.g. Musterstrasse 12 |

    | `address` | Comma-separated postal code and city, e.g. 10115, Berlin |

    | `name` | Full name as single field. No separate first/last name available.
    |

    | `floor_area_id` | References floor_area_id in the property_structure table
    |


    ## Request an API key


    API keys are issued via the [Trassets
    Portal](https://portal.api.trassets.ai).
  version: 1.0.0
servers: []
security: []
paths:
  /meta/{api_table}/values/{column}:
    get:
      tags:
        - Meta
      summary: Get configured lookup values for a column
      description: >-
        Returns a list of `{value, label}` pairs for the specified column and
        table as configured in `api_model.value_lookups`. Returns 404 when no
        lookup values are configured for this combination.
      operationId: get_meta_values_meta__api_table__values__column__get
      parameters:
        - name: api_table
          in: path
          required: true
          schema:
            type: string
            title: Api Table
        - name: column
          in: path
          required: true
          schema:
            type: string
            title: Column
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  additionalProperties:
                    type: string
                title: Response Get Meta Values Meta  Api Table  Values  Column  Get
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key

````