세션 토큰은 Autocomplete (New) 호출을 세션으로 추적하는 사용자 생성 문자열 (또는 객체)입니다. 자동 완성 (신규)은 세션 토큰을 사용하여 사용자 자동 완성 검색의 쿼리 및 선택 단계를 결제 목적의 개별 세션으로 그룹화합니다.
사용자는 각 세션의 세션 토큰을 만들어야 합니다. 세션 토큰은 URL 및 파일 이름 안전 base64 문자열이어야 합니다. 사용자는 어떤 방식으로든 세션 토큰을 생성할 수 있지만 Google에서는 세션 토큰에 버전 4 범용 고유 식별자 (UUID)를 사용하는 것이 좋습니다.
세션은 Autocomplete (New) 호출로 시작하고 Place Details (New) 또는 Address Validation 호출로 종료됩니다. 각 세션에는 여러 개의 Autocomplete (New) 쿼리가 포함될 수 있으며, 그 뒤에 Place Details (New) 또는 Address Validation에 대한 요청이 하나 포함됩니다. 세션 내 각 요청에 사용되는 API 키는 동일한 Google Cloud 콘솔 프로젝트에 속해야 합니다.
세션 토큰은 다음과 같은 방식으로 종료됩니다.
Place Details (New)가 호출됩니다.
주소 유효성 검사가 호출됩니다.
세션이 중단됩니다.
세션이 종료되면 토큰이 더 이상 유효하지 않습니다. 앱에서 각 새 세션에 대해 새 토큰을 생성해야 합니다. sessionToken 매개변수가 생략되거나 세션 토큰을 재사용하는 경우 새 세션에 대해 세션 토큰이 제공되지 않은 것처럼 요금이 청구됩니다 (각 요청에 대해 별도로 요금이 청구됨).
[null,null,["최종 업데이트: 2025-08-29(UTC)"],[[["\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)."]]
