Engineering

Google My Business API in 2026: Access, Approval and Posting

Google My Business is now Google Business Profile, but posting still uses v4. Learn which APIs to enable, how approval works, and where Outstand's BYOK integration fits.

Google My Business API in 2026: Access, Approval and Posting

The Google My Business API is now part of Google's Business Profile APIs, a family of services for managing business accounts, locations, posts, reviews, and performance data. Access requires Google's approval for your Cloud project, and the API is available at no charge subject to quotas. In 2026, creating local posts still uses the Google My Business v4 endpoint, not the Business Information API.

TL;DR

  • Apply for Google Business Profile API access before building your production publishing flow.
  • Google requires applicants to manage a verified profile active for at least 60 days and have a business website listed on that profile.
  • A project quota of 0 QPM means access has not been granted. Google's prerequisites identify 300 QPM as the approved-project indicator.
  • Use OAuth with https://www.googleapis.com/auth/business.manage and an authorized business user.
  • Discover accounts and locations with the newer APIs, then create local posts through v4.
  • Outstand requires your own approved Google Cloud credentials for Google Business Profile. Managed Keys do not cover it.

The requirements and quota indicators above come from Google's current API prerequisites, checked in November 2026.

What happened to the Google My Business API?

Google My Business became Google Business Profile. However, the product rename did not turn every endpoint into one new, consistently named API.

Google describes the current architecture as a federated model: separate services handle different capabilities, with different base URLs. Several services retain “My Business” in their names. The reference overview also still lists the Google My Business v4.9 API.

If you search for “google business api,” distinguish profile management from public place discovery. Business Profile APIs manage listings you are authorized to manage. They are not a directory API for retrieving arbitrary businesses. Google's overview directs developers seeking local business information for end users to Google Maps Platform instead.

Which APIs do you actually need?

This is the current service map from Google's reference overview, with the discontinued Q&A service called out separately.

API

Purpose

Relevance to a posting integration

My Business Account Management API

Accounts, administrators, and access management

Discover the user's accounts

My Business Business Information API

Location information and attributes

Discover locations and manage listing data

My Business Verifications API

Verification options and verification status

Check or manage location verification workflows

My Business Notifications API

Account notification settings

Configure event notifications

Business Profile Performance API

Listing performance insights

Read location-level metrics

My Business Place Actions API

Action links such as booking and ordering

Separate from local-post CTA buttons

My Business Lodging API

Hotel amenities and lodging information

Relevant to lodging businesses

Google My Business API v4.9

Local posts, reviews, media, and other remaining functionality

Create local posts using a /v4/ URL

My Business Q&A API

Discontinued service

Do not implement new Q&A workflows

Q&A is not merely awaiting migration. Google's deprecation schedule says it was discontinued on November 3, 2025, with no replacement. Google also instructs developers to stop using its Q&A notification types.

Conversely, do not interpret “legacy v4” as “all v4 endpoints are dead.” Google's 2026 change log includes updates to both local posts and reviews. Check deprecations by resource, not by the age of the hostname.

How to request Google Business Profile API access

Google Business Profile API access is granted to a Google Cloud project. Having a Cloud account, enabling an API, or creating an OAuth client does not itself grant access.

1. Meet the eligibility requirements

Google's prerequisites require applicants to manage a Google Business Profile that is verified and active for 60 or more days. It can be your own office or headquarters, or a client's profile you manage. You also need a website representing the business listed on that profile.

Use an application email that is an owner or manager on the profile. Keep the profile complete and current, including its official website. Google's FAQ additionally recommends a valid business email tied to your business domain and a live, updated website.

Treat these as application preparation steps, not tricks for passing review. Do not create a fake listing just to qualify.

2. Submit the correct project number

Create or select the Google Cloud project your integration will actually use. Copy its project number from the project dashboard. Do not substitute the project name, string project ID, or OAuth client ID.

