/miit_icp/filings

POST /api/miit_icp/filings

Price: 5 credits

Get one ICP filing from China's MIIT register by its id: the website or app filing's licence number, the filed domain or app name, the filing company with its own licence number and type, and the last filing update.

How to use it

Ids come from miit_icp/filings/search. A website filing's service_id is filled only here.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• filing_id string required — ICP filing id from miit_icp/filings/search (examples: "website:282751:10000245113", "app:7218837", "mini_program:26642086")

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 — 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 — No filing under that id, including an app id asked as another service type 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.