---
title: "Create a NUCC taxonomy specialty entry"
method: POST
path: "/specialties/nucc"
tags: ["Specialty"]
---

# Create a NUCC taxonomy specialty entry

`POST /specialties/nucc`

Creates a new NUCC (National Uniform Claim Committee) taxonomy specialty entry for the tenant. NUCC specialties represent standardized provider taxonomy codes used in claim and credentialing workflows, and are distinct from the general medical specialties managed via `POST /specialties`.

**When to use:** Use this endpoint when you need to add a tenant-level NUCC taxonomy specialty record. For general (non-NUCC) specialties use `POST /specialties`.

**Preconditions:** Requires the `CREATE_SPECIALTY` permission. The `tenant-id` header must be supplied. The request body contains only a `data` object, which is validated against the NuccSpecialty JSON Schema before storage — a schema violation returns 400. The `createdBy` and `updatedBy` audit fields are both automatically set to the authenticated user's ID from the JWT at creation time; they are not accepted in the request body.

**Result:** Returns 201 with the created NUCC specialty object, including the server-assigned `id` (a UUID-format string generated by the data layer). Not idempotent — repeat calls create duplicate entries. 400 is returned for either JSON Schema validation failure or a downstream data-layer error.

## Headers

- `tenant-id` string, required

## Request body

- CreateNuccSpecialtyRequest
  - `data` NuccSpecialtySchema — Represents the NUCC specialty information options for a healthcare provider.
    - `classification` string, required — The classification of the NUCC specialty
    - `specialization` string, nullable — The specific specialization within the NUCC classification
    - `category` 'Individual' | 'Non-Individual', required — Allowed categories for NUCC Specialty
    - `displayName` string, required — The human-readable name of the NUCC specialty
    - `specialtyNuccTaxonomyCode` string, required — The NUCC taxonomy code associated with the specialty

## Response `201`

The NUCC specialty entry was created; the response body is the new record with its server-assigned ID.

- object
  - `id` string — Server-assigned NUCC specialty identifier.
  - `createdAt` string, date — Date the record was created.
  - `createdBy` string — ID of the user who created the record.
  - `updatedAt` string, date — Date the record was last updated.
  - `updatedBy` string — ID of the user who last updated the record.
  - `data` NuccSpecialtySchema — Represents the NUCC specialty information options for a healthcare provider.
    - `classification` string, required — The classification of the NUCC specialty
    - `specialization` string, nullable — The specific specialization within the NUCC classification
    - `category` 'Individual' | 'Non-Individual', required — Allowed categories for NUCC Specialty
    - `displayName` string, required — The human-readable name of the NUCC specialty
    - `specialtyNuccTaxonomyCode` string, required — The NUCC taxonomy code associated with the specialty

## Other responses

- `400` — The request body failed NuccSpecialty JSON Schema validation, or a downstream data-layer error occurred.
- `401` — Unauthorized - Authentication required
- `403` — Forbidden - User does not have required permissions
- `500` — Internal Server Error - An unexpected error occurred

---

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