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
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/google-maps-extractor/business-reviews 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'
Query Result
Use Cases
- New-review alerts for client and competitor locations, reading pages until the first review already stored and notifying on low ratings
- One-off backfill of a business's review history into a database for sentiment and topic analysis
- Complaint keyword mining such as wait time, price or cleanliness across all branches of a multi-location brand
- Rating-drift reports that compare the newest 50 reviews against last month's snapshot for each location
- Review datasets for NLP training or evaluation, with the language chosen per request
- Reply-gap audits that list reviews whose owner_response_text is empty so a support team can answer them
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.