/google/maps/places/search

POST /api/google/maps/places/search

Price: 3 credits

Search Google Maps places by text query. Returns places with name, address, rating, categories, GPS.

How to use it

Search Google Maps for places (businesses, points of interest) by free-text query. Returns name, feature_id, address, rating, review count, categories, coordinates. Use feature_id with the place, reviews, and photos endpoints.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search query (examples: "starbucks times square new york"; minLength: 1)
• count integer — Max number of results (default: 20; min: 1)
• latitude number nullable — Latitude to bias results toward; requires longitude (min: -90; max: 90)
• longitude number nullable — Longitude to bias results toward; requires latitude (min: -180; max: 180)
• zoom number nullable — Map zoom level controlling the search radius; requires latitude and longitude (min: 1; max: 21)

Response

• @type string (default: "GooglePlace")
• feature_id string required
• name string required
• place_id string nullable
• entity_id string nullable
• cid string nullable
• address string nullable
• city string nullable
• state string nullable
• postal_code string nullable
• country string nullable
• neighborhood string nullable
• latitude number nullable
• longitude number nullable
• timezone string nullable
• categories array (default: [])
• primary_category string nullable
• rating number nullable
• review_count integer nullable
• rating_distribution object nullable
  • @type string (default: "GooglePlaceRatingDistribution")
  • star_1 integer nullable
  • star_2 integer nullable
  • star_3 integer nullable
  • star_4 integer nullable
  • star_5 integer nullable
• price_level string nullable
• phone string nullable
• website string nullable
• domain string nullable
• description string nullable
• editorial_summary string nullable
• time_spent string nullable
• image string nullable
• menu_url string nullable
• is_claimed boolean (default: false)
• owner object nullable
  • @type string (default: "GooglePlaceOwner")
  • id string nullable
  • name string nullable
• hours array (default: [])
  • @type string (default: "GooglePlaceHours")
  • day string required
  • hours string nullable
• popular_times array (default: [])
  • @type string (default: "GooglePlacePopularTimes")
  • day string required
  • hours array (default: [])
    • @type string (default: "GooglePlacePopularHour")
    • hour integer nullable
    • busy_percent integer nullable
• attributes array (default: [])
  • @type string (default: "GooglePlaceAttributeGroup")
  • name string required
  • items array (default: [])
• actions array (default: [])
  • @type string (default: "GooglePlaceAction")
  • label string nullable
  • provider string nullable
  • url string required
• related_places array (default: [])
  • @type string (default: "GoogleRelatedPlace")
  • feature_id string nullable
  • name string nullable
  • primary_category string nullable
  • rating number nullable
• hotel object nullable
  • @type string (default: "GooglePlaceHotel")
  • hotel_class string nullable
  • price number nullable
  • offers array (default: [])
    • @type string (default: "GooglePlaceHotelOffer")
    • provider string nullable
    • price number nullable
    • url string nullable
• plus_code string nullable
• url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.