POST /api/kipris/patents
Price: 1 credit
Get a Korean patent or utility model record by application number
Get the full bibliographic record of a Korean patent or utility model from KIPRIS (the Korean IP office registry) by its application number. Returns the title and abstract (Korean and English), claims, IPC and CPC classifications, applicants, inventors, agents and rights holders (Korean and English) with their addresses, application/publication/registration numbers and dates, legal status, priority numbers and the representative drawing image.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)application_number string required — Korean patent or utility model application number (10-13 digits) (examples: "1020130096423")@type string (default: "KiprisPatent")id string requiredcountry_code string nullablecategory string nullablekind_code string nullabletitle_en string nullableabstract string nullableclaims string nullableapplication_number string nullableapplication_date string nullablepublication_number string nullablepublication_date string nullableregistration_number string nullableregistration_date string nullableinternational_application_number string nullableinternational_publication_number string nullablelegal_status string nullablelegal_status_detail string nullableipc 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 nullable422 — 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 — Record not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.