/wipo_brands/trademarks/statistics

POST /api/wipo_brands/trademarks/statistics

Price: 1 credit

Aggregate trademark counts over a chosen dimension

How to use it

Get aggregated trademark counts broken down by a chosen dimension — designation country, origin office, Nice class, mark feature, record type, status, owner kind, or applicant country. Optionally scope the aggregation to a mark text query and the same filters as the search endpoint. Returns each dimension value with its record count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• facet string required — Dimension to aggregate counts over (one of: "designation", "office", "niceClass", "markFeature", "type", "status", "kind", "applicantCountryCode")
• keyword string nullable — Mark text query to scope the aggregation (examples: "apple")
• strategy string — Mark text matching strategy (default: "Simple"; one of: "Embedded", "Exact", "Simple", "Fuzzy", "Phonetic", "Stemming")
• owner string nullable — Scope by owner or holder name
• nice_classes array nullable — Scope by Nice classification class numbers (examples: [9,42])
• designations array nullable — Scope by designation country or office codes (examples: ["US"])
• offices array nullable — Scope by origin office codes (examples: ["US","JP"])
• features array nullable — Scope by mark feature (one of: "Colour", "Combined", "Figurative", "Hologram", "Motion", "Multimedia", "Olfactory", "Other", "Pattern", "Position", "Sound", "Stylized characters", "Three dimensional", "Tracer", "Undefined", "Word")

Response

• @type string (default: "WipoBrandsStatisticBucket")
• value string required
• count integer required

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.