Session tokens

Session tokens are user-generated strings 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.

Session tokens terminate in the following ways:

• Place Details (New) is called.
• Address Validation is called.
• The session is abandoned.

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.