A RetroSearch Logo

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

Search Query:

Showing content from https://developers.google.com/maps/documentation/places/android-sdk/usage-and-billing below:

Places SDK for Android Usage and Billing

Skip to main content Places SDK for Android Usage and Billing

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

Reminder: To use the Places SDK for Android, you must include an API key with all API requests and you must enable billing on each of your projects.

Click the info info icon to see the table of contents for this page.

About Autocomplete (New) sessions

An Autocomplete (New) session includes one or more Autocomplete (New) requests, and a Place Details (New) request or Address Validation request. The same session token is passed to the Autocomplete (New) request and to the subsequent Place Details (New) request or Address Validation request.

A session starts with the first Autocomplete (New) request. A Place Details (New) request or Address Validation request is then made when the user has selected one of the Autocomplete (New) suggestions. If a session is abandoned, meaning no Place Details (New) request or Address Validation request is made, Autocomplete (New) requests are charged as if no session token was provided.

After a user has selected a place (meaning a Place Details (New) request or Address Validation request is made), you must start a new session using a new session token.

Note: Session tokens can overlap across projects, but they must be unique per project. For example, an app using Project A and an app using Project B can use the same session token, while multiple apps using Project A cannot use the same session token.

A session token is good for one session and cannot be used for more than one session. If you reuse a session token, the session is considered invalid and the requests are charged as if no session token were provided.

SKU details and pricing for the Places SDK for Android

The following table shows the SKU details and pricing for the Places SDK for Android.

Adjust quota

Quota limits define the maximum number of requests allowed for a specific API or service within a given timeframe. When the number of requests in your project reaches the quota limit, your service stops responding to requests.

Important: To understand how an increase in quota could affect your bill, check out the pricing calculator.

To modify a quota value for your API, follow these steps:

  1. In the Cloud console, navigate to Google Maps Platform > Quotas.
  2. Select the API for which you want to modify the quota.
  3. Identify the quota value that you want to change, and select it using the checkbox.
  4. Click Edit, enter a new quota value, and click Submit request.
View quota increase requests Important: You must have the appropriate IAM permissions to view quota increase requests.

To view all quota increase requests, including past and pending requests:

  1. In the Cloud console, navigate to Google Maps Platform > Quotas.
  2. Select the API for which you want to view the quota increase request.
  3. Click Increase Requests.
Tip: Make sure to monitor your quota usage regularly to avoid service interruptions. Learn more about quotas and quota alerts. Terms of Use restrictions

For information on terms of use, see the License Restrictions section of the Google Maps Platform Terms of Service.

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-08-14 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-08-14 UTC."],[[["The Places SDK for Android uses a pay-as-you-go pricing model based on SKUs for different features and data fields."],["Autocomplete sessions are billed differently depending on whether they include a Place Details request and session token usage."],["Data SKUs (Basic, Contact, Atmosphere) incur additional charges based on the fields requested, with Basic Data included in the base SKU cost."],["Field masks are crucial for cost optimization by specifying only the necessary data fields in requests."],["Daily quotas can be set to control API usage and prevent unexpected billing charges by managing requests for the Places SDK for Android."]]],[]]


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