563848e0ecc0
Update a facility and its tenant association
Updates the CoreFacility identified by the path certifyFacilityId and its TenantFacility association for the tenant (update path). Use this when the certifyFacilityId is already known; use POST /facilities instead to create a new facility. Stored identity fields not present in the payload are merged in before validation, then the same crosswalk identity used at create time is re-resolved and updated — retrying this call with the same payload is safe and updates the same rows (idempotent). Request body is validated against the same facility-upsert JSON Schema and tenant-specific rules used by POST /facilities. Returns HTTP 201 (not 200) on success — this matches the create endpoint's status code by historical convention rather than by REST semantics for an update; treat any 2xx as success rather than branching on the exact code. Response body is the same ID map as create (crosswalkId, corefacilityId, tenantfacilityId, etc.), not the full facility object. See POST /facilities for the create path.
Path parameters
Facility ID
Headers
Tenant ID
Request body
Example request
{
"facilityId": "cf_abc123",
"name": "Acme Medical Center",
"npi": "1234567890",
"tin": "123456789",
"ncpdpId": "1234567",
"facilityType": "Hospital",
"facilityEffectiveDate": "2024-01-01",
"attestationDate": "2024-01-01",
"effectiveDate": "2024-01-01",
"serviceAddress": {
"state": "CA"
},
"officeAddress": {
"state": "CA"
},
"billingAddress": {
"state": "CA"
},
"mailingAddress": {
"state": "CA"
},
"irsAddress": {
"state": "CA"
}
}Response
Facility successfully updated
Example response
{
"crosswalkId": "1234567890-123456789",
"corefacilityId": "cf_abc123",
"tenantfacilityId": "tf_abc123",
"facilityentityaddressId": "fea_abc123"
}