Google Business Location Info
Read and edit the business information of a connected Google Business Profile location:
name, store code, description, address, service area, regular, special and "more" hours,
phone numbers, website, categories, open status, labels, ad phone, coordinates and chain
relations. You can also review the changes Google suggests, see the moderation status of
each field, and list locations (creating and deleting them is not generally available yet).
Both endpoints call Google's Business Information API in real time and refresh the stored
access token automatically. The Google Business connection already includes the required
permission (business.manage), so no reconnection is needed.
- Authentication: API Key —
Authorization: Apikey <YOUR_API_KEY>
The location is resolved in this order: location_id in the request → the location
pinned to the profile → the account's only location.
If the account has several locations and none of those applies, the API answers
400 location_required with the list of available_locations. List them with
Get Google Business Locations.
Read location info
- Method:
GET - Endpoint:
/api/uploadposts/google-business/location-info
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | Yes | The profile username that owns the connected Google Business account. |
location_id | string | No | locations/123, a bare 123, or accounts/456/locations/123. See "Which location?" above. |
read_mask | string | No | Comma-separated Location fields to return (e.g. name,title,serviceItems). Default: all of them. |
Example Request
curl 'https://api.upload-post.com/api/uploadposts/google-business/location-info?user=agent-paris' \
-H 'Authorization: Apikey YOUR_API_KEY'
Successful Response (200 OK)
{
"success": true,
"location_id": "locations/111",
"info": {
"location_id": "locations/111",
"title": "Agence Dupont",
"description": "Agence immobilière à Paris 11e.",
"phone": "+33 1 23 45 67 89",
"additional_phones": [],
"website": "https://dupont.example",
"primary_category": "categories/gcid:real_estate_agency",
"primary_category_name": "Real estate agency",
"additional_categories": ["categories/gcid:property_management_company"],
"regular_hours": [
{ "day": "MONDAY", "open": "09:00", "close": "18:30" }
],
"special_hours": [
{ "date": "2026-12-25", "closed": true },
{ "date": "2026-12-31", "open": "10:00", "close": "14:00", "end_date": "2026-12-31" }
],
"address": { "locality": "Paris", "postalCode": "75011", "regionCode": "FR", "addressLines": ["1 rue Exemple"] },
"open_status": "OPEN",
"opening_date": "2015-03",
"store_code": "PAR-11",
"labels": ["north"],
"ad_phone": null,
"service_area": null,
"more_hours": [{ "hours_type_id": "DELIVERY", "periods": 5 }],
"parent_chain": null,
"service_items": 3,
"maps_uri": "https://maps.google.com/?cid=1",
"place_id": "ChIJ...",
"has_pending_edits": false,
"has_google_updated": false,
"has_voice_of_merchant": true,
"can_delete": true
},
"location": { "name": "locations/111", "title": "Agence Dupont", "...": "raw Google Location resource" }
}
info is a flat, readable view; location is Google's raw
Location resource.
Update location info
Only the fields you send are changed: the API builds Google's updateMask from them.
edit_mode decides how the body is read:
legacy(default) — the endpoint works exactly as it always has. Onlydescription,website(orwebsite_uri),phone(orprimary_phone),additional_phones,regular_hours,special_hours,primary_categoryandadditional_categoriesare used; an empty value (""or[]) clears the field and noconfirmis needed. Every other key (title,address,labels,store_code,open_status,dry_run,confirm,include_edit_status...) is ignored and listed inignored_fields.validate_only: truestill asks Google to validate without applying anything. The answer hassuccess,location_id,validate_only,update_mask,ignored_fields,infoandlocation.strict(send"edit_mode": "strict") — every field in the table below. An empty value ("",[]or{}) leaves the field as it is (it is listed inunchanged_fields); to clear a field sendnull.title,phone,primary_categoryandopen_statuscannot be cleared. Risky changes needconfirm,dry_runvalidates without applying, and the answer addsdry_run,unchanged_fields,edit_mode,has_pending_editsandedit_status.
Any other edit_mode value is refused with 400 invalid_edit_mode.
- Method:
PATCH(also acceptsPOST) - Endpoint:
/api/uploadposts/google-business/location-info
Body Parameters (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
user | string | Yes | Profile username. |
location_id | string | No | Location to edit (see "Which location?"). |
edit_mode | string | No | legacy (default) or strict. See above. |
validate_only | boolean | No | Both modes: Google validates the change without applying it. |
dry_run | boolean | No | Strict only. true asks Google to validate the change without applying it (Google's validateOnly). Recommended before any real edit. Ignored in legacy mode (the edit is applied). |
confirm | boolean | Depends | Strict only. Required (true) to change title, address, primary_category, phone or to set open_status to a closed value. Not needed with dry_run. |
include_edit_status | boolean | No | Strict only. Default true: after a real edit the answer includes edit_status. false skips it. |
title | string | No | Strict only. Business name as customers know it. Needs confirm. |
store_code | string | No | Strict only. Your own id for the location (unique in the account). null removes it. |
description | string | No | Business description, max 750 characters. |
website | string | No | Absolute http(s) URL. null removes it. |
phone | string | No | Primary phone, e.g. +33 1 23 45 67 89. |
additional_phones | array of string | No | Up to 2 extra phone numbers. null removes them. |
regular_hours | array | No | Weekly hours: [{"day": "MONDAY", "open": "09:00", "close": "18:00"}]. day may also be a list (["MONDAY", "TUESDAY"]). Several entries for the same day = split hours (e.g. lunch break). A close earlier than open closes the next day; "close": "24:00" = until midnight. null clears the hours. |
special_hours | array | No | Exceptions: [{"date": "2026-12-25", "closed": true}] or [{"date": "2026-12-31", "open": "10:00", "close": "14:00"}]. Optional end_date. null clears them. |
primary_category | string | No | Google category id, e.g. gcid:real_estate_agency (or categories/gcid:...). |
additional_categories | array of string | No | Up to 9 extra category ids. null removes them. |
address | object / null | No | Strict only. Storefront address: region_code (required, e.g. ES), address_lines (max 5), locality, postal_code, administrative_area, sublocality, organization, recipients, language_code, sorting_code. Google's camelCase keys are accepted too. null removes it (service-area businesses). Needs confirm. |
service_area | object / null | No | Strict only. {"business_type": "CUSTOMER_LOCATION_ONLY" | "CUSTOMER_AND_BUSINESS_LOCATION", "places": [{"place_id": "...", "place_name": "Madrid"}]} (max 20 places). null removes it. |
more_hours | array | No | Strict only. Hours for departments or services: [{"hours_type_id": "DELIVERY", "hours": [{"day": "MONDAY", "open": "12:00", "close": "16:00"}]}]. Valid hours_type_id values come from categories batch with view=FULL. null clears them. |
open_status | string | No | Strict only. OPEN, CLOSED_TEMPORARILY or CLOSED_PERMANENTLY. Closed values need confirm. |
opening_date | string | No | Strict only. YYYY-MM-DD or YYYY-MM; in the past or at most one year ahead. null removes it. |
labels | array of string | No | Strict only. Private labels (1-255 characters each), never shown to customers. null clears them. |
ad_phone | string | No | Strict only. Phone shown in Google Ads location extensions instead of the primary one. null removes it. |
latlng | object / null | No | Strict only. {"latitude": 40.41, "longitude": -3.70}. Google only accepts it from approved clients; otherwise it answers with a validation error. |
relationship_data | object / null | No | Strict only. {"parent_chain": "chains/...", "parent_location": {"place_id": "...", "relation_type": "DEPARTMENT_OF"}, "children_locations": [...]}. Replaces all relations. |
parent_chain | string | No | Strict only. Shortcut to set only the chain (chains/..., see chains); null removes it. The other relations are kept. |
regular_hours and special_hours also accept Google's native objects
({"periods": [...]} and {"specialHourPeriods": [...]}). When you send only
phone or only additional_phones (same for the two category fields, for open_status /
opening_date and for parent_chain), the other half keeps its current value (in both modes): Google
replaces those fields as one block, so the API reads that one field first. The rest of the
location is never read or rewritten.
A new name, address, primary category or primary phone, or a closed status, can make Google
ask for verification again, hold the change under review, or suspend the listing if it looks
wrong. In strict mode those changes need "confirm": true. Try them first with "dry_run": true: Google
validates the change and nothing is applied. Google allows 10 edits per minute per
location; above that the API answers 429 location_edit_rate_limited.
Example Request
curl -X PATCH https://api.upload-post.com/api/uploadposts/google-business/location-info \
-H 'Authorization: Apikey YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"user": "agent-paris",
"edit_mode": "strict",
"description": "Agence immobilière à Paris 11e : vente, location et gestion.",
"website": "https://dupont.example",
"regular_hours": [
{ "day": ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY"], "open": "09:00", "close": "12:30" },
{ "day": ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY"], "open": "14:00", "close": "19:00" },
{ "day": "SATURDAY", "open": "10:00", "close": "13:00" }
],
"special_hours": [{ "date": "2026-12-25", "closed": true }]
}'
Successful Response (200 OK)
{
"success": true,
"location_id": "locations/111",
"validate_only": false,
"dry_run": false,
"update_mask": ["profile", "websiteUri", "regularHours", "specialHours"],
"ignored_fields": [],
"unchanged_fields": [],
"edit_mode": "strict",
"has_pending_edits": true,
"info": { "...": "same shape as the GET response" },
"location": { "...": "raw Google Location after the update" },
"edit_status": {
"fields": {
"regularHours": { "stage": "PENDING", "source": "SOURCE_API", "update_time": "2026-11-14T10:00:00Z", "rejection_reason": null }
},
"pending_review": true,
"rejected": false,
"experimental": true,
"channel": "v1alpha"
}
}
ignored_fields lists keys of your body that are not used in the chosen mode (they are not sent to Google).
edit_status is Google's moderation stage for each edited field: PENDING (under review),
ACCEPTED (live), REJECTED (see rejection_reason), UPDATED_BY_GOOGLE or DRAFT (the
location is not verified yet). It comes from an experimental Google API; if Google does not
return it, the edit still succeeds and the answer carries a warnings entry. Check it later
with extended location info.
Changes suggested by Google
Google may change a listing from user reports or other sources. See what differs:
- Method:
GET - Endpoint:
/api/uploadposts/google-business/location-info/google-updated?user=X[&location_id=][&read_mask=]
{
"success": true,
"location_id": "locations/111",
"has_google_updates": true,
"diff_fields": ["regularHours", "websiteUri"],
"pending_fields": [],
"location": { "...": "the listing as customers see it" },
"diffMask": "regularHours,websiteUri"
}
Accept or reject them field by field:
- Method:
POST - Endpoint:
/api/uploadposts/google-business/location-info/google-updates
| Name | Type | Required | Description |
|---|---|---|---|
user | string | Yes | Profile username. |
location_id | string | No | Location (see "Which location?"). |
decision | string | Yes | accept (keep Google's value) or reject (send yours again). |
fields | array of string | Yes | Fields from diff_fields, e.g. ["regularHours"]. |
dry_run | boolean | No | Validate only. |
confirm | boolean | Depends | Required for title, storefrontAddress, categories, phoneNumbers and openInfo. |
Only the fields you name are read and written. A field without a pending Google change
answers 409 no_google_update.
Edit status of each field (experimental)
- Method:
GET - Endpoint:
/api/uploadposts/google-business/location-info/extended?user=X[&location_id=]
Returns what you submitted (locationProvidedByMerchant), what customers see
(locationSeenByConsumers) and, per field, the moderation stage (edit_status), plus
pending_fields and rejected_fields. Built on an experimental Google API: the answer
carries "experimental": true and Google may change it with 30 days' notice.
List locations with filters
- Method:
GET - Endpoint:
/api/uploadposts/google-business/locations/list
| Parameter | Description |
|---|---|
user | Profile username. |
account | Google account (accounts/123 or 123). Default: the account connected to the profile. |
filter | Google's filter syntax, e.g. title="Bakery" (Google's guide). |
order_by | title and/or store_code, optionally with desc. |
read_mask | Fields to return (default name,title,storeCode,storefrontAddress,categories,openInfo,metadata). |
page_size / page_token | 1-100 (default 100) and the next_page_token of the previous page. |
Create a location
Creating and deleting locations is not generally available yet: both endpoints answer
503 gbp_feature_disabled before anything else is checked.
- Method:
POST - Endpoint:
/api/uploadposts/google-business/locations/create
Send either location (a Google Location object) or the same friendly fields as the update
above, plus language_code (BCP 47, cannot be changed later). title, primary_category
and language_code are required. Also: account (default: the connected one),
request_id (up to 50 letters, digits, - or _; generated if missing), dry_run and
confirm (required for a real creation). The request_id comes back in every answer, errors
included. Upload-Post never retries a creation on its own: if Google does not confirm it
(502 google_result_unknown), repeat the request with the same request_id, and Google
never creates the location twice. Search first with
Google locations search
to avoid duplicates. Google limits how many locations can be created per day; above that
the API answers 429 daily_limit_reached or 429 google_daily_quota_exhausted (and
503 gbp_quota_guard_unavailable if those limits cannot be checked right now). A new
location has to be verified before it shows on Maps.
Delete a location
- Method:
DELETE(alsoPOST) - Endpoint:
/api/uploadposts/google-business/locations/delete - Body:
{"user": "...", "location_id": "locations/111", "confirm": true}
Not generally available yet (see the note above). Irreversible. If Google does not allow deleting it through the API, the answer is
409 location_cannot_be_deleted: delete it from business.google.com.
Errors
Every error carries success: false, code, the same value in error_code, and an error message.
| Status | code | Meaning |
|---|---|---|
| 400 | invalid_json | The body is not a valid JSON object. |
| 400 | invalid_edit_mode | edit_mode is not legacy or strict. |
| 400 | user_required | Missing or invalid user. |
| 404 | profile_not_found | The profile does not exist. |
| 400 | google_business_not_connected | The profile has no Google Business account connected. |
| 401 | google_business_reconnect_required | The Google connection expired; reconnect Google Business. |
| 400 | location_required | Several locations and none selected; see available_locations. |
| 400 | invalid_location_id | location_id is not locations/{id}, a bare numeric id or accounts/{a}/locations/{id} (checked before calling Google). |
| 404 | no_locations / location_not_found | No location for the account / Google does not know the location. |
| 400 | invalid_field | A field failed validation; see errors. |
| 400 | no_fields | Nothing to update was sent. |
| 400 | confirmation_required | A risky change or a deletion was sent without "confirm": true. |
| 400 | invalid_read_mask / invalid_order_by / invalid_filter | A list parameter is not valid. |
| 400 | google_precondition_failed | Google cannot do this for this location yet (e.g. not verified). |
| 409 | no_google_update / location_cannot_be_deleted | See the sections above. |
| 429 | location_edit_rate_limited | More than 10 edits per minute on the same location; see retry_after_seconds. |
| 503 | gbp_feature_disabled | The action is not available (creating and deleting locations are not generally available yet). |
| 400 | google_validation_error | Google rejected the change; see google_error (with fieldViolations). |
| 403 | google_business_permission_denied | The connected Google user cannot edit this location. |
| 429 | google_rate_limited | Google rate limit; retry later. |
| 502 | google_api_error | Google error on their side. |
| 502 | google_unreachable / google_result_unknown | Google could not be reached / did not confirm a change: check before repeating it. |
Notes:
- Google may review some edits before they appear publicly on Search and Maps.
- Category ids are Google's
gcid:values (search them); changing the primary category may trigger re-verification of the business.- Attributes (Wi-Fi, payments, WhatsApp link...) are edited with Google Business Attributes; services and menus with Menus and Services.