google-maps/
reviews

The Google Maps Reviews API collects public reviews from known Google Maps URLs with normalized text, reviewer references, ratings, source links, timestamps, place references, and available media.

Google Maps Reviews API

Place reviews
Day-window filter
Normalized review records
0.15 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Google Maps Reviews

Google Maps reviews are public place feedback records that can include written text, a reviewer reference, a rating, source and subject links, publication and collection times, and media. They support source-linked feedback datasets and comparisons across known places or collection windows.

Google Maps Reviews API Features

  • Known-URL batch inputThe Google Maps Reviews API takes one or more supported google.com or goo.gl URLs in one asynchronous task instead of resolving places by a separate identifier API.
  • Optional day windowApply one positive days_limit value to every submitted URL row when the workflow needs a recent-review window.
  • Stable review recordsRead review identity, text, reviewer fields, rating, place references, timestamps, source URL, and available media through the review v1.0 schema.

Google Maps Reviews API Parameters

ParametersRequiredDescription
urlsRequiredOne or more non-empty URLs on google.com, any google.com subdomain, goo.gl, or a goo.gl subdomain, separated by commas or new lines. Use known Maps place URLs for review collection.
days_limitOptionalOptional positive integer applied to every provider input row as a review recency window. Omit it to send no day-window filter.
results_limitOptionalOptional integer from 1 through 2,000 that caps the total reviews stored for the task. It defaults to 100, and source availability can produce fewer rows.

How to Use the Google Maps Reviews API

Submit known Google Maps URLs to the Google Maps Reviews API, track the asynchronous task, and read the saved review records through the task result cursor.

  1. Prepare one or more supported Google Maps place URLs on google.com or goo.gl.
  2. POST urls and, when needed, days_limit and results_limit to /v1/google-maps/reviews.
  3. Poll /v1/tasks/{task_id} until status is succeeded or failed.
  4. Read /v1/tasks/{task_id}?limit=50 and continue with results.next_cursor while results.has_more is true.
curl -X POST "https://api.socq.ai/v1/google-maps/reviews" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.google.com/maps/place/Coffee%20Project%20New%20York%20%7C%20East%20Village/data=!4m7!3m6!1s0x89c2599b5a24d7fd:0x9e354f6cf514b9fc!8m2!3d40.7270884!4d-73.9893820!16s%2Fg%2F11c3svpqld!19sChIJ_dckWptZwokR_LkU9WxPNZ4?authuser=0&hl=en&rclk=1"],"days_limit":3650,"results_limit":3}'

# Poll GET /v1/tasks/{task_id}, then request
# GET /v1/tasks/{task_id}?limit=50&cursor={results.next_cursor}.

Google Maps Reviews API Use Cases

  • Known-place feedback datasets: Prepare review text, ratings, publication times, and source links for a defined set of public place URLs.
  • Source-aware reviewer research: Retain available reviewer names, usernames, profile links, and review URLs so records remain traceable to their public context.
  • Recent-window comparisons: Run the same place set through the Google Maps Reviews API with documented days_limit values at different times to compare bounded collections without claiming complete history.
  • Media-linked review archives: Keep available review media beside text, rating, place reference, and collection time in a normalized research record.

Google Maps Reviews API Pro Tips

  • Submit resolvable google.com or goo.gl Maps URLs; a place name, Google Business Profile account, or Place ID alone is not an accepted urls item.
  • Use days_limit only when a positive whole-number window is meaningful; omitting it leaves the provider row without that filter.
  • Treat results_limit as one global stored-result ceiling across the URL batch, not as a per-URL promise.
  • Keep the submission results_limit separate from the task-reading limit: the latter controls page size from 1 to 500 and uses an opaque cursor.
  • Allow text, reviewer attributes, rating, subject references, timestamps, and media to be absent when the public source does not expose them.

Beyond the Google Maps Reviews API, use these APIs when you need a different type of public Google Maps data.

Explore other platforms

Combine Google Maps data with public data from other supported social platforms.

Google Maps Reviews API — FAQ

Google Maps Reviews API is a programmatic interface for collecting public review records from known Google Maps URLs into a stable review schema. It returns only data available through the supported public collection path and does not provide logged-in Google Business Profile management actions.

The runtime accepts non-empty URLs whose host is google.com, a google.com subdomain, goo.gl, or a goo.gl subdomain. For useful review results, submit known Google Maps place URLs rather than names or standalone identifiers.

days_limit is optional and must be an integer of at least 1. When present, the provider adapter copies the same value onto every URL input row; when omitted, no days_limit field is sent.

results_limit defaults to 100 and accepts integers from 1 through 2,000. The provider request receives the cap and the runtime also stops storing rows when the task-wide total reaches it, so URL count, the day window, and public dataset availability can all produce fewer results.

The review v1.0 schema can contain id, platform, resource, type, url, published_at, collected_at, text, author, rating, subject_id, subject_url, and media. Author expands into identity, username, name, profile URL, avatar URL, and nullable account flags.

There is no base task charge. The request reserves 0.15 credits per estimated result using results_limit, or 100 when it is omitted, then settles at 0.15 credits for each result actually stored and refunds unused reserved credits; an empty result settles to zero.