Google Maps Business Dataset Search API

Endpoint facts

Method

GET

API path

/datasets/google-map-businesses/search

Auth

apiKey

Credits

2 credits/request

Platform

Datasets

Response schema

#/definitions/datasets.googleMapBusinessesSearchResponseDoc

Overview

Searches Google Maps business records stored in a search index. Sort enum: `relevance`, `updated_at_desc`, `rating_desc`, `review_count_desc`, `distance_asc`. `category` is a Google Maps type token in lower-case snake_case (e.g. `dentist`, `bus_stop`, `atm`), both as the `category` filter and in each result's `category` field. A `rating` of `null` means no aggregate rating is available for that business (too few reviews, or a place type Google does not rate) — it is never a literal zero-star score; read it together with `review_count`, and note that `rating_desc` sorts unrated businesses last and `min_rating` above 0 excludes them. Use `has_geo=false` to isolate locationless service-area businesses (which have a `null` `geo`). Developers commonly use this endpoint for repeatable dataset search, filtering, facets, local business enrichment, analytics, exports, and internal tools that need structured records beyond the limited manual refinement available in the Google Maps app. Authentication uses the x-api-key header, usage is metered with the credit cost shown on this page, and the request does not trigger live scraping or proxy routing.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.

• Data source: stored Crawlora dataset records
• Proxy strategy: no proxy routing is applied
• Browser rendering: not used for dataset search or lookup requests
• Live scraping: not triggered by dataset list, search, nearby, facet, or detail endpoints
• Validation: invalid filters, coordinates, pagination, and enum values return documented errors
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Defaults to `relevance` sort when `q` is supplied. - Defaults to `updated_at_desc` sort when no `q` is supplied. - `lat` and `lon` must be supplied together. `distance_asc` requires `lat` and `lon`, but does not require `radius_m`. - The maximum result window is `10000`; `page * page_size` must not exceed `10000`. - A `null` `rating` in a result means no aggregate rating is available for that business (too few reviews, or a place type Google does not rate) — it is never a literal zero-star score. A present `rating` is always between `1.0` and `5.0`. Read it together with `review_count`; `rating_desc` sorts unrated (null) businesses last. - Invalid enum values return the standard invalid params envelope. - Does not trigger live scraping. Example response: ```json { "code": 200, "msg": "OK", "data": { "dataset": "google-map-businesses", "items": [ { "place_id": "ChIJ99URUeOAhYAR0J5ZUxTesDQ", "name": "Hotel Zephyr San Francisco", "category": ["hotel"], "rating": 4.1, "review_count": 3213 } ], "page": 1, "page_size": 20, "total": 1, "sort": "relevance" } } ```

Error behavior

Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.

When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.

Related