These endpoints read or update the Google Business Profile location resource for the team’s selected location. They map to Google’s Business Information API. You need a connected Google Business account with a location already selected (same rule as posts). Base path:Documentation Index
Fetch the complete documentation index at: https://info.bundle.social/llms.txt
Use this file to discover all available pages before exploring further.
/api/v1/misc/google-business
All requests use your usual API key authentication.
Get location
Endpoint:GET /api/v1/misc/google-business/location
Query
| Parameter | Required | Description |
|---|---|---|
teamId | Yes | Team that owns the connected Google Business social account. |
fields | No | Subset of location fields to return. If omitted, a default profile-oriented field list is used (name, title, profile, website, phones, categories, hours fields, address, service area, coordinates, open info, metadata). |
fields accepts comma-separated values or repeated query params, for example fields=name,title or fields=name&fields=title.
Allowed fields values (Google read field paths):
name, languageCode, storeCode, title, phoneNumbers, categories, storefrontAddress, websiteUri, regularHours, specialHours, serviceArea, labels, adWordsLocationExtensions, latlng, openInfo, metadata, profile, relationshipData, moreHours, serviceItems
The response shape follows Google’s API (we pass through the payload). Use it to drive your own UI or to read state before a patch.
Update location
Endpoint:PATCH /api/v1/misc/google-business/location
Only the top-level keys you include in the update payload are sent to Google. Only the fields listed below participate. Send at least one patchable field.
The API automatically determines which provided fields should be updated.
Patchable fields
| Field | Purpose |
|---|---|
title | Display name (max 255 characters). Use null to clear where Google allows. |
profile | Object with description (max 1500 characters) and other Google-supported keys. |
websiteUri | Public website URL. |
phoneNumbers | primaryPhone, additionalPhones[]. |
categories | primaryCategory.name, additionalCategories[].name (Google category resource names). |
storefrontAddress | Structured address (regionCode, postalCode, locality, addressLines, etc.). |
regularHours | Standard weekly hours (periods with open/close days and times). |
specialHours | Exceptions (specialHourPeriods with dates and closed flag). |
moreHours | Named hour sets (for example department-specific hours); each item can include hoursTypeId and periods. |
openInfo | Opening status metadata (Google’s schema). |
serviceArea | Service-area business definition (Google’s schema). |
latlng | latitude and longitude. |
Other body keys
| Field | Description |
|---|---|
validateOnly | If true, Google validates the request without applying the change. |
Useful metadata for feature eligibility
Google location metadata can indicate whether certain feature families are available for this location. In particular:metadata.canModifyServiceListcontrols service-list edit eligibility.metadata.canHaveFoodMenuscontrols food-menu eligibility.
metadata through GET /location before enabling related editing UI.
Example: title, description, and hours (anonymized)
Single update payload with profile copy plus weekly hours, holiday exceptions, and an extra hour type (moreHours). teamId and business copy below are placeholders.
Smaller payloads
You can send partial update payloads, for example onlytitle and websiteUri, or only profile.
Hours only
You may includeregularHours, specialHours, or moreHours in this endpoint, or use the dedicated Hours endpoint when you only change hours and want an explicit fields list for hour sections.
Related
- Google Business Hours for updates that only touch
regularHours,specialHours, ormoreHourswith an explicitfieldslist. - Google Business main guide for posts and analytics.