AI-generated Key Takeaways
-
Google Maps Platform Places SDK for iOS pricing is based on SKUs (product identifiers) for each API request and volume tiers.
-
Autocomplete requests without a session token or abandoned sessions are billed per request.
-
Place Details requests incur charges based on the data fields requested (Basic, Contact, Atmosphere).
-
Using Field Masks to retrieve only necessary data fields can optimize costs.
-
Session tokens should be used to manage Autocomplete sessions and avoid unnecessary charges.
Places SDK for iOS requests for the Places API are billed by SKU. 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.
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 iOS
The following table shows the SKU details and pricing for the Places SDK for iOS.
Usage limits
To review and manage your quotas and usage limits, see Quotas and quota alerts.
The Places SDK for iOS (New) queries the Places API (New), and the Places SDK for iOS (Legacy) queries the Places API. Quota limits configured on the Places API (New) and Places API apply to the requests from the corresponding SDK.
- Places API (New): The limit per minute is per API method per project. This means that each API method has a separate quota.
- Places API: the limit is per project. All methods on the Places API share the same quota.
- The limit per minute is calculated as the sum of SDK and server-side requests for all applications using the credentials of the same project.
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.
To modify a quota value for your API, follow these steps:
- In the Cloud console, navigate to Google Maps Platform > Quotas.
- Select the API for which you want to modify the quota.
- Identify the quota value that you want to change, and select it using the checkbox.
- Click Edit, enter a new quota value, and click Submit request.
View quota increase requests
To view all quota increase requests, including past and pending requests:
- In the Cloud console, navigate to Google Maps Platform > Quotas.
- Select the API for which you want to view the quota increase request.
- Click Increase Requests.
Terms of Use restrictions
For information on terms of use, see the License Restrictions section of the Google Maps Platform Terms of Service.