/kipris/patents/search

POST /api/kipris/patents/search

Price: 10 credits

Search Korean and foreign patent and utility model collections

How to use it

Search KIPRIS patent and utility model collections (the Korean IP office registry). Set collection to korea for Korean records or foreign for the mirrored US/EP/WO/JP/CN offices (choose offices). Combine any of the filters (query, title, abstract, applicant, inventor, agent, ipc, cpc, application_number, publication_number and application/publication date ranges in YYYYMMDD); all are combined with AND. Restrict Korean results to patents or utility models via category. Order by relevance (default) or application/publication/registration date. Returns each match's full bibliographic record including Korean and English titles and abstracts, classifications, applicants, inventors and legal status.

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 searched across title, abstract and claims (examples: "battery")
• invention_title string nullable — Words in the invention title (examples: "lithium battery")
• abstract string nullable — Words in the abstract
• applicant string nullable — Applicant / owner name (examples: "삼성전자", "Samsung")
• inventor string nullable — Inventor name
• agent string nullable — Patent agent / attorney name
• ipc string nullable — IPC classification symbol (examples: "H01M")
• cpc string nullable — CPC classification symbol (examples: "H01M4/88")
• application_number string nullable — Application number (examples: "1020130096423")
• publication_number string nullable — Publication (laid-open) 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)
• collection string — Which collection to search: Korean records or foreign offices (default: "korea"; one of: "korea", "foreign")
• category string nullable — Restrict Korean results to patents or utility models only (one of: "patent", "utility")
• offices array nullable — Foreign offices to include when collection is foreign (one of: "US", "EP", "WO", "JP", "CN")
• sort string — Result ordering (default: "relevance"; one of: "relevance", "application_date", "publication_date", "registration_date")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "KiprisPatent")
• id string required
• country_code string nullable
• category string nullable
• kind_code string nullable
• title_en string nullable
• abstract string nullable
• claims string nullable
• application_number string nullable
• application_date string nullable
• publication_number string nullable
• publication_date string nullable
• registration_number string nullable
• registration_date string nullable
• international_application_number string nullable
• international_publication_number string nullable
• legal_status string nullable
• legal_status_detail string nullable
• ipc array (default: [])
• cpc array (default: [])
• applicants array (default: [])
• applicants_en array (default: [])
• applicant_addresses array (default: [])
• inventors array (default: [])
• inventors_en array (default: [])
• inventor_addresses array (default: [])
• agents array (default: [])
• agents_en array (default: [])
• agent_addresses array (default: [])
• rights_holders array (default: [])
• rights_holders_en array (default: [])
• rights_holder_addresses array (default: [])
• priority_numbers array (default: [])
• family_members array (default: [])
• image 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.