/patentscope/patents/search

POST /api/patentscope/patents/search

Price: 10 credits

Search WIPO PATENTSCOPE patent collections

How to use it

Search WIPO PATENTSCOPE (international PCT/WO + national patent collections). Combine any of the filters (applicant, inventor, title, ipc, cpc, country, application_number, publication_number, grant_number and application/publication/priority/grant date ranges in YYYYMMDD), or pass a raw CQL expression via query. All provided filters are combined with AND. Order results by relevance (default) or by publication/application date via sort. Returns each match's doc_id, publication number, title, country, publication date, IPC, application number, applicant, inventor and abstract. Feed doc_id into patentscope/patents for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free keyword or raw CQL expression to combine with the other filters (examples: "quantum")
• applicant string nullable — Applicant / owner name (examples: "IBM", "Google")
• inventor string nullable — Inventor name (examples: "Hassabis")
• patent_title string nullable — Words in the patent title (examples: "neural network")
• ipc string nullable — IPC classification symbol (examples: "G06N", "H04L 9/32")
• cpc string nullable — CPC classification symbol (examples: "G06N3/04")
• country string nullable — Two-letter office / country code (examples: "US", "EP")
• application_number string nullable — Application number (examples: "93110696")
• publication_number string nullable — Publication number (as printed, without country prefix) (examples: "0594947")
• grant_number string nullable — Grant number
• application_date_from string nullable — Earliest application date (YYYYMMDD) (examples: "20200101")
• application_date_to string nullable — Latest application date (YYYYMMDD) (examples: "20201231")
• publication_date_from string nullable — Earliest publication date (YYYYMMDD)
• publication_date_to string nullable — Latest publication date (YYYYMMDD)
• priority_date_from string nullable — Earliest priority date (YYYYMMDD)
• priority_date_to string nullable — Latest priority date (YYYYMMDD)
• grant_date_from string nullable — Earliest grant date (YYYYMMDD)
• grant_date_to string nullable — Latest grant date (YYYYMMDD)
• lang string — Language used to match the title filter (default: "en"; one of: "en", "fr", "de", "es", "pt", "ru", "ja", "zh", "ko", "ar")
• sort string — Result ordering (default: "relevance"; one of: "relevance", "publication_date_desc", "publication_date_asc", "application_date_desc", "application_date_asc")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "PatentscopeSearchItem")
• doc_id string required
• publication_number string nullable
• country_code string nullable
• publication_date string nullable
• ipc array (default: [])
• application_number string nullable
• applicant string nullable
• inventor string nullable
• abstract string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 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 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 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 Wait at least 30 seconds, then retry.

Response 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.