/tipo/patents

POST /api/tipo/patents

Price: 20 credits

Get a Taiwan patent, utility model or design record by certificate or publication number: title in Chinese and English, publication and grant numbers and dates, application number and date, IPC or Locarno classes, applicants, current holders, inventors, agents, priorities, examiner, abstract, cited patents, claims, full description and reference signs

How to use it

A 9-digit publication number returns the published application, an I/M/D number the granted patent; each names the other in publication_number or grant_number. Find numbers with tipo/patents/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• number string required — Patent certificate or publication number, or the record's TWPAT link (examples: "I818416", "M684034", "202237336", "https://tiponet.tipo.gov.tw/twpat5/twpatc/twpatkm?!!FRURLI818416")

Response

• @type string (default: "TipoPatent")
• 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
• publication_number string nullable
• publication_date integer nullable
• grant_number string nullable
• grant_date integer nullable
• certificate_number string nullable
• gazette_issue string nullable
• application_number string nullable
• application_date integer nullable
• ipc array (default: [])
  • @type string (default: "TipoClassification")
  • code string required
  • version string nullable
• current_ipc array (default: [])
  • @type string (default: "TipoClassification")
  • code string required
  • version string nullable
• locarno array (default: [])
• applicants array (default: [])
  • @type string (default: "TipoParty")
  • name string required
  • address string nullable
  • country string nullable
• applicant_standard_names array (default: [])
• current_holders array (default: [])
• holder_standard_names array (default: [])
• inventors array (default: [])
  • @type string (default: "TipoParty")
  • name string required
  • address string nullable
  • country string nullable
• agents array (default: [])
• current_agents array (default: [])
• priorities array (default: [])
  • @type string (default: "TipoPriority")
  • country string nullable
  • number string nullable
  • date integer nullable
• examiner string nullable
• dual_filing string nullable
• abstract string nullable
• cited_patents array (default: [])
• cited_literature string nullable
• cited_by_count integer nullable
• claims string nullable
• description string nullable
• reference_signs string nullable

Errors

• 422 — number is not a Taiwan patent certificate or publication number 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 — No patent under that number 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.