Google Reviews API: The Official Routes and What They Miss

Searching for a Google reviews API leads to a frustrating discovery.
Google has two official APIs that touch review data, and neither does what most people searching for one actually need.
One returns a maximum of 5 reviews per place.
The other returns full review data, but only for businesses you own, and only after Google approves your application.
If you need all reviews, for any place, in a format your software can use, you're outside what the official routes offer.
This guide maps the whole picture: what each official API actually returns, why the caps exist, and the at-scale alternatives that fill the gap.

Key Takeaways

• Google has no official API for unlimited public review access. The two official routes are the Places API (capped) and the Business Profile API (own listings only).
• The Places API returns a maximum of 5 reviews per place. They're relevance-sorted, and there's no pagination to get more.
• The Business Profile API requires approval and ownership. It returns full review data, but only for locations you manage, and API access itself is granted through an application form.
• At-scale access comes from third-party APIs. These source review data from public Google Maps listings and return it as structured JSON, for any business.
• Review volume on Google is worth the effort. A single Las Vegas hotel carries over 143,000 Google reviews, more than its count on any other platform.

The Two Official Routes (and Their Walls)

Google's official review access splits across two very different APIs.
Knowing which wall you'll hit saves days of reading the wrong documentation.

Places API: a hard cap of 5 reviews

The Places API returns place details for any business, including a reviews field.
Google's own reference is explicit: "A maximum of 5 reviews can be returned", sorted by relevance.
No pagination.
No way to request the 6th review.
A business with 54,000 reviews and a business with 12 reviews both return at most 5.
Google places API reviews access works fine for showing a review snippet on a map widget, which is the job it was designed for.
For analysis, monitoring, or reputation work, 5 relevance-picked reviews is a keyhole.

Business Profile API: full data, owners only

The Business Profile API (formerly Google My Business) returns complete review data with pagination.
The catch is scope: it serves businesses managing their own profiles, so you read reviews for locations you own or manage.
Access is also gated.
The API is only visible to Google accounts that submit and receive approval through an access request form.
Good for a brand pulling its own reviews into a support workflow.
No help at all for competitive analysis, market research, or any use case involving businesses you don't control.

Side by side

Why the Caps Exist

The pattern makes sense from Google's side.
Review content is one of Google Maps' main assets, and handing it out in bulk through a cheap official endpoint would hand away the asset.
So the official APIs serve two narrow jobs: decorating map integrations (Places) and letting merchants manage their own presence (Business Profile).
Everything between those two jobs, which includes most real review-data use cases, has no official route.
Full access means getting the same data a user sees on the public Google Maps listing: every review, the reviewer context, the owner responses, the running total.
That data is visible to anyone with a browser.
The question is getting it as structured JSON instead of a screen, which is where the google maps reviews API alternatives come in.

The At-Scale Options

Third-party providers fill the gap with APIs that source review data from public Google Maps listings.
They differ mainly in pricing shape and how much of the pipeline they run for you.

The DIY row deserves its one honest sentence: Google Maps is a heavily defended, frequently changed target, and keeping a scraper alive against it is a standing engineering cost rather than a weekend project.
For a general comparison of scraper classes and their real costs, the hotel data scraper guide covers the same tool families in depth.

Pulling Google Reviews with StayAPI

Vertical data APIs deliver the same at-scale access with a domain focus.
StayAPI's Google reviews endpoints return full review data for any business on Google Maps, hotel or otherwise (we've pulled a New York deli with 54,000 reviews through the same two calls).
The flow is two requests.
First, find the place's data_id by name with the search-and-review endpoint:

curl -X GET "https://api.stayapi.com/v1/google_reviews/search-and-review?query=Bellagio%20Las%20Vegas" \
  -H "x-api-key: YOUR_API_KEY"

Then pull reviews with that data_id, sorted how you need them:

