Read and patch Google Business Profile location data: title, profile description, website, phones, categories, address, hours, service area, coordinates, and metadata.
Last updated: May 2026
Read location data with explicit Google field paths
Patch only the profile fields included in your payload
Useful for multi-location admin panels, franchise tooling, local SaaS products, and agency dashboards
This workflow reads and updates the core Google Business Profile location resource. It covers profile-facing data such as display name, description, website URL, phone numbers, categories, storefront address, service area, coordinates, open status, hours-related fields, and Google metadata.
Use GET /api/v1/misc/google-business/location to read a selected location and PATCH /api/v1/misc/google-business/location to update it. GET accepts fields as comma-separated or repeated query params. PATCH sends only the top-level keys included in your update payload.
Patchable fields include title, profile, websiteUri, phoneNumbers, categories, storefrontAddress, regularHours, specialHours, moreHours, openInfo, serviceArea, and latlng. Use validateOnly when you want Google to validate the payload before applying it.
Google Business Profile fields are location-specific and often category-dependent. A field that works for one branch may be read-only, unsupported, invalid, or risky for another branch. Your UI should read current state before patching and surface Google validation messages clearly.
The location metadata can tell you whether feature families are available. For example, canModifyServiceList controls whether service list editing should be enabled, and canHaveFoodMenus controls whether food menus should be shown in the product. Use metadata to avoid fake buttons that lead to rejected API calls.
bundle.social keeps location profile management next to posts, reviews, media, account operations, and analytics. That makes it easier to build one operational dashboard for local profiles instead of duct-taping a separate Google Business Profile integration onto your app.
Platform APIs change. Use these links to confirm current error behavior and field support.
No. This endpoint supports the location fields exposed by the bundle.social Google Business Profile location workflow. Some Google fields are read-only, eligibility-based, or managed through dedicated endpoints such as hours, attributes, service lists, food menus, media, posts, and reviews.
Yes, the location endpoint can include hours-related fields. Use the dedicated hours endpoint when you only want to change regularHours, specialHours, or moreHours with explicit hour field selection.
Because Google feature availability can vary by location. Metadata helps your UI decide whether service lists or food menus should be editable before the user wastes time on changes Google will reject.
Related
Focused updates for regular, special, and extra hours.
Manage category-dependent facts and amenities.
Core Google Business Profile API landing page.
Troubleshoot Google Business Profile validation, permissions, field, quota, and retry failures.
Publish posts, events, and offers across business locations.
Monitor reviews and send owner replies from one workflow.
Build with less platform drag