/tipo/trademarks/search

POST /api/tipo/trademarks/search

Price: 10 credits

Search Taiwan trademarks by text in the mark, applicant or holder name, case status, Nice class and application date: application and registration numbers, mark name and wording, status, dates, classes with goods, applicant, agent and the mark image

How to use it

All given criteria must match. Pass application_number to tipo/trademarks for goods per class, prosecution history and every applicant and agent.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Text contained in the mark's Chinese or English wording (examples: "台積電", "SONY")
• applicant string nullable — Text contained in the applicant or holder name (examples: "台灣積體電路")
• statuses array nullable — Case statuses to include; every status when omitted (one of: "pending", "registered", "application_lapsed", "registration_lapsed", "rejected", "other")
• goods_class integer nullable — Nice class of goods or services (examples: 9, 35; min: 1; max: 45)
• application_date_from integer nullable — Earliest application date, unix seconds (examples: 1609459200)
• application_date_to integer nullable — Latest application date, unix seconds (examples: 1798761599)
• count integer required — Max number of trademarks to return (min: 1; max: 1000)

Response

• @type string (default: "TipoTrademarkSearchItem")
• case_number string required
• application_number string nullable
• mark_name string nullable
• mark_text_zh string nullable
• mark_text_en string nullable
• mark_text_ja string nullable
• mark_symbols string nullable
• mark_kind string nullable
• mark_kind_en string nullable
• status string nullable
• status_en string nullable
• status_code string nullable
• is_valid boolean nullable
• invalidation_reason string nullable
• examination_result string nullable
• rejection_clause string nullable
• registration_number string nullable
• application_date integer nullable
• examination_notice_date integer nullable
• registration_date integer nullable
• registration_notice_date integer nullable
• expiry_date integer nullable
• deletion_date integer nullable
• decision_date integer nullable
• goods_classes array (default: [])
• goods array (default: [])
  • @type string (default: "TipoGoodsClass")
  • goods_class string required
  • goods string nullable
  • groups array (default: [])
• applicant string nullable
• applicant_en string nullable
• applicant_address string nullable
• applicant_address_en string nullable
• applicant_country string nullable
• applicant_country_en string nullable
• applicant_origin string nullable
• agent string nullable
• disclaimer string nullable
• remark string nullable
• related_registration_number string nullable
• mark_description string nullable
• image string nullable
• priorities array (default: [])
  • @type string (default: "TipoTrademarkPriority")
  • date integer nullable
  • country string nullable
  • country_en string nullable
• rejection_notice_date integer nullable
• cited_registrations array (default: [])
• is_divisional boolean nullable

Errors

• 422 — neither query nor applicant is given, a text is blank, a list is empty or the date window is reversed 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.