Updated Oct 2026

Google My Business API Migration: Map Every v4 Endpoint to the New Business Profile APIs

The Google My Business API v4 wasn’t switched off in one go. Google split it into separate Business Profile APIs: accounts moved to the Account Management API, locations to the Business Information API, verifications and notifications to their own APIs, and insights to the Performance API. Reviews, local posts and media still run on mybusiness.googleapis.com/v4. A Google My Business API migration is mostly a matter of moving account and location calls, adding readMask, and deleting features Google discontinued, such as Q&A and Business Calls.

New to the naming? Start with the Google My Business API and the Google Business Profile API overviews.

What “deprecated” means in the Google My Business API

Google uses two states on its sunset dates page:

• Support ended: the method still works, but gets no new features or bug fixes.
• Discontinued: the method returns errors and is about to be shut down.

If your code still calls a discontinued v4 method, you’re not looking at a warning. You’re looking at errors in production.

Google My Business API migration map: old → new

Dates come from Google’s sunset dates page. The original split of v4 into separate APIs happened earlier and isn’t listed there.

What still lives in v4

These resources remain documented on v4.9 and keep getting features (see the change log):

Reviews still use the v4 name format accounts/{accountId}/locations/{locationId}. The new APIs use locations/{locationId}. Keep a helper that converts between both. For the reviews side, see our guide to replying to reviews by API.

How to migrate, step by step

Step 1 — Inventory every v4 call

Search your codebase for mybusiness.googleapis.com/v4 and for client library classes such as Mybusiness.Accounts. Tag each call as “move”, “keep on v4” or “delete” using the tables above.

Step 2 — Enable the new APIs in your Cloud project

Enable My Business Account Management API, My Business Business Information API, My Business Verifications API, My Business Notifications API and the Business Profile Performance API. Each has its own default quota of 300 QPM.

Step 3 — Move account calls

# Before (v4, deprecated)
curl -H "Authorization: Bearer ACCESS_TOKEN" "https://mybusiness.googleapis.com/v4/accounts"

# After (Account Management API v1)
curl -H "Authorization: Bearer ACCESS_TOKEN" "https://mybusinessaccountmanagement.googleapis.com/v1/accounts"

Step 4 — Move location calls and add readMask

The Business Information API returns only the fields you ask for. Omit readMask and the call fails (locations.list reference).

// Node 18+ — after migration
const res = await fetch(
  `https://mybusinessbusinessinformation.googleapis.com/v1/accounts/${accountId}/locations` +
  `?readMask=name,title,storefrontAddress,websiteUri&pageSize=100`,
  { headers: { Authorization: `Bearer ${token}` } }
);
const { locations = [], nextPageToken } = await res.json();
// location.name is "locations/123..." — build "accounts/{accountId}/locations/123..." for v4 reviews

# Python 3 — after migration
import requests
r = requests.get(
    f"https://mybusinessbusinessinformation.googleapis.com/v1/accounts/{account_id}/locations",
    params={"readMask": "name,title,storefrontAddress,websiteUri", "pageSize": 100},
    headers={"Authorization": f"Bearer {token}"},
)
r.raise_for_status()
for loc in r.json().get("locations", []):
    location_id = loc["name"].split("/")[-1]
    reviews_parent = f"accounts/{account_id}/locations/{location_id}"

Field names changed too: for example, the business name is title and the address is storefrontAddress in the new API. Map them in one place, not across your codebase.

Step 5 — Move insights and notifications

Replace reportInsights with locations.fetchMultiDailyMetricsTimeSeries and translate the metric names. Replace notification settings with PATCH https://mybusinessnotifications.googleapis.com/v1/accounts/{accountId}/notificationSetting. The NEW_REVIEW and UPDATED_REVIEW types are still available; the Q&A types are deprecated.

Step 6 — Delete what Google shut down

Remove Q&A, Business Calls, photo and post insights, and health provider attributes. There’s no replacement, so these become product decisions, not code changes.

Step 7 — Test and watch the logs

Run both paths side by side for a few days and compare location counts and review counts. Watch for 400 (missing readMask or updateMask), 403 (API not enabled in the project) and 429 (new API, new quota).

Common migration errors

FAQ

Is the Google My Business API deprecated?

Partly. Accounts, locations, verifications, notifications and insights moved to new Business Profile APIs. Reviews, local posts and media are still served by the v4 endpoints.

Where are reviews in the new Business Profile APIs?

Reviews remain on mybusiness.googleapis.com/v4: reviews.list, reviews.get, updateReply, deleteReply and locations:batchGetReviews. See our Google reviews API page.

Do I need to apply for access again to use the new APIs?

Access is granted per Google Cloud project, so you enable the new APIs in the project you already use. New projects follow the access process first.

What replaced reportInsights?

locations.fetchMultiDailyMetricsTimeSeries in the Business Profile Performance API v1. reportInsights was discontinued on 2023-03-30.

Is the Q&A API still available?

No. Google ended support for the My Business Q&A API on 2025-09-15 and discontinued it on 2025-11-03, with no replacement.

curl "https://api.prismareviews.com/v1/locations" \
  -H "Authorization: Bearer $PRISMA_API_KEY"