Google Reviews API
The Google Reviews API for one business at a time
/search/reviews returns one business's Google reviews — rating, full text, author, date, and any owner reply — from a single GET request. Address the place with a featureId, a cid, or just its name. 1 credit per call, up to 50 reviews, 3,000 free credits to start.
{ "searchTime": 0.17, "totalResults": 85000, "page": 1, "organic": [ { "position": 1, "title": "31.10. Connection Pools and Data Sources", "link": "www.postgresql.org/docs/…", "domain": "postgresql.org", "snippet": "For an environment without an application se…" }, { "position": 2, "domain": "medium.com", … }, { "position": 3, "domain": "stackoverflow.blog", … } ], "credits": 1}What is the Google Reviews API and how many reviews can I get per call?
Searlo's /search/reviews endpoint returns up to 50 of a business's Google reviews per call — rating, full text, author, date, and any owner reply — for 1 credit. Address the business with the featureId or cid from a places result, or resolve it by name with q.
Google's place-review lookup has no continuation token, so 50 is the ceiling per call, not a page size — there is no "page 2" to request. That is the honest limit: if a business has thousands of reviews, this endpoint gives you its top reviews, not a scrape of its full archive.
- Reviews per call
- Up to 50 (limit parameter, default 10) — hasNextPage is always false, there is no pagination
- Cost per call
- $0.30 per 1,000 calls (1 credit each)— our pricing
- Free credits to start
- 3,000 free credits — One-time bonus on sign-up. No credit card required.— our pricing
- Outscraper Google reviews
- Free first 500 reviews, then $3/1,000 (501–100,000), $1/1,000 after 100,000 — billed per review returned, not per call; claims uncapped "all reviews" access— outscraper.com/google-business-reviews-api
- DataForSEO Google Reviews API
- $0.075 per 1,000 reviews (standard queue, up to 45 min) or $0.15 per 1,000 (priority, up to 1 min) — an async task, not a live GET— dataforseo.com/apis/reviews-api/google-reviews-api
- Yelp Places API (different data source)
- $229–$643/mo plus $5.91–$14.13 per additional 1,000 calls; up to 7 review excerpts at the top tier, never the full review text— business.yelp.com/data/products/places-api
Third-party figures on this page last verified against the sources linked above. Prices change; if you find one of these stale, tell us and we will correct it.
/search/reviews is a different shape of question from a places search: instead of "which businesses match this query", it's "what do people say about this one business". Every serious SERP-data competitor treats that as a separate product with its own page — SerpApi's /google-maps-reviews-api, Outscraper's /google-business-reviews-api, DataForSEO's /reviews-api/google-reviews-api, ScrapingDog's /google-maps-reviews-api — and Searlo does the same here rather than folding reviews into the places page as an afterthought.
Address the business with featureId or cid — both come straight off a /search/places or /search/maps result — or skip the lookup entirely and pass a name in q. The response carries the place's own rating and review count alongside the reviews themselves, so you always have both the sample and the total it was drawn from.
The one thing this endpoint will not do is hand you a business's complete review history. Google's underlying place-review call returns one page with no continuation token, so 50 reviews is the ceiling — not a limit Searlo imposes, but the shape of the data it's built on.
Features
Full review text
Not just a star average — the actual review text, per review, for up to 50 reviews per call.
Author detail
Name, profile URL, photo, their own review count, and whether they're a Local Guide — enough to weigh a review, not just read it.
Place-level rating and count
Every response includes the place's overall rating and total review count, so a 50-review sample always comes with its context.
Owner replies
When a business responded, the reply's text and relative timestamp come back attached to the review it answers.
Three ways to address a place
featureId, cid, or a plain-text name in q — whichever your workflow already has on hand.
Localized results
gl and hl return reviews and place data as Google renders them for that country and language.
Get started in one request
Address the place with the featureId or cid off a places result, or skip straight to a name lookup with q.
curl "https://api.searlo.tech/api/v1/search/reviews?featureId=0x808580620f5d41dd%3A0x13b2c33ee2dfe160&limit=50" \
-H "x-api-key: YOUR_API_KEY"import requests
r = requests.get(
"https://api.searlo.tech/api/v1/search/reviews",
params={"featureId": "0x808580620f5d41dd:0x13b2c33ee2dfe160", "limit": 50},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = r.json()
print(data["place"]["title"], data["place"]["rating"], data["place"]["reviewCount"])
for rev in data["reviews"]:
print(rev["rating"], rev["author"], rev["text"][:80])
if "response" in rev:
print(" owner reply:", rev["response"]["text"])const params = new URLSearchParams({
featureId: "0x808580620f5d41dd:0x13b2c33ee2dfe160",
limit: "50",
});
const res = await fetch(
`https://api.searlo.tech/api/v1/search/reviews?${params}`,
{ headers: { "x-api-key": "YOUR_API_KEY" } },
);
const { place, reviews } = await res.json();
console.log(place.title, place.rating, place.reviewCount);
reviews.forEach((r) => console.log(r.rating, r.author, r.text.slice(0, 80)));curl "https://api.searlo.tech/api/v1/search/reviews?q=Franklin%20Barbecue%20Austin&limit=20" \
-H "x-api-key: YOUR_API_KEY"import requests
r = requests.get(
"https://api.searlo.tech/api/v1/search/reviews",
params={"q": "Franklin Barbecue Austin", "limit": 20},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = r.json()
print(data["place"]["title"], data["place"]["rating"])const params = new URLSearchParams({ q: "Franklin Barbecue Austin", limit: "20" });
const res = await fetch(
`https://api.searlo.tech/api/v1/search/reviews?${params}`,
{ headers: { "x-api-key": "YOUR_API_KEY" } },
);
const { place } = await res.json();
console.log(place.title, place.rating);Searlo vs Outscraper
Outscraper is the most-cited Google reviews scraper, and its own pricing page is the fairest comparison — it bills per review returned, not per call, which is a structurally different unit worth pricing out at your actual volume.
| Capability | Searlo | Outscraper |
|---|---|---|
| Billing unit | $0.30 per 1,000 calls (up to 50 reviews each) | Per review returned: free first 500, then $3/1,000 (501–100K), $1/1,000 after |
| Live, synchronous response | Yes | Yes |
| Free tier | 3,000 free credits | First 500 reviews free |
| Reviews per lookup | Up to 50 — no pagination (Google's own limit) | Claims uncapped "all reviews" access |
| Owner replies included | Yes | Yes |
| Address a place by | featureId, cid, or name (q) | Place ID or Google Maps URL |
Why reviews get their own endpoint
A places search answers "which businesses match"; a reviews call answers "what do people say about this one" — different input shape (one place, not a query over many), different consumer (a reputation dashboard or a review-response tool, not a directory). Every peer in this space — SerpApi, Outscraper, DataForSEO, ScrapingDog — sells it as a separate product for exactly that reason, and folding it into the places page would bury a distinct search intent under an unrelated one.
The 50-review cap, and why there's no page 2
Google's own place-review lookup returns one batch of reviews with the place record and no continuation token — hasNextPage is always false in the response. Fifty is the ceiling Searlo can return per call, and it is a limit of the upstream data, not a quota Searlo could raise on request.
If a workflow genuinely needs a business's full review archive rather than its current top reviews, no live API call — from Searlo or otherwise — gets you there in one request; that is a different, heavier scraping problem this endpoint does not claim to solve.
Three ways to address a place
featureId and cid are the identifiers a /search/places or /search/maps result already carries — pass either straight through and skip a second lookup. Where no prior search exists, q resolves a plain-text name ("Franklin Barbecue Austin") to its top matching place before returning that place's reviews.
What's in an owner reply
When a business has responded to a review, the response object carries the reply's text and a relative timestamp ("2 weeks ago"), attached to the review it answers. The review itself carries an absolute isoDate; Google doesn't expose one for the reply, so a reply's exact date isn't available — only how long ago it was posted, relative to when you called the API.
Google Reviews API pricing, compared honestly
Searlo charges $0.30 per 1,000 calls, one credit per call regardless of how many of the up-to-50 reviews come back. Outscraper and DataForSEO price by the row instead: Outscraper is free for the first 500 reviews then $3/1,000 up to 100,000 ($1/1,000 after; verified at outscraper.com/google-business-reviews-api), and DataForSEO is $0.075 per 1,000 reviews on its standard queue or $0.15/1,000 on priority — cheaper per row, but an async task with up to a 45-minute turnaround rather than a live response (verified at dataforseo.com/apis/reviews-api/google-reviews-api).
Neither comparison is apples-to-apples without naming the unit: per-call pricing rewards fewer, larger pulls; per-row pricing rewards pulling exactly the reviews you need and no more. Both are listed above (verified 2026-09-13) so the choice is a real trade-off, not a marketing number.
Google reviews vs. other review sources
Yelp is not a substitute data source for this endpoint — it's a different platform with its own reviews, and Searlo does not return Yelp data anywhere. Yelp's own Places API is worth knowing about only as a pricing contrast: $229–$643/month plus $5.91–$14.13 per additional 1,000 calls, a 30-day trial capped at 5,000 calls, and no tier that returns more than 7 review excerpts — never full review text (verified at business.yelp.com/data/products/places-api, 2026-09-13). If Yelp reviews specifically are the requirement, that is a separate product to evaluate, not a gap in this one.
What teams build on the reviews API
- Reputation-monitoring dashboards that track rating and sentiment over time
- Competitor review benchmarking across a set of locations
- Review-response tooling and CRM enrichment with recent customer feedback
- Local SEO audits that use review count and rating as ranking signals
- AI agents and chat assistants summarizing recent sentiment for a business
FAQ
Frequently asked questions
What is the Google Reviews API?
Searlo's /search/reviews endpoint returns one business's Google reviews — rating, full text, author, date, and any owner reply — from a single GET request, addressed by featureId, cid, or a name lookup. It returns up to 50 reviews per call and includes the place's overall rating and review count alongside them.
Is this the same as the Google Maps Reviews API?
Yes — "Google reviews API" and "Google Maps reviews API" describe the same product across this market (SerpApi, Outscraper, and ScrapingDog all use the "maps reviews" phrasing for their equivalent endpoint). Searlo's single /search/reviews endpoint covers both phrasings; there's no separate product or price for one versus the other.
How many reviews can I get per business?
Up to 50 per call, set with the limit parameter (default 10). Google's place-review lookup returns one batch with no continuation token — hasNextPage is always false — so 50 is a hard ceiling, not a page size you can paginate past.
How much does a Google business reviews API cost?
Searlo charges $0.30 per 1,000 calls, one credit per call regardless of how many reviews come back, with 3,000 free credits to start. Outscraper bills per review returned (free under 500, then $3/1,000 up to 100K), and DataForSEO charges $0.075–$0.15 per 1,000 reviews as an async task — three different pricing units, compared in full above.
Do you return review photos?
No. /search/reviews returns the review text, rating, and author detail (including the author's own profile photo), plus any owner reply, but not photos attached to the review itself. If photo extraction is a hard requirement, that is a real gap versus scrapers like Outscraper that do return them.
Can I get Yelp reviews from this API?
No — /search/reviews returns Google reviews only. Yelp is a separate platform with its own review corpus; Yelp's own Places API is priced from $229/month and, at every tier, returns at most 7 review excerpts rather than full review text.
How do I find a business's featureId or cid?
Both come off a Google Places API result: search with /search/places or /search/maps, and each returned business carries featureId and cid. Pass either straight into /search/reviews, or skip the lookup entirely and pass the business name in q.