Updated Oct 2026

Google My Business API (now Google Business Profile API)

What changed, what still works, and how to keep your review code running.

The Google My Business API still exists, but under a new name: Google now calls it the Google Business Profile APIs. Most of the old v4 features were split into separate v1 APIs or retired, while the review endpoints (list, get, batch get, reply, delete reply) are still served from the v4 Google My Business API. If you maintain GMB code, your review calls keep working; your location, account and insights calls probably need migrating.

Get API key

Keep your review sync running without touching v4. 2 locations free.

How the official Google My Business API works today

What the rename actually changed

Google My Business became Google Business Profile for merchants. For developers, the change was bigger than a name: the single v4 API was broken into purpose-specific services. When you set up a project today, Google lists these APIs to enable in Cloud Console:

One detail catches people out: the “Google My Business API” entry only appears in Cloud Console after your account has been approved through the access request form. If you can’t find it, you’re not approved yet. Details in how to get API access.

What was deprecated, with dates

From Google’s official deprecation schedule:

Old v4 featureReplacementSupport endedDiscontinued
accounts.locations.reportInsights (most metrics)Performance API v1 locations.fetchMultiDailyMetricsTimeSeries2022-11-212023-03-30
localPosts.reportInsights, photo and post metricsNone2022-11-212023-02-20
My Business Business Calls APINone2023-02-212023-05-30
My Business Q&A APINone2025-09-152025-11-03

Location and account management moved to the Business Information and Account Management APIs.

What still lives in v4: reviews

The review endpoints have not moved. They remain under https://mybusiness.googleapis.com/v4/:

MethodEndpoint
reviews.listGET /v4/accounts/{accountId}/locations/{locationId}/reviews
reviews.getGET /v4/accounts/{accountId}/locations/{locationId}/reviews/{reviewId}
batchGetReviewsPOST /v4/accounts/{accountId}/locations:batchGetReviews
updateReplyPUT /v4/accounts/{accountId}/locations/{locationId}/reviews/{reviewId}/reply
deleteReplyDELETE /v4/accounts/{accountId}/locations/{locationId}/reviews/{reviewId}/reply

They accept either the legacy plus.business.manage scope or business.manage. reviews.list returns up to 50 reviews per page. The API is free: Google says it is available to registered users at no charge.

What the Google My Business API doesn’t tell you

Your old code mixes two generations. A typical GMB integration from 2020 calls accounts.locations.list on v4. That now lives in the Business Information API with a different resource shape and a readMask. Reviews still expect the v4 accounts/{id}/locations/{id} name, so you end up translating IDs between v1 and v4 in the same job.

Stack Overflow answers are mostly stale. Many top answers for “google my business api reviews” reference endpoints that were discontinued, or the old Google+ scope as if it were the only one. Check every snippet against the current reference.

Reviews are the last v4 resource standing. Google hasn’t announced a date, and the deprecation schedule doesn’t list reviews. But every other major v4 surface has moved. Budget for one more migration.

Notifications moved too. If you used v4 updateNotifications, real-time alerts are now handled by the My Business Notifications API on Cloud Pub/Sub (NEW_REVIEW, UPDATED_REVIEW).

New projects still need approval. The rename didn’t remove the gate. A new Cloud project starts at 0 QPM until Google approves it, and reaches 300 QPM after. Full detail on our Google Business Profile API page.

Read and reply to Google My Business reviews with Prisma

Prisma calls the Google My Business v4 review endpoints for you and returns the result in one stable format. If Google moves reviews to a new API, we migrate. Your integration doesn’t change. You connect each location by OAuth once, as owner or manager.

curl

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

curl "https://api.prismareviews.com/v1/reviews?location_id=loc_8f2a&platform=google" \
  -H "Authorization: Bearer $PRISMA_API_KEY"

Python (replacing a legacy GMB sync)

Python
import os, requests

API = "https://api.prismareviews.com/v1"
headers = {"Authorization": f"Bearer {os.environ['PRISMA_API_KEY']}"}

for loc in requests.get(f"{API}/locations", headers=headers).json()["data"]:
    reviews = requests.get(
        f"{API}/reviews",
        params={"location_id": loc["id"], "platform": "google", "since": "2026-10-01"},
        headers=headers,
    ).json()["data"]
    for r in reviews:
        print(loc["id"], r["rating"], r["text"][:60])

Node.js (reply)

Node.js
await fetch(`https://api.prismareviews.com/v1/reviews/${reviewId}/reply`, {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.PRISMA_API_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({ text: "Thank you for coming back, Marc!" })
});

Every review uses the same fields whatever the platform: id, platform, location_id, rating (1-5 integer), text, author, created_at, reply, url. Start with the quickstart, or see how to reply to Google reviews via API.

Google My Business API vs Prisma

Google My Business API (v4) + Business Profile APIsPrisma
APIs to integrateUp to 7 Google APIs, v1 and v4 mixed1 REST API, v1
AccessNew Cloud project: apply, 0 QPM until approvedAPI key on sign-up, same day
AuthOAuth 2.0, legacy or new scopeAPI key; OAuth per location handled by Prisma
Reviewsv4 list / get / batchGetReviewsGET /v1/reviews
Replyv4 updateReply / deleteReplyPOST / DELETE /v1/reviews/{id}/reply
Future migrationsYours to doOurs to do
NotificationsNotifications API + Pub/SubWebhooks
PriceFree2 locations free, then plans from €49/month

Keep your own integration if your GMB code already runs on an approved project, you only need Google and you have someone who’ll follow the changelog of Google’s deprecations.

Move to Prisma if your legacy sync broke, the person who wrote it left, or you need Trustpilot, App Store or Google Play reviews in the same format. Our migration guide covers both paths: migrating to the new Google APIs yourself, or swapping to Prisma.

FAQ

Is the Google My Business API deprecated?

The name is retired; the product is now the Google Business Profile APIs. Several v4 features were deprecated (insights in 2023, the Q&A API in November 2025), but the v4 review endpoints are still live and not on Google’s deprecation schedule.

Does the Google My Business API still return reviews?

Yes. reviews.list, reviews.get, updateReply, deleteReply and batchGetReviews are still served under mybusiness.googleapis.com/v4/. For the full picture of reviews options, including Places, see our Google Reviews API page.

Do I need to apply again for Google My Business API access?

Not if your Cloud project was already approved. A new project must apply through the “Application for Basic API Access” form, and its quota stays at 0 QPM until Google approves it.

Is the Google My Business API free?

Yes. Google states it is available to registered users at no charge. The cost is engineering and maintenance.

Is there a Google My Business API Python client?

You can call the REST endpoints with any HTTP library plus an OAuth token, or use Google’s generic API client libraries. With Prisma, it’s a plain requests.get with one API key.

Stop maintaining GMB code.

One API key, Google reviews in a stable format, and we handle the next Google migration.

Get API key

2 locations free, then plans from €49 a month. No Google API application on your side.

Get your API key in a minute

Free Spark plan: 2 locations, no card. Test keys return sample data on all 11 platforms, so you can build before connecting a real one.