Google Maps Platform Places API

Places API is useful when an application needs to turn a location-oriented query into structured place data. For example, a neighborhood guide could send a text search for vegetarian restaurants near a chosen point, apply a location bias, and request only each result's display name and formatted address. The official Text Search guide shows an HTTP POST to the Places endpoint, an API key header and a field-mask header. The response contains place records, and a next-page token can be used to retrieve another page.

Choose fields deliberately

A field mask is required; omitting it produces an error. It also determines which place fields come back and helps control processing and billing. Start with the smallest set needed for the screen, then add detail fields only when the interface needs them. Search supports a location bias that favors an area without guaranteeing results stay inside it, or a location restriction for certain categorical searches when results must remain within a defined rectangle. Google notes that a text search can return at most 60 results across pages and that repeated identical requests are not guaranteed to return a consistent list.

Account, policy and pricing

The product page offers a Maps Demo Key for prototyping without a credit card, while live Places requests use an API key and are governed by Maps Platform terms and attribution requirements. Google publishes both usage-based SKU pricing and monthly subscription plans; which SKU applies depends in part on the requested fields. The page also flags that product availability, functionality and terms can differ for customers billed in the European Economic Area. Check the current pricing and data-use requirements for the intended region and fields before relying on a cost estimate.