curl -X GET "https://api.stayapi.com/v1/google_reviews/reviews?data_id=0x80c8c430cb5147bd:0x82f2c7c5d9d10d84&sort_by=newest" \
  -H "x-api-key: YOUR_API_KEY"

The truncated response:

{
  "success": true,
  "data_id": "0x80c8c430cb5147bd:0x82f2c7c5d9d10d84",
  "place_name": "Bellagio Hotel & Casino",
  "place_address": "3600 Las Vegas Blvd S, Las Vegas, NV 89109",
  "total_reviews": 143399,
  "average_rating": 4.7,
  "reviews": [
    {
      "rating": 5.0,
      "text": "Precioso, cómodo y con una excelente ubicación para hospedarse",
      "iso_date": "2026-08-24T17:14:03Z",
      "reviewer": {
        "name": "Claus M.",
        "reviews_count": 32,
        "local_guide": true
      },
      "likes": 0,
      "owner_response": null
    }
  ],
  "next_page_token": "..."
}

Reviews come back in pages, and sort_by accepts newest, highest_rating, lowest_rating, or the default most_relevant.
Sorting by newest is what makes monitoring work: each pull starts at the most recent review instead of Google's relevance picks.
Full parameter details are in the Google reviews API documentation.
For hotels specifically, the same key covers review data across Google Hotels, Booking.com, TripAdvisor, and other OTAs, so Google reviews land in the same pipeline as the rest of the guest feedback.

What It Costs

Google reviews API pricing depends on the route, and the shapes matter more than the exact numbers.
- Places API: pay-per-request by SKU tier, and the reviews field sits in a premium tier. You're paying real money for 5 reviews per place.
- Business Profile API: free, if you clear the approval and only need your own locations.
- SERP-scraper and extractor tools: per request or per thousand results; costs scale linearly with volume.
- StayAPI: per-request pricing with a free tier to test on, and no rate limits to engineer around.
For a one-time pull of a handful of places, almost any option is cheap.
The math diverges at monitoring scale: pulling fresh reviews for 200 locations weekly is 800+ requests a month, every month, and per-request price differences compound fast at that volume.

Getting Started

Here's the shortest path to full Google review data:
1. Sign up at stayapi.com to get an API key. Free tier, no credit card.
2. Preview the data without writing code: the free Google search and reviews tool takes a business name and shows the structured response.
3. Find your target's data_id with the search-and-review endpoint (one request per business, cache the IDs).
4. Pull reviews with sort_by=newest and page through with next_page_token until you're caught up.
5. Schedule the pull. A cron job or a no-code flow in N8N or Make.com can append new reviews to a sheet or database on whatever cadence you need.
6. If the reviews feed analysis, the hotel review sentiment guide covers what to do once the data lands.
For a walkthrough against your specific use case, book a demo call.

FAQ

Is Google reviews API free?

The official options have costs on both routes: the Places API bills per request (and caps at 5 reviews), while the Business Profile API is free but limited to your own approved locations.
Third-party APIs typically offer free tiers for testing and charge per request at scale.

How do I get an API for Google reviews?

Pick the route that matches your scope.
Your own business's reviews: apply for Business Profile API access.
A snippet of any place's reviews: the Places API with a standard key.
All reviews for any place: a third-party provider; StayAPI's Google reviews endpoint is one example.

How do I see all Google reviews for a business?

On screen, the Google Maps listing shows them all.
Programmatically, no official API returns the full set for a business you don't own, so full access runs through third-party APIs that source from the public listing and paginate through the complete history.

Do you need a Google reviews API key?

Every route needs some key: a Google Cloud API key for the official APIs (plus approval for Business Profile), or the provider's key for third-party access.
Third-party providers typically use one key in a request header, and the same key covers every source they offer.

Can I get more than 5 reviews from the Places API?

No.
The 5-review maximum is a documented hard limit of the Places API, with no pagination parameter.
More than 5 means the Business Profile API (your own locations) or a third-party source.