/miit_icp/filings/search

POST /api/miit_icp/filings/search

Price: 10 credits

Search China's MIIT ICP filing register for websites, apps, mini-programs or quick apps: by the filing company's name, a domain, an app name or an ICP licence number. Each row is the filing's licence number, the filed domain or app name, the filing company, its type and the last filing update.

How to use it

A company name or licence number returns that company's filings, up to count; a domain returns its own filing. App, mini-program and quick-app names match exactly. For the violating-site blacklist use miit_icp/violations.

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 filings to return (min: 1; max: 1000)
• query string required — Company name, domain, app name or ICP licence number (examples: "北京百度网讯科技有限公司", "baidu.com", "京ICP证030173号", "爱企查"; minLength: 1)
• service_type string — Kind of filed service (default: "website"; one of: "website", "app", "mini_program", "quick_app")

Response

• @type string (default: "MiitIcpFiling")
• id string required
• service_type string required (one of: "website", "app", "mini_program", "quick_app")
• licence string nullable
• company_licence string nullable
• name string nullable
• domain string nullable
• company_name string nullable
• company_type string nullable
• content_type string nullable
• leader_name string nullable
• access_restriction string nullable
• updated_at integer nullable
• company_record_id string nullable
• domain_id string nullable
• service_id string nullable

Errors

• 422 — count above 200 for a service_type other than website 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.