latestOpenAPI 3.1.02026-08-194237902.5 MB

563848e0ecc0

Practitioner

Update practitioner network associations within a group

Associates the practitioner with one or more networks within a group, creating or updating TenantGroupPractitionerNetwork relationships, following upsert semantics. Use this when adding the practitioner to a network or updating network-specific association data in bulk; the request body must include a groupId to scope the associations, and for associating with a single network with additional group-creation side effects, use POST /practitioners/{id}/networks instead. {id} is the certifyPractitionerId, and the group identified by groupId in the request body must already be associated with the practitioner. Only the networks present in the request are upserted — networks already associated with the practitioner but omitted from the request are left unchanged, not removed. Each entry in networks accepts a required networkId and a free-form networkData object.

put/practitioners/{id}/networks

Path parameters

idstring required

Practitioner ID (certifyPractitionerId)

Headers

tenant-idstring

Request body

groupIdstring required

ID of the group to which the practitioner belongs

Example request

{
  "groupId": "group-123",
  "networks": [
    {
      "networkId": "network-123"
    }
  ]
}

Response

Successfully updated practitioner network associations. The response is a tenantGroupPractitionerId plus a networkAssociations array, each entry containing networkId, tenantGroupPractitionerNetworkId, and status.

tenantGroupPractitionerIdstring

ID of the tenant group practitioner

Example response

{
  "tenantGroupPractitionerId": "tgp-456",
  "networkAssociations": [
    {
      "networkId": "net-123",
      "tenantGroupPractitionerNetworkId": "tgpn-789",
      "status": "updated"
    }
  ]
}