/wipo_brands/trademarks/search

POST /api/wipo_brands/trademarks/search

Price: 1 credit

Search trademarks by mark text and filters

How to use it

Search the WIPO Global Brand Database of trademarks, emblems, and appellations of origin from 89 offices worldwide. Match by mark text with a choice of matching strategies, and filter by owner, representative, goods and services, application or registration number, Nice classes, Vienna image classes, designation countries, origin offices, and mark feature. Returns each matching record's ST13, mark text, type, feature, status, numbers and dates, origin office, designation, Nice classes, applicants, and image.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Mark text search query (examples: "apple")
• count integer required — Max number of results (min: 1)
• strategy string — Mark text matching strategy (default: "Simple"; one of: "Embedded", "Exact", "Simple", "Fuzzy", "Phonetic", "Stemming")
• owner string nullable — Filter by owner or holder name
• representative string nullable — Filter by representative name
• goods_services string nullable — Filter by goods and services text
• number string nullable — Filter by application or registration number
• nice_classes array nullable — Filter by Nice classification class numbers (examples: [9,42])
• vienna_classes array nullable — Filter by Vienna image classification codes (examples: ["01.01.01"])
• designations array nullable — Filter by designation country or office codes (examples: ["US","EM"])
• offices array nullable — Filter by origin office codes (examples: ["US","JP"])
• features array nullable — Filter by mark feature (one of: "Colour", "Combined", "Figurative", "Hologram", "Motion", "Multimedia", "Olfactory", "Other", "Pattern", "Position", "Sound", "Stylized characters", "Three dimensional", "Tracer", "Undefined", "Word")
• sort string — Result ordering (default: "most_relevant"; one of: "most_relevant", "least_relevant", "recently_filed", "oldest_filed", "recently_registered", "oldest_registered", "st13_descending", "st13_ascending")

Response

• @type string (default: "WipoBrandsSearchTrademark")
• st13 string required
• mark_text string nullable
• type string nullable
• kind string nullable
• mark_feature string nullable
• status string nullable
• application_number string nullable
• registration_number string nullable
• application_date string nullable
• registration_date string nullable
• expiry_date string nullable
• origin_office string nullable
• designation array (default: [])
• nice_classes array (default: [])
• applicants array (default: [])
• applicant_countries array (default: [])
• image 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.