Stay organized with collections Save and categorize content based on your preferences.
Reminder: To use the Places API, you must enable billing on each of your projects and include an API key or OAuth token with all API or SDK requests. About field masksFor Place Details (New), Nearby Search (New), and Text Search (New), use the FieldMask header in API requests to specify the list of fields to return in the response. You are then billed at the highest SKU applicable to your request. That means if you select fields in both the Essentials and the Pro SKUs, you are billed based on the Pro SKU.
Using field masking is a good design practice to ensure that you don't request unnecessary data, which helps to avoid unnecessary processing time and billing charges.
About Autocomplete (New) sessionsAn Autocomplete (New) session includes one or more Autocomplete (New) requests, and a Place Details (New) request or Address Validation request. The same session token is passed to the Autocomplete (New) request and to the subsequent Place Details (New) request or Address Validation request.
A session starts with the first Autocomplete (New) request. A Place Details (New) request or Address Validation request is then made when the user has selected one of the Autocomplete (New) suggestions. If a session is abandoned, meaning no Place Details (New) request or Address Validation request is made, Autocomplete (New) requests are charged as if no session token was provided.
After a user has selected a place (meaning a Place Details (New) request or Address Validation request is made), you must start a new session using a new session token.
Note: Session tokens can overlap across projects, but they must be unique per project. For example, an app using Project A and an app using Project B can use the same session token, while multiple apps using Project A cannot use the same session token.A session token is good for one session and cannot be used for more than one session. If you reuse a session token, the session is considered invalid and the requests are charged as if no session token were provided.
SKU details and pricing for the Places APIThe following table shows the SKU details and pricing for the Places API.
Usage limitsTo review and manage your quotas and usage limits, see Quotas and quota alerts.
Places API (New): The rate limit per minute is per API method per project. Meaning each API method has a separate quota.
Places API (Legacy): The rate limit per minute is calculated as the sum of client-side and server-side requests for all applications using the credentials of the same project.
Quota limits define the maximum number of requests allowed for a specific API or service within a given timeframe. When the number of requests in your project reaches the quota limit, your service stops responding to requests.
Important: To understand how an increase in quota could affect your bill, check out the pricing calculator.To modify a quota value for your API, follow these steps:
To view all quota increase requests, including past and pending requests:
For information on terms of use, see policies for the Places API, and the License Restrictions section of the Google Maps Platform Terms of Service.
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."],[[["Google Places API uses a pay-as-you-go model with charges based on specific features (SKUs) used in requests."],["You receive a $200 monthly credit that automatically applies to eligible SKUs until February 28, 2025."],["Using field masks to specify only the data needed in your requests can help control costs."],["Autocomplete sessions, linking Autocomplete requests with Place Details or Address Validation requests, are currently free."],["Pricing varies by SKU and usage volume, with tiers adjusting based on the number of requests made per month."]]],["The Places API uses a pay-as-you-go model with SKUs for billing, including a $200 monthly credit until February 2025. Autocomplete sessions, using unique tokens, bundle requests and are cheaper than individual ones. `FieldMask` is used to limit charges and data retrieval. Place Details, Nearby, and Text Search SKUs are tiered (IDs Only, Location, Basic, Advanced, Preferred) based on the fields requested. Data SKUs are charged additionally. Photo requests have a different SKU and pricing. Billing is influenced by API requests and data fields requested.\n"]]
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