Set one member's Specialties to Cred, under its own tenant
PUT/api/v1/anchor-groups/:anchorGroupId/shared-credentialing-workflows/:id/members/specialties-to-credential
Sets the specialties one member workflow of this shared credentialing run credentials, under the tenant named in the body. The body carries the member's desired list; the server adds what is new and removes what is gone through the shared Specialties section's own writes, for that tenant only. A removed specialty another tenant also holds is narrowed off this tenant; one only this tenant holds is deleted. The section writes need credentialing-workflow:details:create (to add) and details:delete (to remove) on every member tenant. Refuses a member outside the States to Cred editable statuses (PSV Complete and later, Withdrawn or Cancelled). A specialty is matched by taxonomy code, else by name; primarySpecialty, subspecialty and type only apply to a newly added specialty, and a specialty the member already holds is left as it is. Writes run removals first, one at a time, so a refusal part-way leaves the earlier writes in place and a retry recomputes the difference. One member per call. An empty array removes them all.
Request
Responses
- 204
- 400
- 403
- 404
- 409
- 422
- 500
The member's Specialties to Cred are as sent
Missing shared run id, a missing or blank workflowId or tenantId, an absent specialties list, an entry without a specialty, an invalid record, or a member whose status does not allow editing (WORKFLOW_NOT_EDITABLE)
The caller may not update credentialing workflows in the body tenant, or lacks the section permission on a member tenant; a missing details:create is found only when the add runs, so earlier removals stand and a retry recomputes the difference
The workflow and tenant are not a member of this shared run in this anchor group
WORKFLOW_CONFLICT or STALE_RECORD: a concurrent writer changed the records; safe to retry
SPECIALTY_RECORD_COLLISION: two specialties differ only by taxonomy code and cannot be changed together (send them in separate calls), or another section refusal such as ALL_TENANTS_LOCKED
The write failed