/ccgp/tenders/search

POST /api/ccgp/tenders/search

Price: 5 credits

Search Chinese government procurement announcements published on CCGP within a date window, by keyword in the title or full text, announcement type, central or local level, category, region, purchasing entity, agency and project number. Each row is the announcement's id, title, publication time, type, purchasing entity, agency, region and category.

How to use it

`start_date` and `end_date` are required, span at most a year and start no earlier than three years ago. Results run newest first; narrow the window or add filters when a query matches more than 1980. Pass a row's `id` to ccgp/tenders for the budget, contacts, attachments and full text.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• start_date string required — First publication day of the window (format: date; examples: "2026-09-01")
• end_date string required — Last publication day of the window (format: date; examples: "2026-09-25")
• keyword string nullable — Words to search for (examples: "医院", "体检服务"; minLength: 1)
• search_in string — Where the keyword is searched (default: "title"; one of: "title", "full_text")
• announcement_type string nullable — Announcement type (one of: "open_tender", "inquiry", "competitive_negotiation", "single_source", "prequalification", "invitation", "award", "correction", "other", "competitive_consultation", "deal", "termination")
• level string nullable — Central or local government procurement (one of: "central", "local")
• category string nullable — Procurement category (one of: "goods", "works", "services")
• region string nullable — Province-level region or separately listed city (one of: "beijing", "tianjin", "hebei", "shanxi", "inner_mongolia", "liaoning", "dalian", "jilin", "heilongjiang", "shanghai", "jiangsu", "zhejiang", "ningbo", "anhui", "fujian", "xiamen", "jiangxi", "shandong", "qingdao", "henan", "hubei", "hunan", "guangdong", "shenzhen", "guangxi", "hainan", "chongqing", "sichuan", "guizhou", "yunnan", "tibet", "shaanxi", "gansu", "qinghai", "ningxia", "xinjiang", "taiwan", "hong_kong", "macao")
• buyer_name string nullable — Purchasing entity name (examples: "深圳市教育局"; minLength: 1)
• agent_name string nullable — Procurement agency name (examples: "深圳交易集团有限公司政府采购业务分公司"; minLength: 1)
• project_code string nullable — Project number (examples: "0724-2631Z3354433"; minLength: 1)
• ppp_only boolean — Only public-private partnership projects (default: false)
• count integer required — Max number of announcements to return (min: 1; max: 1980)

Response

• @type string (default: "CcgpTenderListing")
• id string required
• url string required
• summary string nullable
• published_at integer nullable
• announcement_type string nullable (one of: "open_tender", "inquiry", "competitive_negotiation", "single_source", "prequalification", "invitation", "award", "correction", "other", "competitive_consultation", "deal", "termination")
• announcement_type_label string nullable
• level string nullable
• buyer_name string nullable
• agent_name string nullable
• region string nullable
• category 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.