/tipo/patents/search

POST /api/tipo/patents/search

Price: 10 credits

Search Taiwan patents, utility models and designs by words across all fields, optionally limited by type, publication or grant, and a date window: number, title in Chinese and English, publication or grant date, application number and date, and case status

How to use it

Returns at most the first 2000 matches; narrow with a date window or filters to reach the rest. Pass number to tipo/patents for claims, parties and the full text.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Words searched across all fields of the patent records (examples: "晶圓 研磨", "台灣積體電路")
• patent_types array nullable — Patent types to include; every type when omitted (one of: "invention", "utility_model", "design")
• record_kinds array nullable — Published applications, granted patents or both; both when omitted (one of: "publication", "grant")
• statuses array nullable — Case statuses to include; every status when omitted (one of: "granted", "revoked", "lapsed", "published", "rejected", "closed")
• date_field string — Date that date_from and date_to apply to (default: "publication_or_grant"; one of: "publication_or_grant", "application", "priority")
• date_from integer nullable — Earliest date, unix seconds (examples: 1735689600)
• date_to integer nullable — Latest date, unix seconds (examples: 1767225599)
• count integer required — Max number of patents to return (min: 1; max: 2000)

Response

• @type string (default: "TipoPatentSearchItem")
• number string required
• url string required
• patent_type string nullable (one of: "invention", "utility_model", "design")
• is_publication boolean (default: false)
• title_en string nullable
• date integer nullable
• application_number string nullable
• application_date integer nullable
• status string nullable

Errors

• 422 — query is blank, a list filter is empty or date_to is before date_from 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.