/ccgp/blacklist/search

POST /api/ccgp/blacklist/search

Price: 5 credits

Search China's register of suppliers penalised for serious dishonesty in government procurement, by company name, credit code, enforcing authority and penalty date. Each record is the company with its credit code and address, the violation, the penalty, its legal basis, the penalty and publication dates and the enforcing authority.

How to use it

With no filter the call walks the whole register, newest publication first. `company_name` matches part of a name; `credit_code` matches one company exactly.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company_name string nullable — Company name or part of it (examples: "建设"; minLength: 1)
• credit_code string nullable — Unified social credit code (examples: "91310114MA1GX6CA80"; minLength: 1)
• enforcement_unit string nullable — Authority that imposed the penalty (examples: "宁波市财政局"; minLength: 1)
• penalty_date_from string nullable — Earliest penalty date (format: date; examples: "2026-09-01")
• penalty_date_to string nullable — Latest penalty date (format: date; examples: "2026-09-25")
• count integer required — Max number of records to return (min: 1; max: 2500)

Response

• @type string (default: "CcgpBlacklistEntry")
• id string required
• company_name string required
• credit_code string nullable
• address string nullable
• violation string nullable
• penalty string nullable
• legal_basis string nullable
• penalty_date string nullable
• published_at integer nullable
• enforcement_unit 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.