---
title: "Associate a provider to a specialty"
method: POST
path: "/specialties/{specialtyId}/providers/{providerId}"
tags: ["specialties"]
---

# Associate a provider to a specialty

`POST /specialties/{specialtyId}/providers/{providerId}`

## Path parameters

- `specialtyId` string, required
- `providerId` string, required

## Response `200`

Specialty Resource

- SpecialtyResourceResponse — Represents an association between a specialty and a specific resource such as an appointment type, provider, or facility. It is used to determine which providers, facilities, or appointment types belong to a given medical specialty.
  - `_id` string — Luma's internal ID of an object.
  - `user` string — The ID of the root account user.
  - `deleted` 0 | 1 — Flag for logical deletion where 1 means deleted.
  - `createdBy` string — The ID of the user who created this object.
  - `updatedBy` string — The ID of the user who updated this object.
  - `deletedBy` string — The ID of the user who deleted this object.
  - `createdAt` string, date-time — The date/time when this object was created.
  - `updatedAt` string, date-time — The date/time when this object was updated.
  - `deletedAt` string, date-time — The date/time when this object was deleted.
  - `specialty` string
  - `refId` string
  - `ref` 'appointmentType' | 'facility' | 'provider'

## Other responses

- `401` — Not authenticated
- `403` — Access token does not have the required scope

---

[API](https://skmtc.net/lumahealth/apis/rest-service.md) · [All operations](https://skmtc.net/lumahealth/apis/rest-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lumahealth/rest-service/revisions/d3c75c2a2f1d/schema)