Open the GBP API access request form, select Application for Basic API Access, and provide the requested business and project details. Describe the legitimate management workflow you are building: for example, publishing approved updates for locations your customers authorize.

Google sends a follow-up email after review. Avoid building an onboarding promise around a guaranteed approval date.

3. Check access before debugging your code

Google's prerequisites explicitly distinguish 0 QPM from 300 QPM when checking approval status. If your project has a zero quota, Google's quota documentation says to request basic API access, not a quota increase.

After approval, enable the services your application needs and create its OAuth credentials. Google's basic setup guide covers this sequence.

There are separate gates here: project API access, OAuth configuration, and the user's permission to manage a particular listing. Passing one does not satisfy the others. Our platform approval guide puts this distinction in context across social integrations.

Google Business Profile API pricing and quotas

Google Business Profile API pricing is straightforward: Google's pricing page states that the Google My Business API is available to registered users at no charge.

Free does not mean unrestricted. The current quota documentation lists 300 QPM defaults for Account Management, Business Information, Performance, Verifications, Lodging, Place Actions, and Notifications. It also lists additional daily limits for particular Business Information operations and a non-increasable limit of 10 edits per minute per profile.

Do not turn those figures into a claimed “300 posts per minute” allowance. The published table does not list a separate localPosts default. Inspect your project's applicable quotas instead of assuming every service and operation shares one allowance.

Requests exceeding quota return HTTP 429 or gRPC RESOURCE_EXHAUSTED. Spread work across time, use exponential backoff with jitter, and avoid large synchronized bursts. A request for higher quota is a separate review, not a paid upgrade that automatically unlocks capacity.

Your application hosting and any integration provider subscription are separate costs from Google's API usage fee.

OAuth and a raw local-post request

Use the current scope from Google's setup guide: https://www.googleapis.com/auth/business.manage.

Your application needs an OAuth access token representing a user with access to the target profile. A Google Cloud API key alone is not a substitute for that authorization. Store client secrets and refresh credentials securely on the server.

The current accounts.locations.localPosts.create reference specifies this request:

bash
1curl -X POST \
2  "https://mybusiness.googleapis.com/v4/accounts/ACCOUNT_ID/locations/LOCATION_ID/localPosts" \
3  -H "Authorization: Bearer GOOGLE_ACCESS_TOKEN" \
4  -H "Content-Type: application/json" \
5  -d '{
6    "languageCode": "en-US",
7    "summary": "Explore our updated services and book your next visit.",
8    "topicType": "STANDARD",
9    "callToAction": {
10      "actionType": "LEARN_MORE",
11      "url": "https://example.com/services"
12    }
13  }'

Replace both resource IDs and the access token with values from your authorized environment. The JSON body is the local post itself, not a localPost wrapper. A successful request returns the created local-post resource.

Google's posting guide covers events, offers, editing, and deletion. It explicitly says Product Posts cannot currently be created through this API. If you add a photo, local-post media uses a publicly accessible sourceUrl with mediaFormat: PHOTO; do not assume the raw image bytes belong in this request.

Managing multiple locations without mixing up resources

Use Account Management to discover accounts, then Business Information to list locations. Google's locations.list reference requires a readMask and supports pagination through nextPageToken.

For a production integration:

  1. Record which customer authorized each connection.
  2. Enumerate the accounts and locations that user can access.
  3. Let the user explicitly select the locations your application should manage.
  4. Persist the resource identifiers and your own customer-to-location mapping.
  5. Queue a separate local-post creation operation for each selected location.
  6. Track results per location so retries do not republish successful destinations.

The create-post method targets one location through its parent path. An account containing many locations does not make one create call publish everywhere.

Keep resource names distinct: newer location APIs use names such as locations/LOCATION_ID, while the v4 posting path includes both account and location. A Maps place identifier is not interchangeable with that v4 resource path.

For third-party listing management, Google's FAQ recommends an agency Organization account and familiarity with business groups and user groups. It also recommends that partners receive manager access rather than making themselves the business's owner.

