Skip to main content

Update a facility location (simple CoreLocation fields)

PUT 
/facilities/:certifyFacilityId/locations/:certifyLocationId

Updates allowed CoreLocation fields for a location linked to the facility. Requires consentAcknowledged: true. Includes contacts, office hours, ADA, limitations, isPrimaryLocation (primary indicator), optional userDefinedFields (full replace of that object on CoreLocation data), and optional specialityDetails (same shape as add-location; syncs TenantFacilityLocationSpecialty via replace semantics). When api-layer.facility.location-tfl-contacts.enabled is on, contacts is stored on the facility's TenantFacilityLocation (data.contacts, the list replaces the stored one; [] clears it) instead of CoreLocation, needs no crosswalkId, and is validated with facility-location-tfl-contacts.schema.json (flat objects, string or null values, at most 50 items, an all-blank item is rejected with 400 INVALID_CONTACT). Location name and service address cannot be changed via this API (crosswalk safety). The authenticated user is the actor (updated_by); scoped effective-date PATCH and cascade to group/network denormalized rows are not part of this endpoint.

Request​

Responses​

Location successfully updated