/ccgp/tenders

POST /api/ccgp/tenders

Price: 20 credits

One Chinese government procurement announcement from CCGP by id or URL: project name and number, type, purchasing entity and agency with addresses and contacts, budget or awarded amount, document sale period, place and fee, opening time and place, evaluation experts, attachments and the full announcement text.

How to use it

Takes the `id` of a ccgp/tenders/search row or the announcement URL. Winners, per-lot amounts and scores appear only inside `content`, as each province words them. `other_fields` holds summary rows whose value is not a clean date or amount.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Announcement id or URL (examples: "zygg/gkzb/202609/t20260924_27402144", "http://www.ccgp.gov.cn/cggg/zygg/gkzb/202609/t20260924_27402144.htm"; minLength: 1)

Response

• @type string (default: "CcgpTender")
• id string required
• url string required
• project_name string nullable
• project_code string nullable
• announcement_type string nullable (one of: "open_tender", "inquiry", "competitive_negotiation", "single_source", "prequalification", "invitation", "award", "correction", "other", "competitive_consultation", "deal", "termination")
• level string nullable
• published_at integer nullable
• category string nullable
• region string nullable
• buyer_name string nullable
• buyer_address string nullable
• buyer_contact string nullable
• agent_name string nullable
• agent_address string nullable
• agent_contact string nullable
• contact_name string nullable
• contact_phone string nullable
• budget_amount number nullable
• awarded_amount number nullable
• currency string nullable
• document_period string nullable
• document_location string nullable
• document_fee number nullable
• submission_location string nullable
• submission_deadline_at integer nullable
• opening_at integer nullable
• opening_location string nullable
• prequalification_date string nullable
• first_published_date string nullable
• corrected_date string nullable
• correction_subject string nullable
• evaluation_experts array (default: [])
• other_fields array (default: [])
  • @type string (default: "CcgpField")
  • label string required
  • value string nullable
• attachments array (default: [])
  • @type string (default: "CcgpAttachment")
  • name string nullable
  • url string required
• content 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 announcement exists under that id 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.