Stay organized with collections
Save and categorize content based on your preferences.
About field masks
For 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) sessions
An 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.
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 API
The following table shows the SKU details and pricing for the Places API.
Places API (New): The rate limit per minute is
per API method per project. Meaning each API method
has a separate quota.
Places API: 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.
[[["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-05-06 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"]]
