Google: Business Information API v1alpha shows edit status and rejection reasons for locations and attributes

Business Information API v1alpha shows edit status and rejection reasons for locations and attributes

Announced2 Nov 2026

Effective2 Nov 2026

StatusTook effect 11 days ago

What changed

Google's Latest updates page for November 2, 2026 adds two v1alpha methods to the My Business Business Information API: locations.getExtended and locations.attributes.getExtended. They return the merchant-provided values, the values consumers see on Search and Maps, and per-field edit metadata: lifecycle stage, source (API or UI), last edit time and, for rejected edits, the policy violation reason.

What it means

Listing management tools can see whether an edit they sent is pending, accepted, rejected for a named policy reason, or overridden by Google, in one call per location.

Who is affected

Developers of tools that update Google Business Profile details (hours, phone, website, attributes) for businesses and agencies.

What to do by 2 Nov 2026

Try locations.getExtended and locations.attributes.getExtended on v1alpha to show edit status, and stop resubmitting identical edits while one is pending. Alpha methods may change.

What this means for you

When you change your opening hours or phone number on Google, Google checks the change before showing it. Until now, apps could not easily tell you whether Google accepted it. Now they can ask: is the change waiting, approved, turned down, or did Google change it itself? If it was turned down, the app can also show why. This is an early test version.

The details

New methods (v1alpha, Business Information API):
- GET https://mybusinessbusinessinformation.googleapis.com/v1alpha/locations/{locationId}:getExtended returns an ExtendedLocation with locationProvidedByMerchant, locationSeenByConsumers and extendedFieldData. Unlike locations.get, it needs no readMask.
- GET .../v1alpha/locations/{locationId}/attributes:getExtended returns ExtendedAttributes, pairing attributeProvidedByMerchant and attributeSeenByConsumers with extendedFieldData for each attribute.
extendedFieldData is keyed by top-level Location field names in snake_case (for example title, phone_numbers, regular_hours) and holds lastEditLifecycleStage, rejectionReason (a PolicyViolation, set when the stage is rejected), updateTime and source (SOURCE_API or SOURCE_UI).
Lifecycle stages: EDIT_LIFECYCLE_STAGE_ACCEPTED, _PENDING, _REJECTED, _UPDATED_BY_GOOGLE, _DRAFT (for example on an unverified location) and _UNSPECIFIED.
Guidance from Google: while an edit is pending, "Don't repeatedly resubmit identical edits". For a rejected edit, fix the policy issue and send a new locations.patch or locations.updateAttributes.
These are alpha channel methods, so fields can change before a stable release. No v1 date is given.

What to do next

Business owners: Nothing. Your listing tool may start showing whether Google accepted your edits.
Marketers and agencies: Ask your listing tool whether it will show Google's edit status and rejection reasons for client locations.
Developers: Call the two getExtended methods after each update to show status, back off while edits are pending, and expect alpha changes.

Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.