Google Maps Data API: Business Search, Reviews & Photos APIs
Find businesses from a city name, keep the search center, then open details, reviews or photos only for the records you choose.
Open the business-search request demoSearch for attorneys in Philadelphia
Replace <API_KEY> with your platform API key. Keep real keys on your server and out of shared URLs and logs.
The example uses the observed public query attorney in Philadelphia, PA, USA with a requested limit of 5; every other input keeps its default. Copying or opening it sends no request, and current results can differ.
Base URL https://api.opendata-api.com
curl -X GET 'https://api.opendata-api.com/api/project/google-maps-extractor/locate-and-search?key=<API_KEY>&limit=5&offset=0&query=attorney+in+Philadelphia%2C+PA%2C+USA'import requests
response = requests.request(
"GET",
"https://api.opendata-api.com/api/project/google-maps-extractor/locate-and-search",
params={
"key": "<API_KEY>",
"limit": "5",
"offset": "0",
"query": "attorney in Philadelphia, PA, USA",
},
timeout=30,
)
response.raise_for_status()
print(response.json())const url = new URL("https://api.opendata-api.com/api/project/google-maps-extractor/locate-and-search");
url.search = new URLSearchParams({
"key": "<API_KEY>",
"limit": "5",
"offset": "0",
"query": "attorney in Philadelphia, PA, USA",
}).toString();
const response = await fetch(url, {
method: "GET",
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
console.log(await response.json());Keep the search center and request contract together
- Reuse inspected coordinates only while city, country and location intent remain unchanged. A center-based search is not a complete citywide count.
- Details, reviews and photos start from a business_id copied from a business row returned by a search, for example its google_id. Do not assemble an ID by hand or carry one over from another product.
- Photo and review responses return next_token, while requests take next_page_token. Keep tokens opaque, keep the business, language, limit and sort inputs identical on every page, and stop on a missing, unusable or repeated continuation.
- Autocomplete, reviews and photo operations use lang; details, location resolution and business searches use language. Nearby search does not accept limit, offset, zoom or radius.
Inspect search execution and location
Check the HTTP status and gateway code/message/data envelope first. Inside data, check the documented status before using the business list or location. A successful empty list is not an execution error.
Choose a location, search, detail, review or gallery task
- Discover businesses around a place
-
Start with a city-name combined search, or use a known coordinate pair for a nearby keyword search. Each returned row carries the business IDs that the later tasks need.
- Choose and inspect a search center
-
Autocomplete helps with partial text; query-locate resolves a location without returning a business list.
- Inspect one selected business
-
Use the business ID from a search row, read the result as one detail object, and expect optional attributes to be missing or null.
- Read bounded review pages
-
Select one business and read bounded pages. Carry the response next_token into the request next_page_token while business, language, limit and sort stay unchanged; the accepted sort values are not documented, so try one on a small page first.
- Explore a business photo gallery
-
Discover available photo categories before selecting a category hash; follow photo continuation only within a page budget.
Place Autocomplete
/api/project/google-maps-extractor/autocomplete Get place and address suggestions from a partial Google Maps search query.
Full docs βDetails
Returns the most relevant Google Maps search completions for a partial text query, intended for location-search typeahead. Send the required query string (for example "los ange") and optionally add country, lang and a lat/lng search center. The response is a JSON object with status (true on success), request_id, a data array of suggestions and the echoed request_params. In a live test call, the query "los ange" returned five suggestions, each with title, description, google_id, place_id, latitude, longitude, country and type; the type values seen were locality, establishment and geocode. The endpoint documentation also mentions street_address, administrative_area_level_1, route, transit_station and political types, but those were not seen in the test call and there is no type parameter, so filtering by type is done on the client. The google_id and place_id values use the same 0x...:0x... and ChIJ... formats that the business endpoints accept as business_id. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 4 optional inputs
| Parameter | In | Value |
|---|---|---|
| query |
Additional inputs for the selected operation (4)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Business Details
/api/project/google-maps-extractor/business-details Fetch the full Google Maps listing record for one business by ID, CID or place ID.
Full docs βDetails
Returns the detail record for a single Google Maps business. Send the required business_id as a Google Maps ID (0x...:0x... form), a numeric CID or a ChIJ... place ID, and optionally set country and language. The response is a JSON object with status (true on success), request_id, a data object and the echoed request_params. In a live test call (a hotel looked up by a 0x...:0x... ID), data included the identifiers google_id, google_mid, place_id and cid; name, status, address, full_address and a detailed_address breakdown (district, street, city, zip_code, state, country); main_category, category_id and categories; latitude, longitude, global_plus_code, compound_plus_code and time_zone; owner_name, owner_id and place_url; website_url, website_domain, phone and full_phone; and rating, reviews_count, reviews_per_rating, reviews_top_terms, reviews_sample, photos_sample and featured_photo. For that hotel, working_hours, popular_times, menu_url, reservation_url, order_online_url, price_range, competitors and posts_sample were null, while hotel_about, hotel_descriptions and hotel_stars were filled, so expect category-dependent fields to be null or absent for other business types. The CID and place ID input forms come from the endpoint documentation and were not used in the test call. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 2 optional inputs
| Parameter | In | Value |
|---|---|---|
| query |
Additional inputs for the selected operation (2)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Business Photos
/api/project/google-maps-extractor/business-photos List photos and videos for a Google Maps business with category filtering and cursor paging.
Full docs βDetails
Returns a page of photos and videos attached to one Google Maps business. Send the required business_id (Google Maps ID, CID or place ID) and optionally category (a category hash from the business photo categories endpoint), country, lang, limit (default 20) and next_page_token. The response is a JSON object with status (true on success), request_id, a data array, next_token for the following page and the echoed request_params. In a live test call with limit=5, data held 14 items (10 of type photo and 4 of type video), each with id, url, type, label, max_size (width and height), aspect_ratio, video_url, video_duration_ms, user_name, user_id, user_profile_url, user_avatar and upload_date_text; label is null for some items, and video_url and video_duration_ms are filled only for videos. Because the test call returned more items than the requested limit, treat limit as a page-size hint and trim on the client if you need an exact count. To fetch the next page, send the returned next_token value as next_page_token. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 5 optional inputs
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query | ||
| query | Optional continuation token: leave blank for the first page and reuse only a token from the same business and filter context. Do not expose it in URLs or logs. |
Additional inputs for the selected operation (2)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Photo Categories
/api/project/google-maps-extractor/business-photos-categories List the photo categories (gallery tabs) of a Google Maps business, each with a name and a hash.
Full docs βDetails
Returns the photo categories that a Google Maps business has in its gallery. Send the required business_id (Google Maps ID such as 0x...:0x..., a numeric CID or a ChIJ... place ID) and optionally country and lang. The response is a JSON object with status (true on success), request_id, a data array and the echoed request_params. In a live test call with only business_id, data held 12 entries, each with a name and a hash. The names seen were All, Menu, Food & drink, Vibe, five dish-specific tabs (Chimichanga, Cobb salad, Quesadilla, Egg roll, Margarita), By owner, Street View & 360 degrees and Videos, so the list is specific to the business and is not a fixed set. The endpoint documentation describes the hash as the value for the category parameter of the business photos endpoint; the test call did not chain the two requests. This endpoint returns categories only, never photos. The response example published with the endpoint is an empty object (and a validation error shape with detail entries for 422), so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 2 optional inputs
| Parameter | In | Value |
|---|---|---|
| query |
Additional inputs for the selected operation (2)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Business Reviews
/api/project/google-maps-extractor/business-reviews Fetch Google Maps reviews for one business, with ratings, reviewer fields, owner replies and cursor paging.
Full docs βDetails
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.
Send a request only when you choose to test 1 required inputs; 5 optional inputs
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query | Optional continuation token: leave blank for the first page and reuse only a token from the same business and filter context. Do not expose it in URLs or logs. |
Additional inputs for the selected operation (3)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Place Search
/api/project/google-maps-extractor/locate-and-search Search Google Maps businesses from a free-text query such as a trade and a city, with the resolved location returned.
Full docs βDetails
Resolves a free-text query to a map location and then lists the businesses found around it, in a single request. Send the required query (for example "attorney in Philadelphia, PA, USA") and optionally country, language, limit (default 20), offset (default 0) and zoom (3 zoomed out to 21 zoomed in). The response is a JSON object with status (true on success), request_id, a data array of places, a location object and the echoed request_params. In a live test call with limit=5, data held 5 places, each with 37 fields: google_id, google_mid, place_id, cid, name, status (OPEN in all five), address, full_address, a detailed_address object (district, street, city, zip_code, state, country), main_category, category_id, categories, latitude, longitude, time_zone, phone, full_phone, website_url, website_domain, working_hours by weekday, rating, reviews_count, featured_photo, about attribute groups, owner fields and hotel, price and reservation fields that were null for the sampled law firms. The location object had id, name, altitude, latitude, longitude and zoom, with id and name null and zoom 7. The documentation says this method combines the query locate and search nearby operations and recommends reusing the returned location with search nearby when the same area is queried repeatedly. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 5 optional inputs
| Parameter | In | Value |
|---|---|---|
| query | ||
| query |
Additional inputs for the selected operation (4)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Location Lookup
/api/project/google-maps-extractor/query-locate Resolve a free-text Google Maps query such as a city or a trade plus a place into latitude, longitude and zoom.
Full docs βDetails
Given a text query, returns the most relevant GPS coordinates for it as a single location object. Send the required query, either general such as "restaurant in New York City" or specific such as "New York City, NY, USA", and optionally add country, language, lat, lng and zoom (3 zoomed out to 21 zoomed in, per the endpoint documentation). The documentation says a query like "restaurant in New York" resolves to the coordinates of New York, so the result is the point for the place the query names, not a list of businesses. The response is a JSON object with status (true on success), request_id, a location object and the echoed request_params. In a live test call with only query set to "attorney in Philadelphia, PA, USA", location held id and name (both null), altitude (97787.43; the unit is not documented), latitude (39.9525839), longitude (-75.1652215) and zoom (7), and request_params echoed just the query. The documentation says status is false on failure, but no failed call was captured. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 5 optional inputs
| Parameter | In | Value |
|---|---|---|
| query |
Additional inputs for the selected operation (5)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query | ||
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Nearby Search
/api/project/google-maps-extractor/search-nearby List Google Maps businesses around a latitude and longitude for a search query such as a trade, with address, contact and rating fields.
Full docs βDetails
Searches for places near a given search center. Send the required query (for example "attorney") and optionally lat and lng for the center (the sample form uses 39.9525839 and -75.1652215), plus country and language codes. The response is a JSON object with status (true on success), request_id, a data array of places and the echoed request_params. In a live test call with query=attorney and the sample coordinates, data held 20 places, each with 37 fields: google_id, google_mid, place_id, cid, name, status (OPEN in all 20), address, full_address, a detailed_address object (district, street, city, zip_code, state, country), main_category, category_id, categories, latitude, longitude, time_zone, phone, full_phone, website_url, website_domain, reservation_url, reservation_domain, working_hours by weekday, rating, reviews_count, featured_photo, about attribute groups, can_claim and owner_name, owner_id and owner_profile_url. hotel_about, hotel_descriptions, hotel_stars, order_online_url, about_descriptions, price_range and price_breakdown were null for all 20 sampled law firms, and reservation_url was set for 8 of the 20. The echoed request_params held lat, lng and query as strings. There is no limit, offset, zoom or radius parameter on this endpoint, so the number of rows is not caller-controlled; the test call returned 20. The documentation says status is false on failure, but no failed call was captured. The response example published with the endpoint is an empty object, so the fields above come from the live test call only.
Send a request only when you choose to test 1 required inputs; 4 optional inputs
| Parameter | In | Value |
|---|---|---|
| query | ||
| query | ||
| query |
Additional inputs for the selected operation (2)
| Parameter | In | Value |
|---|---|---|
| query | ||
| query |
Request cost is temporarily unavailable. No price is assumed.
Local-business discovery capabilities
Pull Google Maps place data as structured JSON: turn a text query into coordinates, list businesses around a point, then use a business ID to read one place's details, photo categories, photos and reviews.
- Place search: free-text queries such as a trade plus a city return businesses together with the resolved location, or search around a latitude and longitude
- Location lookup: resolve a city or address phrase to coordinates and zoom, and fill search boxes with place and address autocomplete suggestions
- Business details: address, coordinates, phone, website, category, rating and review counts for one place by Google Maps ID, CID or place ID
- Reviews: ratings, review text, reviewer fields and owner replies, continued page by page with a cursor token
- Photos: gallery categories plus photos and videos, filtered by category and paged with a cursor token
Built for lead lists, review monitoring, store locators and local SEO checks without running a headless-browser scraper. Place lists return a limited number of rows per call, reviews and photos continue through next_token, and optional fields vary by business.