---
title: "Fetch a single tenant specialty by its ID"
method: GET
path: "/tenant-specialties/{id}"
tags: ["Tenant Specialty"]
---

# Fetch a single tenant specialty by its ID

`GET /tenant-specialties/{id}`

Returns the detail of a single tenant specialty record belonging to the tenant identified by the `tenant-id` header.

**What it does:** Retrieves one tenant specialty by its unique identifier, including its tenant-specific metadata (display name, description, change reason).

**When to use:** Use this when you already hold the `id` of a tenant specialty (for example, from a prior `GET /tenant-specialties` response) and need its detail. Do not use this as a lookup-by-name or lookup-by-classification — use the list or by-classification endpoints for those.

**How to call it:** Supply the required `tenant-id` header and the tenant specialty `id` as a path segment. `id` is an opaque, server-assigned string (assigned as a UUIDv4 by the data layer at creation time); the API does not otherwise constrain its format. Requires the `READ_TENANT_SPECIALTY` permission.

**What you get back:** The tenant specialty's entity content (display name, description, change reason) on 200. Returns 404 if no specialty with the given `id` exists for the supplied `tenant-id`.

## Path parameters

- `id` string, required

## Headers

- `tenant-id` string, required

## Response `200`

The tenant specialty matching the given `id`.

- GetTenantSpecialtyResponse
  - `data` TenantSpecialtySchema — Represents a specialty associated with a tenant.
    - `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

- `401` — Unauthorized - the request is missing a valid JWT.
- `403` — Forbidden - the caller lacks the READ_TENANT_SPECIALTY permission for this tenant.
- `404` — No tenant specialty exists with the given `id` for the supplied `tenant-id`.
- `500` — Internal Server Error - an unexpected error occurred while retrieving the record.

---

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