# Goole Play

#### SERP API Google Query Parameters

Configure Google search queries using Thordata’s SERP API, including localization parameters, Play Store Categories, pagination, and "advanced parameter" output options.

<details>

<summary><strong><code>q</code> ,</strong>Search Query<strong>(Required)</strong></summary>

Define the search query used for data scraping (Default value: `q=pizza`). Any keywords in any language are supported.

**Example Request:**\
Example using the parameter `q`: pizza

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1"
```

</details>

## Localization

<details>

<summary><strong><code>gl</code> ,</strong>Country<strong>(Optional)</strong></summary>

Specify the target country/region for search results (default value: `us`). Use two-letter country codes(e.g., `us`, `ru`, `uk`).

For the complete list of supported country codes, please refer to: [Google’s Country List](https://developers.google.com/adwords/api/docs/appendix/geotargeting).

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`gl`: <mark style="color:blue;">ru</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "gl=ru" \
 -d "json=1"
```

</details>

<details>

<summary><strong><code>hl</code> ,</strong>Language<strong>(Optional)</strong></summary>

Set the interface language for search results (default value: `en`). Adopt standard language code formats (e.g., `en`, `es`, `zh-CN`).

For the complete list of supported language codes, please refer to: [Google Language Codes](https://developers.google.com/google-ads/api/docs/start).

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`hl`: <mark style="color:blue;">es</mark>

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "hl=es"
```

</details>

## Search Types

<details>

<summary><strong><code>apps_category</code> ,</strong>Apps Category<strong>(Optional)</strong></summary>

The parameter defines the app store category.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,**`apps_category`**:ANDROID\_WEAR

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "apps_category=ANDROID_WEAR"
```

</details>

## Pagination

<details>

<summary><strong><code>next_page_token</code>,</strong>Next Page Token<strong>(Optional)</strong></summary>

Parameter defines the next page token. It is used for retrieving the next page results. It shouldn't be used with the `section_page_token`, `see_more_token`, and `chart` parameters.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`next_page_token`:GAME

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "next_page_token=GAME"
```

</details>

<details>

<summary><strong><code>section_page_token</code> ,</strong>Section Page Token<strong>(Optional)</strong></summary>

Parameter defines the section page token used for retrieving the pagination results from individual sections. This parameter is a safer version of `see_more_token`, and is found in every row you can paginate into. It shouldn't be used with the `next_page_token`, `see_more_token`, and `chart` parameters

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,**`section_page_token`**:serpapi\_pagination.next\_page\_token

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "section_page_token=serpapi_pagination.next_page_token"
```

</details>

<details>

<summary><code>chart</code> <strong>,</strong>Chart<strong>(Optional)</strong></summary>

The parameter is used to display the top charts. It returns up to 50 results. Each store contains different charts and requires different values ​​to retrieve results. To get the value of a specific chart, you can use our Google Play app store API JSON output: (chart\_options\[index].value for example chart=topselling\_free). It should not be used with `section_page_token`, `see_more_token`, and `next_page_token` parameters.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`chart`:top\_free

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "chart=top_free"
```

</details>

<details>

<summary><code>see_more_token</code> <strong>,</strong>See more token<strong>(Optional)</strong></summary>

This parameter defines the 'see more' token used to retrieve individual partial paginated results. This token is typically found on the next page of results. It should not be used with `section_page_token`, `next_page_token`, and `chart` parameters.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,**`section_page_token`**:serpapi\_pagination.next\_page\_token

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "see_more_token=similar_apps"
```

</details>

## Advanced Parameters

<details>

<summary><code>store_device</code> <strong>,</strong>Device<strong>(Optional)</strong></summary>

The parameter defines the device to use for sorting results. This parameter cannot be used with the apps\_category or q parameters. Available options:

`phone` - Phone devices (default)

`tablet` - Tablet devices

`tv` - TV devices

`chromebook` - Chromebook devices

`watch` - Watch devices

`car` - Car devices

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`store_device`:`phone`

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "store_device=phone"
```

</details>

<details>

<summary><code>age</code> <strong>,</strong>Age<strong>(Optional)</strong></summary>

Parameter defines age subcategory. age works, and should only be used with apps\_category=FAMILY(Kids Apps)

It can be set to:

`AGE_RANGE1` - Ages up to 5

`AGE_RANGE2` - Ages 6-8

`AGE_RANGE3` - Ages 9-12

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`age`:AGE\_RANGE1

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=google_play" \
 -d "q=pizza" \
 -d "json=1" \
 -d "age=AGE_RANGE1"
```

</details>

For further assistance, contact us at **<support@thordata.com>**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.thordata.com/doc/scraping/serp-api/query-parameters/google/goole-play.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.