Stay organized with collections Save and categorize content based on your preferences.
Session tokensSession tokens are user-generated strings (or objects) that track Autocomplete (New) calls as sessions. Autocomplete (New) uses session tokens to group the query and selection phases of a user autocomplete search into a discrete session for billing purposes.
Users are responsible for creating session tokens for each session. Session tokens must be URL- and filename-safe base64 strings. Users can generate session tokens in any manner, although Google recommends using version 4 universally unique identifiers (UUIDs) for session tokens.
The session begins with a call to Autocomplete (New), and concludes with a call to Place Details (New) or Address Validation. Each session can have multiple Autocomplete (New) queries, followed by one request to Place Details (New) or Address Validation. The API key(s) used for each request within a session must belong to the same Google Cloud Console project.
Note: Session tokens cannot be exchanged between Places API (Legacy) endpoints and Places API (New) or Address Validation endpoints. For example, a Place Autocomplete (Legacy) request can be followed by a Place Details (Legacy) request in the same session, but it cannot be followed by a Place Details (New) request or an Address Validation request in the same session.Session tokens terminate in the following ways:
Once a session has concluded, the token is no longer valid; your app must generate a fresh token for each new session. If the sessionToken parameter is omitted, or if you reuse a session token, the new session is charged as if no session token was provided (each request is billed separately).
For more information about how Autocomplete (New) requests are billed, see Autocomplete (New) and session pricing.
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."],[[["Session tokens group Autocomplete (New) queries and selection phases into a session for billing purposes, ending with a call to Place Details (New) or Address Validation."],["Session tokens must be URL- and filename-safe base64 strings, with Google recommending the use of version 4 universally unique identifiers (UUIDs)."],["A session begins with an Autocomplete (New) call, allowing for multiple queries within the session before concluding with Place Details (New) or Address Validation."],["Each request within a session must utilize API keys associated with the same Google Cloud Console project, with sessions terminating upon calling Place Details (New), Address Validation, or abandonment."],["Omitting or reusing session tokens results in individual request billing, while fresh tokens are required for each new session to leverage session-based pricing."]]],["Session tokens, user-generated strings, track Autocomplete (New) calls as sessions for billing. Users create tokens, ideally UUIDs, for each session. A session starts with Autocomplete (New) and ends with Place Details (New) or Address Validation, allowing multiple Autocomplete queries. The API keys must be from the same project. Omitting the token or reusing it results in per-request billing. Session tokens are invalid after use and can not be exchanged between places API and places API (new) or Address Validation.\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