Add a specialty to the tenant's configuration

Creates a new tenant specialty record, associating a global specialty with the tenant identified by the tenant-id header.

What it does: Persists a tenant-scoped specialty entry. A tenant specialty is distinct from a global specialty — it represents the tenant's adoption of a specialty for use in their credentialing workflows.

When to use: Call this after confirming the referenced global specialty exists. Do not call this if a tenant specialty for the same specialty already exists for the tenant (check with GET /tenant-specialties first) — this operation does not check for an existing record and is not idempotent; submitting the same payload twice creates a second, duplicate record.

How to call it: Supply the required tenant-id header. The request body must include a non-empty specialtyId; a missing or blank specialtyId returns 400 before any other validation occurs. The data field is additionally validated against the TenantSpecialty JSON Schema; schema violations also return 400. Requires the CREATE_TENANT_SPECIALTY permission.

What you get back: On success (201) the created tenant specialty object is returned, including the server-assigned id. No Location header is emitted.