Skip to documentation
Browse documentation

Search nearby

Discover places around a coordinate, nearest first, each with its distance in meters. Places Google returns beyond the radius are dropped and counted in the summary; optional query and type terms narrow the search.

Capability ID googlemaps.nearby
Maximum runtime 120 seconds
View raw

POST /execute Shared execution endpoint

Input parameters

country string optional

Two-letter country code (default 'us'). Default: `us`.

include_exclusion_summary boolean optional

Include counts of fetched places rejected for being outside the radius or missing usable coordinates (default true). These counts do not describe all places in the area. Default: `true`.

lang string optional

Language code such as 'en' or 'en-US' (default 'en'). Default: `en`.

lat number required

Latitude (required). From -90 to 90.

Example 37.7749
limit integer optional

Max results (default 60, max 120). From 1 to 120. Default: `60`.

Example 20
lng number required

Longitude (required). From -180 to 180.

Example -122.4194
query string optional

Search terms, e.g. 'coffee'. Combined with any type terms.

Example coffee
radius integer optional

Search radius in meters (default 1000). Results farther than this are dropped; results are sorted nearest first with distance_m. From 1 to 50000. Default: `1000`.

Example 500
types array<string> optional

Additional type terms combined into the search query, e.g. ['restaurant'].

Response

Successful output is returned in results[0].data.

Raw platform output is intentionally open-ended and may evolve with the upstream source.

Illustrative sample The example response is shown in the response panel.

Illustrative output fields

Values illustrate one response. Read the guidance above for missing values and limits; fields can vary with the requested operation and the data available.

PathObserved typeExample
items array 3 items
items array 3 items
summary object 3 fields
summary.has_more boolean true
summary.query string coffee
summary.total_items integer 20

Execution behavior

A 200 response completed inline. A 202 response was queued; poll GET /jobs/:id until the job reaches completed or failed.