563848e0ecc0
Associate a facility with a network
Associates a facility with a network following the roster ingestion pattern. The network must belong to a group (groupId provided in request body). If the facility is not associated with the group, the group association will also be created simultaneously. Validates that the network belongs to the specified group before creating the association. Supports three request shapes, each with different conflict behavior: (1) legacy single networkId — always upserts the TenantGroupFacilityNetwork relationship with no pre-check, silently updating an existing association rather than rejecting it; (2) bulk networkIds or (3) grouped networkAssociations — both explicitly check for an existing active association per facility-network and per facility-location-network pair first, and return 409 Conflict if one already exists rather than silently updating it. Choose the bulk/grouped shapes when you need to detect pre-existing associations instead of upserting over them.
Path parameters
ID of the facility (certify facility ID)
Headers
Request body
Example request
{
"groupId": "group-123",
"networkId": "network-456",
"networkIds": [
"network-456",
"network-789"
],
"facilityLocationIds": [
"loc-1",
"loc-2"
],
"networkEffectiveDate": "2026-04-01",
"groupEffectiveDate": "2026-03-15",
"networkAssociations": [
{
"networkId": "network-456",
"effectiveDate": "2026-04-01"
}
]
}Response
Successfully associated facility with network
Example response
{
"tenantGroupFacilityId": "tgf-456",
"tenantGroupFacilityNetworkId": "tgfn-789",
"networkId": "net-123",
"status": "created",
"facilityNetworkCount": 2,
"locationNetworkCount": 4,
"associations": [
{
"networkId": "net-123",
"tenantGroupFacilityNetworkId": "tgfn-789",
"tenantGroupLocationFacilityNetworkIds": [
"tglfn-1"
]
}
]
}