For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to Fetch Google Maps Reviews from a Place URL

Google Maps reviews are one of the most useful sources for understanding customer feedback, local reputation, and competitor performance. But manually reading reviews from Google Maps does not work well when you need structured review data for dashboards, reports, or monitoring workflows.

Pullbay’s Google Maps Reviews endpoint lets you fetch reviews for a place using the full Google Maps place URL.

Important: Reviews Require placeUrl, Not fid

Endpoint

GET https://api.pullbay.com/google-maps/place/reviews

Authorization: Bearer YOUR_API_KEY

Parameters

Parameter
Type
Required
Description

placeUrl

string

Yes

Full Google Maps place URL

maxItems

integer

No

One-shot bulk pull, 1–500 results

cursor

string

No

Cursor returned by the previous response

maxItems and cursor are mutually exclusive. Use one or the other in a request.

Approaches

Use maxItems when you want a simple one-shot pull.

When to use this

Use this approach when you need up to 500 reviews in a single request and do not need to continue with cursor pagination.

The reviews endpoint uses cursor-style pagination. The response can include pagination.cursor. Pass that cursor in the next request to continue.

Useful Review Fields

A Google Maps review can include:

Field
Description

id

Review ID

link

Permalink to the review

text

Review body

stars

Rating from 1 to 5

date

Posted timestamp in Unix milliseconds

dateIso

Posted timestamp in ISO 8601 format

likes

Number of likes on the review, nullable

photos

Photo URLs attached to the review

reviewer.name

Reviewer display name

reviewer.url

Reviewer Google Maps profile URL

reviewer.totalReviews

Total reviews written by the reviewer

reviewer.totalPhotos

Total photos uploaded by the reviewer

ownersResponse

Owner response object, empty object when none

details

Free-form review metadata

Client-Side Filtering by Rating

The API does not document a server-side rating filter for reviews. If you want only low-rating reviews, fetch reviews first and filter by stars in your own code.

Export Reviews to CSV

Deduplication

If you fetch reviews repeatedly, store the review id and use it as a unique key.

Credit Considerations

Each request is billed independently. The exact credit charge is returned in:

Credit cost is dynamic, so read it from every response instead of assuming a fixed rate.

Troubleshooting

Problem
Possible Cause
Fix

400 Bad request

Missing or invalid placeUrl

Make sure you pass the full Google Maps place URL

400 Bad request

maxItems and cursor used together

Use only one per request

402 Insufficient credits

Not enough credits

Check Pullbay account credits

404 Not found

Review set not found

Verify the place URL

No cursor returned

No continuation cursor available

Stop pagination

Next Steps

After fetching Google Maps reviews, you can:

  • Store reviews in a database

  • Deduplicate reviews by id

  • Filter client-side by stars

  • Track new reviews over time

  • Combine reviews with place details from the fid endpoint

Last updated