Os tokens de sessão são strings (ou objetos) gerados pelo usuário que rastreiam chamadas do Autocomplete (New) como sessões. O preenchimento automático (novo) usa tokens de sessão para agrupar as fases de consulta e seleção de uma pesquisa de preenchimento automático do usuário em uma sessão discreta para fins de faturamento.
Os usuários são responsáveis por criar tokens de sessão para cada sessão. Os tokens de sessão precisam ser strings base64 seguras para URL e nome de arquivo. Os usuários podem gerar tokens de sessão de qualquer maneira, mas o Google recomenda usar identificadores exclusivos universais (UUIDs) da versão 4 para tokens de sessão.
A sessão começa com uma chamada para o Autocomplete (New) e termina com uma chamada para Place Details (New) ou Address Validation. Cada sessão pode ter várias consultas do Autocomplete (New), seguidas por uma solicitação de Place Details (New) ou Address Validation. As chaves de API usadas em cada solicitação em uma sessão precisam pertencer ao mesmo projeto do Console do Google Cloud.
Os tokens de sessão terminam das seguintes maneiras:
O Place Details (novo) é chamado.
A Address Validation é chamada.
A sessão é abandonada.
Após a conclusão de uma sessão, o token perde a validade. Seu app precisa
gerar um novo token para cada sessão. Se o parâmetro sessionToken for omitido ou você reutilizar um token, a nova sessão vai ser cobrada como se nenhum token de sessão tivesse sido fornecido e cada solicitação será faturada separadamente.
[null,null,["Última atualização 2025-08-30 UTC."],[[["\u003cp\u003eSession tokens group Autocomplete (New) queries and their corresponding Place Details (New) or Address Validation calls into sessions for billing purposes.\u003c/p\u003e\n"],["\u003cp\u003eYou must generate a unique, URL-safe base64 session token (preferably a UUID) for each new user session.\u003c/p\u003e\n"],["\u003cp\u003eA session concludes when Place Details (New) or Address Validation is called, or if the session is abandoned.\u003c/p\u003e\n"],["\u003cp\u003eRequests without a session token or with a reused token are billed individually per request.\u003c/p\u003e\n"],["\u003cp\u003eEach request within a session must use API keys from the same Google Cloud Console project.\u003c/p\u003e\n"]]],["Session tokens, unique identifiers, group user autocomplete searches into sessions for billing. These tokens, which must be URL- and filename-safe base64 strings, are created by the user, with UUIDs recommended. A session begins with an Autocomplete (New) call and ends with Place Details (New) or Address Validation. Each session may include several Autocomplete (New) queries. Once terminated, a new token is required. Omitting or reusing a token results in individual billing for each request.\n"],null,["Select platform: [Android](/maps/documentation/places/android-sdk/place-session-tokens \"View this page for the Android platform docs.\") [iOS](/maps/documentation/places/ios-sdk/place-session-tokens \"View this page for the iOS platform docs.\") [JavaScript](/maps/documentation/javascript/session-pricing \"View this page for the JavaScript platform docs.\") [Web Service](/maps/documentation/places/web-service/place-session-tokens \"View this page for the Web Service platform docs.\")\n\n\u003cbr /\u003e\n\nSession tokens\n==============\n\nSession tokens are user-generated strings (or objects) that track [Autocomplete (New)](/maps/documentation/places/android-sdk/place-autocomplete)\ncalls as *sessions*. Autocomplete (New) uses session tokens to group the query\nand selection phases of a user autocomplete search into a discrete session for\nbilling purposes.\n\nUsers are responsible for creating session tokens for each session. Session\ntokens must be URL- and filename-safe base64 strings. Users can generate session\ntokens in any manner, although Google recommends using [version 4 universally\nunique identifiers (UUIDs)](https://tools.ietf.org/html/rfc4122) for session tokens.\n\nThe session begins with a call to Autocomplete (New), and concludes with a call\nto [Place Details (New)](/maps/documentation/places/android-sdk/details-place) or [Address Validation](/maps/documentation/address-validation/overview). Each session can have\nmultiple Autocomplete (New) queries, followed by one request to Place Details\n(New) or Address Validation. The API key(s) used for each request within a\nsession must belong to the same Google Cloud Console project.\n| **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)](/maps/documentation/places/android-sdk/autocomplete) 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.\n\nSession tokens terminate in the following ways:\n\n- Place Details (New) is called.\n- Address Validation is called.\n- The session is abandoned.\n\n| **Note:** You can optionally omit the Autocomplete (New) session token from a request. If the session token is omitted, each request is billed separately and charges the [SKU: Autocomplete Requests](/maps/billing-and-pricing/sku-details#places_autocomplete-request-new-ess-sku).\n\nOnce a session has concluded, the token is no longer valid; your app must\ngenerate a fresh token for each new session. If the `sessionToken` parameter is\nomitted, or if you reuse a session token, the new session is charged as if no\nsession token was provided (each request is billed separately).\n\nFor more information about how Autocomplete (New) requests are billed, see\n[Autocomplete (New) and session pricing](/maps/documentation/places/android-sdk/session-pricing)."]]
