# /google/patents/patents/search

`POST /api/google/patents/patents/search`

Price: 10 credits

Search patents by query and filters

## How to use it

Search Google Patents by keyword query with optional filters: assignee, inventor, country/jurisdiction, grant status, document type, language, CPC classification, litigation presence, and a date range (before/after a priority, filing, or publication date). Results can be ordered by relevance or publication date, deduplicated by patent family or by individual publication, and optionally grouped into clusters of related patents. Returns a list of patents, each with publication number, title, snippet, first inventor, current assignee, priority/filing/grant/publication dates, language, PDF and thumbnail links, and the patent web URL.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `query` (string, required) — Search query (examples: "machine learning", "solar panel"; minLength: 1)
- `count` (integer, required) — Number of patents to return (min: 1)
- `assignee` (string, nullable) — Filter by patent assignee / owner
- `inventor` (string, nullable) — Filter by inventor
- `country` (array, nullable) — Filter by jurisdiction country codes (e.g. US, EP, WO, CN, JP, DE, KR)
- `status` (string, nullable) — Filter by grant status (one of: "GRANT", "APPLICATION")
- `type` (string, nullable) — Filter by document type (one of: "PATENT", "DESIGN")
- `language` (string, nullable) — Filter by document language (e.g. ENGLISH, GERMAN, CHINESE)
- `cpc` (string, nullable) — Filter by CPC classification code (e.g. G06N)
- `litigation` (string, nullable) — Filter by litigation presence (one of: "YES", "NO")
- `before` (string, nullable) — Upper date bound as YYYYMMDD, applied with before_type (pattern: ^\d{8}$)
- `after` (string, nullable) — Lower date bound as YYYYMMDD, applied with after_type (pattern: ^\d{8}$)
- `before_type` (string) — Which date the before bound applies to (default: "priority"; one of: "priority", "filing", "publication")
- `after_type` (string) — Which date the after bound applies to (default: "priority"; one of: "priority", "filing", "publication")
- `sort` (string) — Result ordering (default: "relevance"; one of: "relevance", "new", "old")
- `dedup` (string) — Deduplicate results by patent family (one representative per family) or by individual publication (default: "family"; one of: "family", "publication")
- `group_by_family` (boolean) — Re-cluster results by patent family upstream so related publications collapse together. Results are always returned as a flat list; the visible effect depends on the matched data. (default: false)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GooglePatentSearchResult")
- `id` (string, required)
- `snippet` (string, nullable)
- `inventor` (string, nullable)
- `assignee` (string, nullable)
- `priority_date` (string, nullable)
- `filing_date` (string, nullable)
- `grant_date` (string, nullable)
- `publication_date` (string, nullable)
- `language` (string, nullable)
- `pdf_url` (string, nullable)
- `thumbnail` (string, nullable)
- `web_url` (string) (default: "")

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.