Google reviews API: 4 APIs an agent can call

A Google reviews API returns the reviews people left on a Google Maps place: the rating, the text, the date and a few more fields per review. You want them to watch your own locations, read what customers say about a competitor, or score a list of local leads. The catch is the input. Every endpoint below wants an identifier for one place, and each provider names that identifier differently.

This post compares the Google reviews APIs in the looot catalog that an agent can call today. You get what each returns, the id it takes, how it bills, a live price table, a guide for choosing, a prompt and a FAQ.

Google reviews API: the short answer

Each bullet names one need. Pick by the id you already have and the number of reviews you want per call.

• Serper, best for reading recent reviews cheaply: about 20 reviews per call, sorted by newest or by rating.
• AnyAPI, best for pulling up to 100 reviews of one place in a single call, at a flat price per request.
• Anysite, best when you also want place photos or the reviews one contributor wrote, from the same provider.
• SerpApi, best when you already search Google Maps through SerpApi and hold its place_id or data_id.

Prices are read from the catalog when the page loads. Anysite bills each review it returns, so it sits in its own table with a per-result price.

Key takeaways

• Reviews are step two. Step one is a Maps search that returns the place id, and each provider has its own search endpoint for that.
• AnyAPI is the only one here whose description says the price stays the same however many reviews come back, up to 100 per call.
• Anysite's cost grows with the count you ask for. Set count low on a first test.
• Google's own Places API returns at most five reviews per place. Google's Place Details documentation, read 2026-11-04, says the reviews field returns "up to five user-submitted Review objects". The endpoints below return more, by paging or by a larger count per call.

How we ranked these Google reviews APIs

We read the public looot catalog on 2026-11-04. Each provider below has an endpoint tagged maps_place_reviews. Serper, AnyAPI and SerpApi bill per call, so we ordered them by that price, cheapest first. Anysite bills per result, which a per-call price cannot be compared with directly.

We placed Anysite by the cost of about 20 reviews, the page Serper returns in one call. At its catalog rate, 20 Anysite results cost more than one Serper or AnyAPI call and less than one SerpApi call, so it sits third. The tie-break, which we did not need, is the number of related Maps endpoints the provider has in the catalog.

We did not run these endpoints for this post. The catalog publishes no measured success rate or speed for them, so we rank on neither. Yelp also appears under this capability, but it returns Yelp excerpts, not Google reviews, so we left it out. The blog's provider snapshot is dated 2026-10-12.

1. Serper, best for recent reviews at a low price per call

The Serper endpoint serper-reviews returns the Google Maps reviews of one place: rating, snippet, user, date and likes, about 20 per page. Pass nextPageToken to get the next page. The sortBy field takes mostRelevant, newest, highestRating or lowestRating. It needs a cid, fid or placeId, which come from a Serper Maps or places result.

Best for

• Checking the newest reviews of your own locations each week by hand.
• Reading the lowest-rated reviews of a competitor to see what people complain about.

Strengths

• The sort options let the agent ask for exactly the slice it needs.
• Serper's local places endpoint returns the cid, so search and reviews stay with one provider.

Limits

• About 20 reviews per call. A place with hundreds of reviews takes many paged calls.
• The input must be an id from a Serper result. A place id from another provider may not match.

Does not fit: a job that wants every review of a busy place in as few calls as possible.

2. AnyAPI, best for many reviews in one call

The AnyAPI endpoint anyapi-run-maps-reviews fetches up to 100 Google Maps reviews for a place by place ID, sorted the way you ask, in one normalized response. The description says the price is flat per request, the same whatever the number of reviews returned. It also lists four routing lanes that run in order when one fails, and a failed attempt moves on only when your payment covers that lane's price.

Best for

• Pulling the last 100 reviews of a place to summarize themes.
• Scoring a lead list where each lead needs a fuller sample than one page.

Strengths

• One call can hold up to 100 reviews, so fewer calls per place.
• The normalized schema stays the same across lanes, so the agent parses one shape.

Limits

• Up to 100 per call is a ceiling. The description does not mention paging past it.
• It takes a place ID. Its Maps search description does not say it returns one, so check the response before you chain them.

Does not fit: a job that wants the full history of a place with thousands of reviews.

3. Anysite, best when you want more than reviews from one provider

The Anysite endpoint anysite-api-google-maps-reviews returns Google Maps reviews for a place. Send feature_id, and sort and count refine it. The description bills 5 credits per 20 results, so the catalog price is per review returned. Anysite also has Maps endpoints for place details, photos and the reviews a single contributor wrote.

Best for

• Pulling reviews and photos of a place through one provider.
• Reading every review one contributor posted, a different endpoint on the same provider.

Strengths

• The count field caps what you pay, because you pay per result.
• The widest set of related Maps endpoints of the four.

Limits

• Per-result billing. Asking for many reviews costs more, unlike a flat per-call price.
• It needs a feature_id. Its places search description does not say it returns one, so read the response first.

Does not fit: a job where you want a fixed cost per place no matter how many reviews come back.

4. SerpApi, best if you already use SerpApi for Maps search

The SerpApi endpoint serpapi-google-maps-reviews returns reviews of one place: rating, snippet, user, date and likes. It takes a place_id or data_id from a Maps search, and next_page_token pages further. The response is raw SerpApi JSON, and search_metadata.status reads Success when the search ran.

Best for

• An agent that already calls SerpApi's Maps search and holds data_id values.
• A team that wants SerpApi's own JSON shape, unchanged.

Strengths

• SerpApi's Maps search returns both place_id and data_id, so the hand-off to reviews is direct.
• search_metadata.status gives the agent a plain check that the search ran.

Limits

• It ranked last on price per call in the live table on 2026-11-04. Check the table for today.
• Raw provider JSON, so the agent parses SerpApi's field names, not a normalized shape.

Does not fit: a team that starts from scratch and wants the lowest cost per review.

How to choose a Google reviews API

Start from the id you hold and the number of reviews you need per place. Most jobs are two calls, find the place and then read its reviews, the same flow as in scraping Google Maps for leads with an agent. Use the same provider for both when you can, so the id matches.

What id do you have?

A Serper cid or placeId goes to Serper. A SerpApi place_id or data_id goes to SerpApi. A feature_id goes to Anysite, and a place ID to AnyAPI. If you only have a business name and a city, run the local search step first.

How many reviews per place?

About 20 recent ones: Serper. Up to 100 in one go: AnyAPI. A small, exact count where you pay only for what comes back: Anysite with a low count.

Do you need more from the same provider?

Photos or contributor history point to Anysite. A Maps search you already run on SerpApi points to SerpApi.

Does the job need a timer?

Watching new reviews every week needs scheduled runs, not available yet. Run the prompt by hand on the day you want fresh data.

Try it

The Google Maps scraper API ranking covers the search step in more depth, and the Google Maps reviews use case lists every reviews endpoint. For a single check by hand, the Google reviews checker needs no setup.

What this post does not cover

It covers reviews of one Google Maps place per call. It does not cover review replies, review removal or your own Business Profile account. It makes no claim about how complete or fast any provider is. Yelp, Google Play and other review sources are left out.

Last checked 2026-11-04 against the public catalog at https://api.looot.ai/v1/public-catalog. Author: the looot team.