Stay organized with collections Save and categorize content based on your preferences.
IntroductionThe Places API is a service that accepts HTTP requests for location data through a variety of methods. It returns formatted location data and imagery about establishments, geographic locations, or prominent points of interest.
Note: Google Maps Platform provides separate versions of the Places library for Android, iOS, and JavaScript. We recommend that you use the version of the Places library specific to your platform. That is, if you are developing an Android app, you should use the Android version of Places. Why use the Places API (New)Create location-aware features to make detailed location data available to your users. The data available through the Places API (New) is built on one of the most accurate, up-to-date, and comprehensive place models of the real world. Here are example use cases for applications:
You can use the Places API (New) to include the following features in your applications:
Many Google Maps Platform APIs support place IDs, where the place ID uniquely identifies a place in the Google Places database and on Google Maps. There are many ways to obtain a place ID, including from the Places API (New), but also from the Geocoding API, Routes API, and Address Validation API.
Once you have a place ID, you can use the Places API (New) to request more details about a particular establishment or point of interest, such as its complete address, phone number, user rating, and reviews.
How the Places API (New) worksPlaces API (New) accepts requests as a standard URL with a specific service endpoint, such as /places or places:searchText and returns a JSON response. Places API (New) supports authorization by API key and OAuth token. The following example makes a Place Details (New) request to return the address components for a place ID using an API key:
https://places.googleapis.com/v1/places/GyuEmsRBfy61i59si0?fields=addressComponents&key=YOUR_API_KEYHow to use the Places API (New)
The steps below cover a typical use case scenario for using the Places API service. As you build out your solution, you can use additional endpoints, such as Nearby Search (New) and Place Photos (New).
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-14 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["The Places API provides location data and imagery for establishments, geographic locations, and points of interest through various methods."],["You can use the Places API to create location-aware features, such as place search, autocomplete, details retrieval, and photo integration."],["The Places API offers two versions: Places API and Places API (New), with differences outlined in a guide for choosing the best fit for your project."],["You can access places data through requests to specific service endpoints using an API key or OAuth token, receiving responses in JSON or XML format."],["Detailed steps for using the API include setup, text search, place details retrieval using place IDs, and accessing place photos."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4