---
title: "List all configuration entries for a tenant"
method: GET
path: "/tenant-configurations"
tags: ["Tenant Configuration"]
---

# List all configuration entries for a tenant

`GET /tenant-configurations`

Returns every stored configuration record for the tenant identified by the required `tenant-id` header. The response is a `TenantConfigurationListResponseDto` envelope containing a `data` array of `TenantConfigurationItemDto` objects and a `totalCount` field.

Use this endpoint when you need all configuration types at once. To retrieve a single type, use `GET /tenant-configurations/by-configuration-type/{configurationTypeId}` instead; that sibling path serves results from a server-side cache, whereas this endpoint does not read from or populate that cache.

This endpoint returns only persisted records. Unlike the by-type endpoint, it does not synthesize a default `tenant-timezone-config` (America/New_York) when none is stored, so tenants without a persisted timezone record will not have one in the returned list.

Preconditions: the `tenant-id` header must be present; omitting it returns 400.

This is a read-only operation with no side effects.

## Headers

- `tenant-id` string, required

## Response `200`

Envelope containing every stored configuration record for the tenant and the total count.

- TenantConfigurationListResponseDto — List of all tenant configurations for a tenant
  - `data` TenantConfigurationItemDto[] — List of tenant configurations
    - `id` string — Unique identifier for the configuration
    - `tenantId` string — Tenant ID this configuration belongs to
    - `namespace` string — Namespace for the configuration
    - `configurationTypeId` string — Type identifier for the configuration
    - `configuration` unknown
    - `updatedAt` string, date-time
    - `createdAt` string, date-time
  - `totalCount` integer — Total number of tenant configurations

## Other responses

- `400` — Request rejected because the required `tenant-id` header is missing or blank. Supply a non-empty `tenant-id` header and retry.
- `401` — Authentication token is missing, expired, or invalid. Obtain a valid JWT and retry.
- `500` — An unexpected error occurred while reading configurations from the data store. The response body is a bare `{"error": "..."}` object, not the structured `ApiError` shape used elsewhere in this API. The request was not fulfilled; retry after a short delay and escalate if it persists.
- `502` — The downstream data store (DAL) returned a server error (5xx) while reading configurations. Retry after a short delay and escalate if it persists.
- `503` — Unable to connect to the downstream data store (network/connectivity failure). Retry after a short delay.

---

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