Update a location

Updates a single location. Only the fields present in input are modified; everything you omit keeps its current value. id is the only required field.

Use case: correct a phone number. Send just id and phone to fix contact details without touching address or hours. The response returns the updated location so you can confirm the new values landed.

Use case: publish a full weekly schedule. Send the seven-day businessHours array (as in the sample request) to set open intervals per day. Mark closed days with { "day": "SUNDAY", "type": "CLOSED", "slots": [] }.

Business hours rules.

• Provide all seven days; a partial week is rejected.
• Times use start/end inside each slots entry (e.g. 09:00am, 05:00pm); intervals within a day must not overlap.
• Holiday and event overrides are extra entries with day: "SPECIAL" and a specialDate (YYYY-MM-DD), sent alongside the seven weekday entries, never instead of them.
• Use SPECIAL only in businessHours. moreHours entries have no specialDate field, so a SPECIAL day there carries no date.
• Use moreHours for secondary schedules (delivery, drive-through), keyed by hoursTypeId.

Always send the full week. Publishers expect a complete MONDAY–SUNDAY schedule; send all seven entries whenever you set businessHours, using type: "CLOSED" (with empty slots) for non-operating days rather than omitting the day.

Gotchas.

• The identifier field is id (the Base64 Relay ID returned by every read endpoint).
• On validation failure the call still returns HTTP 200 with success: false and a populated errors array, always check success, not just the status code.

Place action links

placeActionLinks manages a location's Google action buttons (ordering, delivery, takeout, reservation, appointment). The write model is append/upsert, not replace:

• action: "add" (the default): adds a new link, or updates a saved link's uri/isPreferred in place.
• action: "delete": removes a saved link and queues its removal from Google.
• Links you don't reference in the request are left unchanged, omitting a link never removes it.

How a link is matched (for edit/delete): by name if present, otherwise by placeActionType + uri. Include name (from a read endpoint) when you have it, for the most accurate match; a link that hasn't synced to Google yet has no name and is matched by placeActionType + uri.

Valid placeActionType values: APPOINTMENT, ONLINE_APPOINTMENT, DINING_RESERVATION, FOOD_ORDERING, FOOD_DELIVERY, FOOD_TAKEOUT, SHOP_ONLINE. At most one preferred link per type.

Changing a link's URL = remove the old + add the new in the same request:

{  "input": {    "id": "TG9jYXRpb246MTgwMDI4OQ==",    "placeActionLinks": [      { "placeActionType": "FOOD_ORDERING", "uri": "https://order.example.com",     "name": "<link-name-if-synced>", "action": "delete" },      { "placeActionType": "FOOD_ORDERING", "uri": "https://new-order.example.com", "isPreferred": true, "action": "add" }    ]  }}

Right after a write, a link's name and submissionStatus are null; they populate once the link syncs to Google. See the Place Action Links guide for the full flow, including how links discovered directly on Google appear under discoveredPlaceActionLinks.