---
title: "List specialties configured for the tenant"
method: GET
path: "/tenant-specialties"
tags: ["Tenant Specialty"]
---

# List specialties configured for the tenant

`GET /tenant-specialties`

Returns the specialties that have been configured for the tenant identified by the `tenant-id` header.

**What it does:** Fetches a page of tenant specialty records — each record links a global specialty definition to this tenant and may carry tenant-specific metadata.

**When to use:** Use this endpoint to display or enumerate specialties active for a tenant. To narrow results to a specific classification taxonomy, use `GET /tenant-specialties/by-classification` instead.

**How to call it:** Supply the required `tenant-id` header. The `name` query parameter is accepted but is not currently forwarded to the data layer — it has no effect on the returned results (tracked as a known limitation, not fixed by this documentation change). Pagination is not exposed: every call returns a fixed first page of up to 10 records regardless of how many tenant specialties exist for the tenant.

**What you get back:** A JSON object containing a `data` array of tenant specialty objects and a `totalCount` integer reflecting the full count before pagination. Requires the `READ_TENANT_SPECIALTY` permission.

## Query parameters

- `name` string

## Headers

- `tenant-id` string, required

## Response `200`

The (fixed first page of the) tenant's specialties, plus the total count before pagination.

- GetTenantSpecialtiesResponse
  - `totalCount` integer — Total number of tenant specialty records matching the query, before pagination. Note the underlying list endpoints return at most a single fixed page of results, so this may exceed the number of items in `data`.
  - `data` TenantSpecialtySchema[] — The page of matching tenant specialty records.
    - `displayName` string, required — Display name for the specialty.
    - `description` string — Detailed description of the specialty.
    - `changeReason` string — Reason for any change to the specialty.

## Other responses

- `400` — Missing or invalid `tenant-id` header.
- `401` — Unauthorized - the request is missing a valid JWT.
- `403` — Forbidden - the caller lacks the READ_TENANT_SPECIALTY permission for this tenant.
- `500` — Internal Server Error - an unexpected error occurred while retrieving the list.

---

[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)