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.
Features
- Known-URL batch inputSubmit 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 [email protected] schema.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | One 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_limit | Optional | Optional positive integer applied to every provider input row as a review recency window. Omit it to send no day-window filter. |
results_limit | Optional | Optional 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
Submit known Google Maps URLs, track the asynchronous task, and read the saved review records through the task result cursor.
- Prepare one or more supported Google Maps place URLs on google.com or goo.gl.
- POST urls and, when needed, days_limit and results_limit to /v1/google-maps/reviews.
- Poll /v1/tasks/{task_id} until status is succeeded or failed.
- 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}.Best 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 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.
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.
Related APIs
Use these APIs when you need a different type of public Google Maps data.
- Google Maps Search API — Search public Google Maps places by query and location with normalized identity, address, contact, rating, review-count, URL, and coordinate fields.
- Google Maps Place Details API