Fetch Google Maps reviews for one business, with ratings, reviewer fields, owner replies and cursor paging.

View all Google Maps Data API: Business Search, Reviews & Photos endpoints →

Returns a page of Google Maps reviews for one business. Send the required business_id (Google Maps ID, CID or place ID) and optionally country, lang, limit (default 20), next_page_token and sort_by. The response is a JSON object with status (true on success), request_id, a data array of reviews, next_token for the following page and the echoed request_params. In a live test call with limit=5, data held 5 reviews and next_token was a string. Each review had id, text, translated_text, time (relative text such as "4 months ago"), timestamp (Unix seconds), url, rating (3 and 5 were seen), language, language_translated_text, source (Google), a photos list with thumbnail_url, full_photo_url, width, height and aspect_ratio, rating_breakdown entries (id, question, rating), question_breakdown entries (id, question, answer, explanation), reviewer fields (user_id, user_name, user_avatar, user_profile_url, user_reviews_count, user_images_count, user_reviews_url, user_is_local_guide, user_local_guide_level) and owner_response_* fields, which were all null in the sample. To read the next page, send the returned next_token value as next_page_token. Accepted sort_by values are not documented and were not tested. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.

API Features

Reviews for any business ID One GET with a Google Maps ID, CID or place ID returns a page of reviews, so there is no need to open the place page or scroll the reviews panel.
Rating and text per review Each review has a rating, text, language and source, and the test call also showed a translated_text field, which was null in all five sample rows.
Cursor paging with next_token The response returns next_token, which is sent back as next_page_token to read the following page, so a review history can be walked page by page.
Adjustable page size The limit parameter defaults to 20, and the test call with limit=5 returned five reviews. The maximum accepted limit is not documented.
Reviewer profile fields Reviewer name, avatar, profile URL, review and photo counts and Local Guide flags come with each review and help weigh how much experience the author has.
Aspect ratings and Q&A answers rating_breakdown and question_breakdown arrays carry per-aspect scores such as Food and answers such as reservation advice where Google Maps shows them.
Photos and owner replies in the row Review photos arrive with thumbnail and full-size URLs, and owner_response_* fields are present so replied reviews can be separated from unanswered ones.

Live API Demo

GET /api/project/google-maps-extractor/business-reviews

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/google-maps-extractor/business-reviews?key=<API_KEY>&business_id=0x80c2c621d7d91b49%3A0x5e3e80cfbddfba70&limit=20'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the business reviews endpoint return?

A JSON object with status, request_id, a data array of reviews, next_token and the echoed request_params. In a live test call with limit=5, data held five reviews, each with rating, text, time, timestamp, language, reviewer fields, photos and owner_response_* fields.

How do I get more than the first page of reviews?

Take next_token from the response and send it as next_page_token in the next call, keeping business_id and the other inputs the same. The parameter is named next_page_token but the response field is next_token. The test call fetched only the first page, so repeat until your own stop condition.

How do I know when I have reached the last page?

The documentation says a token is returned when more reviews exist. What the last page looks like (missing, null or empty next_token) was not observed in the test call, so stop when data is empty or next_token is not a nonempty string.

What values does sort_by accept?

The documentation only describes it as the sorting criteria for reviews and does not list the allowed values. The test call did not use sort_by, so confirm a value on a small request before relying on it, for example for newest-first monitoring.

What is the difference between time and timestamp?

time is relative text such as "4 months ago", while timestamp is a Unix time in seconds. Use timestamp, or the review id, for sorting and de-duplicating stored reviews.

Are owner replies and translations always filled in?

No. In the test call every owner_response_* field and translated_text was null, so treat them as optional and null-check them. Whether they are populated for reviews that do have an owner reply or a translation was not seen.

Which parameters are required, and what are the defaults?

Only business_id is required; the sample form uses 0x80c2c621d7d91b49:0x5e3e80cfbddfba70. limit defaults to 20 and next_page_token defaults to an empty string. country, lang and sort_by are optional and their accepted values are not enumerated in the documentation.

Related operations

Guides

View Subscription Plans →