GMBSync. by CodeWays

Bypass the Google Places API 5-Review Limit with Official GBP OAuth Sync

Every developer who integrates Google Maps Place Details hits the same brick wall: even if a business has 800 verified reviews, Google Places API returns at most 5 reviews with no pagination cursor. Here is why that limit exists at the API boundary and how to sync every historical review cleanly using official Google Business Profile OAuth 2.0.

Why Both Places API Legacy and Places API (New) Stop at 5 Reviews

Google divides Maps review access into two completely separate product boundaries: public lookup APIs (Places API) and owner-authenticated management APIs (Google Business Profile API). Regardless of whether you query the legacy /maps/api/place/details/json?fields=reviews endpoint or the newer Places API (New) endpoint https://places.googleapis.com/v1/places/{placeId} with X-Goog-FieldMask: reviews, Google enforces a strict 5-item array cap.

There is no pageSize, offset, or nextPageToken parameter on Places API reviews. Additionally, Places API payloads are strictly read-only: you cannot filter out spam programmatically across your full catalog, monitor 1-to-3 star alerts in real time, or publish owner replies back to Google Maps.

1. Hard 5-Review Truncation

Places API only snapshots five editorial highlights per lookup, leaving hundreds of recent 5-star customer stories invisible on your storefront.

2. GBP 0-QPM Approval Gate

Building directly against Google Business Profile API v4 starts at 0 QPM quota until Google manually approves your GCP project application.

3. Paginated OAuth + Dedup

GMBSync holds approved GBP API production quota, pulls 50 reviews per page via nextPageToken, and deduplicates against Places snapshots cleanly.

Places API (New) vs GBP API v4 vs GMBSync Edge Engine

Comparison of Google Places API, Google Business Profile API v4, and GMBSync review sync capabilities
API Capability Google Places API (New) Raw GBP API v4 (DIY) GMBSync Edge Sync
Maximum Reviews Fetched Hard cap at 5 reviews 100% (50/page + cursor) 100% + Takeout archive
Authentication Requirement Billable GCP API Key business.manage OAuth + Quota Pre-approved 1-click OAuth
Owner Reply Publishing Not supported (read-only) PUT .../reviews/{id}/reply 1-click & AI autopilot
Storefront Delivery Cost Per-SKU Places billing Self-hosted cron + cache <15 KB cached widget ($0+)

Places API Cap vs Paginated GBP v4 + Edge Embed

Once your Google Business Profile is linked in GMBSync, embed your full synchronized review library anywhere in two lines without exposing API keys or hitting the 5-review cap:

// 1. Places API (New): capped at 5 reviews, zero nextPageToken
GET https://places.googleapis.com/v1/places/ChIJ...
Header: X-Goog-FieldMask: rating,userRatingCount,reviews

// 2. GBP API v4 (OAuth business.manage): full paginated review stream
GET https://mybusiness.googleapis.com/v4/accounts/{accountId}/locations/{locationId}/reviews?pageSize=50&pageToken={nextPageToken}

// 3. GMBSync Storefront Embed (<15 KB, full synced history, zero API keys):
<div id="gmbsync-widget" data-widget-id="YOUR_WIDGET_ID" data-layout="carousel" data-min-stars="4"></div>
<script src="https://gmbsync.com/widget.js" async defer></script>

How GMBSync Deduplicates Places Snapshots, GBP Pages & Google Takeout Archives

Switching from Places API to Google Business Profile OAuth often causes duplicate review rows in naive sync scripts because Places returns temporary anonymous URL hashes while GBP v4 uses canonical location-scoped review IDs. GMBSync resolves this automatically across every sync cycle:

  • Canonical Scoped Keys: Authenticated GBP reviews carry deterministic :gbp: review identifiers linked directly to your verified location_id, enabling reliable PUT .../reply publishing back to Google.
  • Author + Rating + Comment Fingerprinting: When you import historical Google Takeout JSON or CSV exports (500+ older reviews) alongside live OAuth pagination, existing Places entries are automatically normalized and merged without creating duplicate cards.
  • Background Sync Cadence: New reviews, star-rating changes, and customer edits sync automatically on your plan schedule (hourly on Agency, 6-hour on Growth, daily on Pro, weekly on Free) and immediately purge storefront edge caches.

Google Places API 5-Review Limit FAQ

Can Google Places API (New) return more than 5 reviews using nextPageToken?

No. Both legacy Place Details (maps/api/place/details/json) and Places API (New) (v1/places/{placeId}?fields=reviews) strictly truncate the reviews array to a maximum of 5 items and provide zero pagination tokens.

Does sorting by newest vs most_relevant give 10 unique Google reviews?

Legacy Place Details allowed toggling reviews_sort=newest and most_relevant to surface up to 5 from each view (often overlapping), whereas Places API (New) always caps reviews[] at 5 total reviews per Place lookup and still misses older review history and owner reply publishing.

How long does Google Business Profile API quota approval take?

New Google Cloud projects start at 0 QPM (queries per minute) on Google Business Profile APIs and require submitting a business case, domain verification, and manual Google review that commonly takes weeks to months. GMBSync operates on pre-approved production GBP API quota so you can connect via OAuth 2.0 immediately.

How do I import 500+ historical Google reviews immediately?

Connect your Google Business Profile via OAuth 2.0 inside GMBSync to pull paginated GBP v4 pages (50 reviews per page with nextPageToken), or upload your Google Takeout JSON export in Dashboard Settings to hydrate your entire multi-year archive in seconds without duplicates.