A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developers.google.com/maps/documentation/javascript/session-pricing below:

Autocomplete and session pricing | Maps JavaScript API

Autocomplete and session pricing

Stay organized with collections Save and categorize content based on your preferences.

Google recommends that you use sessions with Autocomplete (New). Sessions help simplify pricing and provide a consistent pricing model for use with Autocomplete (New).

Session pricing starts with the first Autocomplete (New) request that includes a session token, continues through each subsequent Autocomplete (New) request, and is then terminated by a request to Place Details (New) or Address Validation that uses the session token.

After the session terminates, any call to Autocomplete (New), Place Details (New), or Address Validation that uses the expired session token is billed as if there was no session token.

Incomplete sessions, meaning sessions that are not terminated by a request to Place Details (New) or Address Validation, are billed only for the autocomplete requests using the SKU: Autocomplete Requests.

The three most common pricing scenarios are:

Note: If you choose not to use sessions with Autocomplete (New), you are billed per-request to Autocomplete using the SKU: Autocomplete Requests. Autocomplete for location data

In this scenario, you are interested in using Autocomplete and Place Details (New) to obtain location information about a place. For example, you select a suggestion from autocomplete and then you use Place Details (New) to get the place's latitude and longitude coordinates to show that place on a map.

Location information can include the place's:

This session is terminated by a single request to Place Details (New) that requests any fields defined by the SKU: Place Details Essentials.

A session starts with the first Autocomplete (New) request that includes a session token, continues through each subsequent Autocomplete (New) request, and is then terminated by a request to Place Details (New) or Address Validation that uses the session token. For an Autocomplete (New) session, here is how you are billed:

Note: If you terminate the session by making a request to Place Details (New) using the Places API Place Details Essentials (IDs Only), then all requests to Autocomplete (New) are billed using the SKU: Autocomplete Requests, as if you did not use sessions. This is because the request using the Places API Place Details Essentials (IDs Only) is not charged, so all Autocomplete (New) requests revert to per-request pricing. Autocomplete for place discovery

In the Autocomplete for place discovery scenario, you are interested in obtaining more than just location data about a place. For example, you might request any of the following:

For this scenario, your session is terminated by a request to Place Details (New) that requests any fields included in the Place Details (New) Pro, Enterprise, or Enterprise + Atmosphere SKUs.

You are then billed as follows:

Autocomplete for checkout and delivery

The Address Validation API is a service that accepts an address. It identifies address components and validates them. It also standardizes the address for mailing and finds the best known latitude and longitude coordinates for it.

In the Autocomplete for checkout and delivery scenario, you terminate the session with a request to the Address Validation API to validate the selected address. You are then billed as follows:

Pricing examples Note: The examples on this page refer to SKUs that apply to users not in India. For India pricing, see Google Maps Platform pricing tables - India.

The following table shows pricing examples for the three main session scenarios. This table also lists the SKUs that appear in your billing statement for each scenario.

Pricing example without sessions

If you don't use sessions, you are billed per request to Autocomplete (New) using the SKU: Autocomplete Requests.

Fallback pricing for incomplete or abandoned sessions

If a session is abandoned, meaning not terminated by a call to Place Details (New) or Address Validation, Autocomplete (New) requests revert to the per-request pricing model and are billed per the SKU: Autocomplete Requests.

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-07-15 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-07-15 UTC."],[[["Google recommends using sessions with Place Autocomplete for simplified and consistent pricing."],["Sessions are initiated with the first Autocomplete request containing a session token and terminated by a Place Details request using the same token."],["Sessions enable discounted pricing for Autocomplete requests after the initial few and are billed differently based on the type of Place Details request terminating them (Location data, Place discovery, or Checkout and delivery)."],["If sessions are not used or are incomplete (not terminated by a Place Details request), Autocomplete requests are billed individually at a standard rate."],["Sessions cannot be shared between Places API endpoints and Places API (New) endpoints, limiting their use to specific sequences of requests within the same API version."]]],[]]


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