What this API is and who it is for
Google Map Places (New V2) surfaces Google's next-generation Places API through a marketplace intermediary, letting developers call the same underlying Google data at a lower cost per request than they would incur by billing directly through Google Cloud. The API exposes five endpoints that together cover the full places workflow: discovery by proximity, discovery by text query, structured place data retrieval, photo access, and autocomplete for search inputs.
The target audience is broad: any developer building a consumer app, internal tool, or data pipeline that needs reliable location information — restaurant finders, real-estate explorers, delivery logistics dashboards, travel itinerary tools — will find the endpoint set familiar and complete. Because the data source is Google Maps, coverage and freshness expectations are those of the Google Places platform, not a niche third-party database.
Endpoint walkthrough
All five endpoints follow Google's v1 Places API path convention, which means response shapes and field masks work exactly as documented by Google's own Places (New) reference.
POST /v1/places:searchNearby — Nearby Search
Accepts one or more place types and a geographic area, returning matching establishments within that boundary. This is the right call when you already know a coordinate and want to surface what is around it — think