> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/google-play/suggestions>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/google-play/suggestions.mdx>

---

# Google Play Suggestions API

The searches Google Play suggests for the start of a query, in any language.

`GET /v1/google-play/suggestions` takes a `query` (the start of a search, such as `spot`), an optional `country` and `language`. `data.suggestions` lists the searches the store suggests, best first, usually up to 5. `data.lookupStatus` is `found` when there is at least one and `no_data` when there is none.

Suggestions follow the language far more than the country, so set `language` to the market you are researching.

## Request

- **Endpoint:** `GET /v1/google-play/suggestions`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by partial query
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/google-play/suggestions/get)
- **Platform page:** [/platforms/google-play](https://www.socialfetch.dev/platforms/google-play)

## FAQ

### What is this useful for?

Keyword research for app store optimisation: the suggestions are the searches people start typing.

### How many credits does it cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.

### Why are suggestions the same in two countries?

They follow the language more than the storefront. Change language to see another market's suggestions.

### What if nothing is suggested?

lookupStatus is no_data and suggestions is empty.
