/cnipa_trademarks/agencies/search

POST /api/cnipa_trademarks/agencies/search

Price: 10 credits

Search China's register of trademark agencies filed with the CNIPA Trademark Office: agencies whose filing passed verification, filed agencies that did not pass it, and agencies whose filing was cancelled. Filter by name, address, region, agency kind, practitioner count and filing or cancellation date. Each row is the agency's id, name, address, region, phone, person in charge, number of filed practitioners and filing date.

How to use it

Cancelled agencies carry name, address and phone, and a cancellation date only for recent cancellations; region_code, enterprise_type and staff_size apply to the verified and not_verified lists only. Name and address match on contained words.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of agencies to return (min: 1; max: 40000)
• status string — Which agency list to search (default: "verified"; one of: "verified", "not_verified", "cancelled")
• name string nullable — Words in the agency name (examples: "律师事务所", "知识产权代理"; minLength: 1)
• address string nullable — Words in the agency address (examples: "朝阳区"; minLength: 1)
• region_code string nullable — Chinese administrative division code of the agency's province or city (examples: "110000", "440300"; pattern: ^\d{6}$)
• enterprise_type string nullable — Kind of agency (one of: "company", "law_firm")
• staff_size string nullable — Number of filed trademark practitioners at the agency (one of: "one", "two", "three_to_ten", "eleven_to_twenty", "over_twenty")
• date_from integer nullable — Earliest filing day, or cancellation day for cancelled agencies, as unix seconds (examples: 1704067200)
• date_to integer nullable — Latest filing day, or cancellation day for cancelled agencies, as unix seconds (examples: 1735603200)

Response

• @type string (default: "CnipaAgency")
• id string required
• name string nullable
• status string required (one of: "verified", "not_verified", "cancelled")
• enterprise_type string nullable (one of: "company", "law_firm")
• enterprise_type_code string nullable
• address string nullable
• region_code string nullable
• region_name string nullable
• phone string nullable
• person_in_charge string nullable
• practitioner_count integer nullable
• filed_at integer nullable
• cancelled_at integer nullable

Errors

• 422 — region_code, enterprise_type or staff_size combined with status cancelled 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.