# Bing Search API

#### SERP API Bing Query Parameters

including output options for parameters such as localization, geographical location, and pagination.

<details>

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

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

**Example Request:**

Example with `q`:<mark style="color:blue;">pizza</mark> parameter

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

</details>

## Localization

<details>

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

This parameter defines that during crawling, you can specify that search results be displayed according to the habits of users in a specific country/region. It is a two-letter country/region code (for example: `us`, `ru`, `uk`).

**Examples:**

* `cc=us` → United States (English)
* `cc=fr` → France (French)

**Example Request:**

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

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

</details>

## Geographical Location

<details>

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

This parameter defines the interface display language of search results during crawling. It adopts the format of <"language code">-<"country/region code">.&#x20;

For example, `en-US`. This string is case-insensitive.

**Examples:**

* `mkt=en-US` → English (United States)
* `mkt=zh-CN` → Simplified Chinese

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`mkt`:<mark style="color:blue;">fr-fr</mark>

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

</details>

<details>

<summary><strong><code>location</code> ,</strong>Location<strong>(Optional)</strong></summary>

This parameter defines the starting geographical location for crawling and should be used in conjunction with the `lat` (latitude) and `lon` (longitude) parameters.

**Example Request:**

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

```sh
curl -X POST https://scraperapi.thordata.com/request \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -H "Authorization: Bearer token" \
 -d "engine=bing" \
 -d "q=pizza" \
 -d "json=1" \
 -d "location=Tokyo%2CJapan" \
 -d "uule=w+CAIQICILVG9reW8sSmFwYW4"
```

</details>

<details>

<summary><strong><code>lat</code> ,</strong>Latitude<strong>(Optional)</strong></summary>

GPS latitude (-90.0 to 90.0). **Must be used with `lon`.**

This parameter defines the GPS latitude of the starting geographical location during crawling. It is used together with the `location` (geographical location) and `lon` (longitude) parameters.

**Example Request:**

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

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

</details>

<details>

<summary><strong><code>lon</code> ,</strong>Longitude<strong>(Optional)</strong></summary>

GPS longitude (-180.0 to 180.0). **Must be used with `lat`.**

This parameter defines the GPS longitude of the starting geographical location during crawling. It is used together with the `location` (geographical location) and `lat` (latitude) parameters.

**Example Request:**

Example: `-74.0060` for New York.

Example results for `q` : <mark style="color:blue;">pizza</mark>,`lon`:<mark style="color:blue;">-74.0060</mark>

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

</details>

## Pagination

<details>

<summary><strong><code>first</code> ,</strong>Result offset<strong>(Optional)</strong></summary>

Sets the result offset (default: `1`). For example, `first=10` skips the first 9 results.

This parameter is used to control the offset of Organic Search results, with a default value of 1. For example, when `first=10`, the system will promote the 10th organic search result to the top position.

**Example Request:**

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

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

</details>

<details>

<summary><strong><code>count</code> ,</strong>Results per page<strong>(Optional)</strong></summary>

Number of results per page (range: `1`–`50`). Use with `first` for pagination.

The per-page parameter is used to control the number of search results displayed per page (minimum value: 1, maximum value: 50). The actual effective value will be affected by the `first` offset parameter.

**Example Request:**

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

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

</details>

## Advanced Filters

<details>

<summary><strong><code>adlt</code> ,</strong>Safe<strong>(Optional)</strong></summary>

This parameter defines whether adult content is blocked from search results. You can set it to either "`strict`" or "`off`".

Adult content filter:

* `strict` → Default (blocks adult content)
* `off` → Allows adult content

**Example Request:**

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

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

</details>

**For assistance, contact <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/bing/bing-search-api.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.