Locations
Update with PUT
The existing update contract, retained for supported integrations.
PUT
Requires
Returns
location:update and project API access. name and city are required on each request; a street address is optional.
For a change that should preserve all omitted choices, use PATCH.
string
required
The public project ID.
string
required
The public location ID.
string
required
Location name.
string
required
Location city.
string
Phone number.
200 and the location resource. Field descriptions are on Create a location.
Existing PUT behavior
- Omitted scalar values generally remain saved; PUT does not have PATCH’s preserve-all-omissions contract.
- Supplied
fieldsandcallsToActionobjects replace their respective attachments. Their omitted keys are removed; an empty object clears those attachments. - Supplied
filtersreplaces the filter list; an empty list clears it. An omitted filter list is preserved. - Omitted marker and location-type selections use the project’s defaults.
- Omitted hours, null hours, and
{}leave any existing hours unchanged. A nonempty hours object must include all seven days; it replaces the saved week. - Use PATCH for
hours:nullclearing or partial weekdays. - PUT can geocode synchronously when either coordinate is missing or zero; it retains the older behavior described under addresses and coordinates.
401, 403, 404, 422, 429. Invalid input saves no part of the location update. See errors.