/kipris/trials/search

POST /api/kipris/trials/search

Price: 5 credits

Search Korean IP trial and judgment records

How to use it

Search Korean IP trial and judgment records on KIPRIS (the Korean IP office registry). Combine any of the filters (query, title, case_number, application_number and request date range in YYYYMMDD); all are combined with AND. Order by relevance (default) or request date. Returns each match's case number, court, trial type and stage, right type, related application number, dates, result, status and parties.

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 the case (examples: "battery")
• ip_right_title string nullable — Words in the IP right title
• case_number string nullable — Trial / judgment case number (examples: "2021101002323")
• application_number string nullable — Related application number
• request_date_from string nullable — Earliest request date (YYYYMMDD) (examples: "20210101")
• request_date_to string nullable — Latest request date (YYYYMMDD)
• sort string — Result ordering (default: "relevance"; one of: "relevance", "request_date")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "KiprisTrial")
• id string required
• case_number string nullable
• court string nullable
• trial_type string nullable
• trial_stage string nullable
• right_type string nullable
• summary string nullable
• application_number string nullable
• request_date string nullable
• decision_date string nullable
• result string nullable
• status string nullable
• ipc array (default: [])
• classification array (default: [])
• demandant string nullable
• demandant_agent 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.