[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[[["\u003cp\u003eSession 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.\u003c/p\u003e\n"],["\u003cp\u003eSession tokens must be URL- and filename-safe base64 strings, with Google recommending the use of version 4 universally unique identifiers (UUIDs).\u003c/p\u003e\n"],["\u003cp\u003eA session begins with an Autocomplete (New) call, allowing for multiple queries within the session before concluding with Place Details (New) or Address Validation.\u003c/p\u003e\n"],["\u003cp\u003eEach 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.\u003c/p\u003e\n"],["\u003cp\u003eOmitting or reusing session tokens results in individual request billing, while fresh tokens are required for each new session to leverage session-based pricing.\u003c/p\u003e\n"]]],["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"],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/web-service/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/web-service/place-details) 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/web-service/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/web-service/session-pricing)."]]