Common rejections and implementation gotchas

Your application is not ready for access review

Before resubmitting a rejected access request, check the 60-day requirement, verification status, website, applicant's profile role, and submitted project number against Google's prerequisites. These are documented checks, not a claim that Google publishes every internal rejection reason.

If quota remains zero, do not repeatedly regenerate OAuth credentials. That does not fix an unapproved project.

Approval is mistaken for permission to every profile

Google's FAQ explicitly says approved API access does not allow you to query any Business Profile. The authorizing user must have access to the particular profile. When a location is missing, inspect the user's account and permissions before assuming an endpoint is broken.

Test infrastructure changes real business data

Google's setup guide says there is no sandbox. Its FAQ warns against fake production listings and recommends mock responses for testing. Use a real, authorized location carefully for end-to-end checks; a successful write can change a real business's public presence.

Old tutorials promise discontinued analytics

The deprecation schedule shows that localPosts.reportInsights was discontinued in February 2023 with no replacement. Location-level Performance API metrics are not a drop-in source of per-post views or CTA clicks. Keep that distinction visible in your dashboard.

How Outstand fits

Outstand's Google Business Profile integration provides publishing through the same API used for other supported networks. It does not remove Google's access requirements.

Google Business Profile is BYOK in Outstand. Customers must bring their own approved Google Cloud credentials. Outstand does not supply a managed Google Business OAuth application.

The Google Business configuration guide documents the actual setup:

  1. Obtain Google's approval for your Cloud project.
  2. Enable My Business Account Management, My Business Business Information, Google My Business for posting, and Business Profile Performance.
  3. Create a Web application OAuth client and configure the business.manage scope.
  4. Add https://www.outstand.so/app/api/socials/google-business/callback as an authorized redirect URI.
  5. Enter your Client ID and Client Secret under Settings > Social Networks > Google Business.
  6. Connect your Google account, grant permissions, and select the verified locations you want to connect.

Each selected location becomes a separate Outstand social account. After connection, use those account IDs in a publish request following the create-post documentation:

bash
1curl -X POST https://api.outstand.so/v1/posts \
2  -H "Authorization: Bearer YOUR_API_KEY" \
3  -H "Content-Type: application/json" \
4  -d '{
5    "content": "Explore our updated services and book your next visit.",
6    "accounts": ["YOUR_GOOGLE_BUSINESS_ACCOUNT_ID"],
7    "google_business": {
8      "topicType": "STANDARD",
9      "callToAction": {
10        "actionType": "LEARN_MORE",
11        "url": "https://example.com/services"
12      }
13    }
14  }'

This uses an Outstand API key, not the Google access token from the raw example. Supply actual connected account IDs, not google_business or Google location IDs. Platform options belong in the top-level google_business object, not a networkOverrideConfiguration wrapper.

Add other connected location IDs to accounts for multiple destinations. The multi-location publishing walkthrough covers that workflow. Outstand handles the unified publishing interface and supports scheduling through scheduledAt; Google still controls access, listing eligibility, quotas, and content acceptance.

FAQ

Is the Google My Business API still available in 2026?

Yes, but the current umbrella is Business Profile APIs. Account and location management use separate newer services, while local posts and reviews remain in the Google My Business v4 API family.

Is the Google Business Profile API free?

Google states that its Google My Business API is available to registered users at no charge. Approval and quota restrictions still apply. Hosting and third-party integration fees are separate.

Why is my API quota zero?

Google says zero quota means API access has not been granted. Submit the Application for Basic API Access rather than a quota-increase request, and verify that you are inspecting the project you submitted.

Can I publish one post to every location with a single Google request?

The raw local-post create method targets one location. Your integration must fan out to each location. Outstand accepts multiple connected account IDs in one create-post request.

Does Outstand let me skip Google's API approval?

No. Google Business Profile requires BYOK in Outstand: your own approved Google Cloud project and OAuth credentials. You must configure those credentials before connecting locations.