> For the complete documentation index, see [llms.txt](https://doc.thordata.com/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.thordata.com/doc/scraping/serp-api/query-parameters/google/goole-patents.md).

# Goole Patents

#### SERP API Google Query Parameters

Configure Google search queries using Thordata’s SERP API, including Date Range parameters, Participants, 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_patents" \
 -d "q=pizza" \
 -d "json=1"
```

</details>

## Date Range

<details>

<summary><strong><code>before</code>,</strong>Date before<strong>(Optional)</strong></summary>

The parameter limits the latest date of the results. The format of this field is "type:`YYYYMMDD`", where type can be priority date (`priority`), application date (`filing`), or publication date (`publication`).

Example:

`priority:20241231`

`filing:20250615`

`publication:20250101`

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark> ,`before`:priority:20241231

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

</details>

<details>

<summary><strong><code>after</code> ,</strong>Date after<strong>(Optional)</strong></summary>

The number is used to limit the results to the earliest date. The format of this field is "type:`YYYYMMDD`", where type can be priority date (`priority`), application date (`filing`), or publication date (`publication`).

Example:

`priority:20241231`

`filing:20250615`

`publication:20250101`

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`after`: filing:20250615

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

</details>

## Participants

<details>

<summary><code>inventor</code>,Inventors<strong>(Optional)</strong></summary>

The parameter defines the inventor of the patent. Multiple inventors are separated by commas using `,`.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`location`:<mark style="color:blue;">India</mark>,`inventor`:A,B

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

</details>

<details>

<summary><code>assignee</code> <strong>,</strong>Assignees<strong>(Optional)</strong></summary>

The parameter defines the assignee of the patent. Multiple assignees are separated by commas using `,`.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`location`:<mark style="color:blue;">India</mark>,`assignee`:A,B

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

</details>

## Pagination

<details>

<summary><strong><code>page</code> ,</strong>Page number<strong>(Optional)</strong></summary>

Parameter defines the result offset. It skips the given number of results. It's used for pagination. (e.g., `0` (default) is the first page of results, `10` is the 2nd page of results, `20` is the 3rd page of results, etc.).

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`page`:<mark style="color:blue;">30</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_patents" \
 -d "q=pizza" \
 -d "json=1" \
 -d "page=30"
```

</details>

<details>

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

This parameter defines the maximum number of results returned per page in the search results. For example, setting it to 10 means 10 results will be returned.

**Example Request:**

Example results for `q` : <mark style="color:blue;">pizza</mark>,`num`:<mark style="color:blue;">20</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_patents" \
 -d "q=pizza" \
 -d "json=1" \
 -d "num=20"
```

</details>

## Advanced Parameters

<details>

<summary><code>sort</code><strong>,</strong>Sort By<strong>(Optional)</strong></summary>

Parameter defines the sorting method. By default, the results are sorted by Relevance.\
List of supported values are:\
`new` - Newest\
`old` - Oldest

**Example Request:**

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

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

</details>

<details>

<summary><code>clustered</code> <strong>,</strong>Group by<strong>(Optional)</strong></summary>

Parameter defines how the results should be grouped.\
List of supported values are:\
`true` - Classification

**Example Request:**

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

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

</details>

<details>

<summary><code>dups</code> <strong>,</strong>Deduplicate by<strong>(Optional)</strong></summary>

\
Parameter defines the method of deduplication. Either Family (default) or Publication.\
List of supported values are:\
`language` - Publication

**Code Example:**

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

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

</details>

<details>

<summary><code>patents</code> <strong>,</strong>Include Patents results<strong>(Optional)</strong></summary>

This parameter controls whether to include `Google Patents` search results. (Default is `true`)

**Code Example:**

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

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

</details>

<details>

<summary><code>scholar</code><strong>,</strong>Include Scholar results<strong>(Optional)</strong></summary>

Parameter controls whether or not to include Google Scholar results. (Defaults to false)

**Code Example:**

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

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

</details>

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