Google Places reference
Google Places API guide
Resolve a place from a text query, then use the returned place ID for details and available reviews. Match address and locality before analysing a similarly named business.
Quickstart
Start with Google Places
Resolve a place from a text query, then use the returned place ID for details and available reviews. Match address and locality before analysing a similarly named business.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Find a place
Select a result by identity and address; retain its place ID. Parameters and current cost →
curl "https://www.monocrawl.com/v1/google_places/search?query=coffee%20in%20Worthing&limit=5" \ -H "x-api-key: mn_your_key_here"
2. Read its details
Replace the example id with the chosen place ID. Parameters and current cost →
curl "https://www.monocrawl.com/v1/google_places/place?id=ChIJl1wfOSCjdUgRhrFnqMsMhQM" \ -H "x-api-key: mn_your_key_here"
3. Read available reviews
Use that same place ID. Returned reviews are a bounded source sample, not all reviews implied by an aggregate count. Parameters and current cost →
curl "https://www.monocrawl.com/v1/google_places/reviews?id=ChIJl1wfOSCjdUgRhrFnqMsMhQM" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Result bounds | Text search limit is 1–20. The declared search contract does not expose a cursor; a result page is not an exhaustive business directory. Endpoint reference → |
| Place identity | Use the place ID from the selected search result. Match address and locality when names repeat. Endpoint reference → |
| Review sample | No public cursor or exhaustive-review contract is declared here. Preserve the source sample and its attribution rather than extrapolating it to all customers. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| A known place | place | Avoid another text search when you already have its ID. |
| Review text | reviews | Keep review time, rating and source attribution when available. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Search and discovery
Reviews and offers
Operations
Google Places
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Google Places
8 operationsElsewhere
The same registry, other shapes
- Google Places overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=google_places— the same rows to your code at runtime, for 0 credits.