Google Maps reviews API for business locations

Google offers its own Places API, and its review data comes back capped to a limited sample of reviews per place rather than the full set a visitor can scroll through on Google Maps itself. That's fine for a small business card, but it isn't enough to analyze sentiment trends or monitor a location's review history in any depth.

Roketfy's Google Maps reviews API is built for the deeper pull: it returns review text, rating, timestamps, attached photos and owner responses, with a depth parameter that can go well beyond what a limited sample gives you.

Identify the place with a keyword (the business name), or, if you already have one, a Google place_id or cid — the two stable identifiers Google itself uses. A location parameter is required alongside it, since the same business name can resolve to different real-world places depending on where the search is anchored.

For a business you're not sure you've matched correctly, run maps-search first with the same keyword and location — it returns a ranked list of matching places with their own place ids and CIDs, which you can then pass into maps-reviews or maps-place with confidence you've got the right one.

The depth parameter controls how many reviews come back in one call, from 1 up to 4,490, defaulting to 10 if you leave it out. Billing is per ten reviews, so requesting depth 50 costs the same as five requests for ten reviews each would — the difference is you get them in one call instead of five.

As with every Data Engine endpoint, only successful requests are charged. A call that fails for a bad place identifier or a location Google can't resolve costs nothing.

Yes. sort_by accepts newest, highest_rating, lowest_rating or relevant (the default), so you can pull the most recent reviews for ongoing monitoring or the lowest-rated ones when you're specifically hunting for service issues to address.

There's no built-in keyword filter on review text itself — pull the reviews you need at the depth and sort order that gets you the right slice, then filter or search the returned text on your own side if you need something more specific.

For a chain, run maps-search once per city or region with the brand name and that region's location value, and use the CIDs it returns to build a stable list of branch identifiers. From then on, call maps-reviews and maps-place directly with each CID rather than re-searching by name every time — it's faster and avoids ambiguity when two branches share a similar name.

maps-place is worth pulling alongside reviews for each location: it returns categories, hours, attributes and rating distribution in one call, giving you the full profile of a branch, not just its review stream.