/twpcc/tenders

POST /api/twpcc/tenders

Price: 5 credits

One Taiwan government procurement notice by id or URL: the agency with its contact, the case number and name, category, budget and amount tier, tendering and award method, announcement dates, bid deadline and opening, performance place and period, every section of the notice as labelled fields, and the case's announcement history.

How to use it

Takes the `id` of a twpcc/tenders/search row or the notice URL. `sections` carries every labelled field of the notice in its own wording, including those without a named field here.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Tender notice id or URL (examples: "71336762", "https://web.pcc.gov.tw/tps/QueryTender/query/searchTenderDetail?pkPmsMain=NzEzMzY3NjI="; minLength: 1)

Response

• @type string (default: "TwpccTender")
• id string required
• url string required
• case_number string nullable
• org_id string nullable
• org_name string nullable
• unit_name string nullable
• org_address string nullable
• contact_name string nullable
• contact_phone string nullable
• contact_fax string nullable
• contact_email string nullable
• category string nullable
• amount_tier string nullable
• legal_basis string nullable
• budget_amount number nullable
• currency string nullable
• tender_method string nullable
• award_method string nullable
• tender_status string nullable
• transmission_number string nullable
• correction_number string nullable
• announced_date string nullable
• original_announced_date string nullable
• deadline_at integer nullable
• opening_at integer nullable
• opening_location string nullable
• performance_location string nullable
• performance_period string nullable
• corrections array (default: [])
  • @type string (default: "TwpccCorrection")
  • label string nullable
  • value string nullable
  • previous_value string nullable
• sections array (default: [])
  • @type string (default: "TwpccSection")
  • name string nullable
  • fields array (default: [])
    • @type string (default: "TwpccField")
    • label string required
    • value string nullable
• history array (default: [])
  • @type string (default: "TwpccHistoryEntry")
  • kind string nullable
  • transmission_number string nullable
  • correction_number string nullable
  • documents_changed boolean nullable
  • announced_date 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 tender notice 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.