# Update provider specialty

Update specialty details with optional sub-specialties

Endpoint: PATCH /v2/provider/{providerId}/specialties/{specialtyId}
Security: BearerAuth

## Header parameters:

  - `organization-id` (string)

## Path parameters:

  - `providerId` (string, required)

  - `specialtyId` (string, required)

## Request fields (application/json):

  - `specialty_nucc_taxonomy_code` (string, required)
    Nucc taxonomy code tied to this specialty

  - `name` (string, required)
    Name of specialty tied to this taxonomy code

  - `is_primary` (boolean, required)
    Whether this specialty is the provider’s primary speciality; they can only have 1 primary specialty

  - `sub_specialties` (array, required)
    Provider’s subspecialties that are tied to this specialty [array] (if there are no subspecialties, include the field, but just put empty [])

  - `sub_specialties.specialty_nucc_taxonomy_code` (string, required)
    Nucc taxonomy code tied to this subspecialty

  - `sub_specialties.name` (string, required)
    Name of subspecialty tied to this taxonomy code


## Response 204 fields

## Response 400 fields

## Response 401 fields

## Response 403 fields

## Response 404 fields