Google Maps Contributor Reviews | Reviewer History API

Pricing

Rating

Developer

Actor stats

Categories

Share

Pull a Google Maps contributor's entire review history as clean structured JSON. Give the API a contributor ID and get back every review that reviewer has left, each with the rating, text, date, likes, photos, and the place reviewed, plus the reviewer's own profile: their Local Guide level, points, and total contributions. It turns a single reviewer into structured data for reputation research, reviewer vetting, and review-fraud detection.

What you get

One row per review, each carrying the reviewer's profile:

• Reviewer: contributor_name, contributor_level, contributor_local_guide, contributor_points, contributor_contributions
• Review: rating, snippet (text), date, likes, review_id, link
• Place reviewed: place_info (title, address, type, coordinates, thumbnail)
• Extras: images, structured details, and the owner response when present

Use cases

• Verify a reviewer is real before trusting their reviews (reputation research)
• Vet an expert witness or a public figure by their full review trail
• Detect coordinated review campaigns by profiling suspect mass reviewers
• Audit whether a reviewer only ever reviews one chain or competitor
• Feed an AI agent a reviewer's history to summarize patterns and red flags

Input

You can read a contributor ID from any place review's reviewer.

Example input

{
"contributorId":"107022004965696773221",
"maxResultsPerContributor":10
}

Sample output

{
"result_type":"review",
"contributor_id":"107022004965696773221",
"position":1,
"contributor_name":"Matt Moeini",
"contributor_level":5,
"contributor_local_guide":true,
"contributor_points":952,
"contributor_contributions":{"reviews":32,"ratings":1,"photos":120},
"review_id":"Ch...",
"rating":5,
"snippet":"Great little spot, the service was excellent ...",
"date":"2 months ago",
"likes":3,
"place_info":{
"title":"Le Petit Marcel",
"address":"2914 N Broadway, Chicago, IL 60657",
"type":"Restaurant",
"gps_coordinates":{"latitude":41.9354,"longitude":-87.6443}
},
"link":"https://www.google.com/maps/..."
}

Pricing

Pay-per-result: a small actor_start fee plus a per-review charge. The per-review price scales down with your Apify plan.

You only pay for the reviews you receive. The endpoint returns about ten of a contributor's most recent reviews per run.

How to get started

1. Open Google Maps Contributor Reviews on the Apify Store.
2. Enter a contributorId (or a contributorIds list).
3. Run the Actor and read the reviewer's history from the dataset.
4. Export as JSON, CSV, or Excel, or pull it from the API.

Prefer code? See johnvc's GitHub for setup guides and code examples.

Run from the API

curl-X POST "https://api.apify.com/v2/acts/johnvc~google-maps-contributor-reviews-api/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN"\
-H"Content-Type: application/json"\
-d'{"contributorId":"107022004965696773221"}'

🔌 Use this API from Claude (MCP)

This Actor is compatible with the Model Context Protocol (MCP), so AI agents can call it as a tool. Add it through the hosted Apify MCP server using this Actor-specific URL:

https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-contributor-reviews-api

If you run agents from Claude Code (free trial) or Claude Cowork (free trial), add the Apify MCP server and ask it to "pull this reviewer's history and flag anything that looks coordinated."

Setup walkthrough:

Apify MCP integration docs: https://docs.apify.com/platform/integrations/mcp

MCP setup, step by step

Visual setup guides for each client (source and more assets: ApifyPublicData on GitHub):

Claude Cowork Desktop (free trial)

👁 Apify MCP install screenshot for the Cowork desktop app

Claude Code (free trial)

👁 Apify MCP install screenshot for the Code CLI

Claude (website)

👁 Install in Claude website

Cursor

👁 Install in Cursor

ChatGPT

👁 Install in ChatGPT

FAQ

What is a contributor ID? It is the long numeric ID that identifies a Google Maps reviewer. You can read it from any place review's reviewer profile, then pass it here to get that reviewer's full history.

How many reviews come back? About ten of the contributor's most recent reviews per run. Use contributorIds to profile several reviewers in one go.

Why is this useful for fraud detection? The reviewer's profile (level, points, contributions) plus their review pattern across places makes it easy to spot mass reviewers, single-target campaigns, and fake-looking accounts.

Can I profile many reviewers at once? Yes. Pass a contributorIds list; each is fetched independently and tagged with its contributor ID.

n8n integration

Available as an n8n community node, n8n-nodes-google-maps-contributor-reviews-api. In n8n: Settings, Community Nodes, install n8n-nodes-google-maps-contributor-reviews-api, then use it in any workflow (it also works as an AI Agent tool).

Featured Tasks

Ready-to-run examples that show this API solving a specific problem. Each opens its own setup so you can run it on your account in one click.

• Get a Google Maps Reviewer's Full Review History
• Audit a Google Maps Local Guide's Reviews
• Export a Google Reviewer's Reviews as JSON
• Vet a Google Reviewer: Spot Fake-Review Signals
• Export a Google Reviewer's Reviews to CSV

Last Updated: 2026.06.30