/thaiegp/tenders

POST /api/thaiegp/tenders

Price: 1 credit

Thailand e-GP public procurement project from govspending.data.go.th by project id: budget, reference price, buyer, location, contracts with amounts, dates and winners, and the bidders with their offers per item.

How to use it

Pass `year` as the row's `budget_year` from thaiegp/tenders/search; without it the project is looked up in the published fiscal years among the 4 starting at the year its id begins with. `bid_items` is empty on projects whose bidders were not published.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Project id (examples: "68049277788")
• year integer nullable — Thai fiscal year (Buddhist Era) the project is budgeted in (examples: 2569)

Response

• @type string (default: "ThaiegpTender")
• id string required
• name string nullable
• budget_year integer nullable
• budget_amount number nullable
• reference_price number nullable
• contract_amount number nullable
• announce_date string nullable
• transaction_date string nullable
• project_type object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• status object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• method_group object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• method object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• organization_type object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• department object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• sub_department object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• province object nullable
  • @type string (default: "ThaiegpProvince")
  • id string nullable
  • name string nullable
  • name_en string nullable
  • center_lat number nullable
  • center_lon number nullable
• district object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• subdistrict object nullable
  • @type string (default: "ThaiegpCode")
  • id string nullable
  • name string nullable
  • name_en string nullable
• location string nullable
• location_type integer nullable
• lat number nullable
• lon number nullable
• contracts array (default: [])
  • @type string (default: "ThaiegpContract")
  • contract_number string nullable
  • contract_number_formatted string nullable
  • amount number nullable
  • contract_date string nullable
  • finish_date string nullable
  • status string nullable
  • status_en string nullable
  • winner object nullable
    • @type string (default: "ThaiegpWinner")
    • tax_id string nullable
    • name string nullable
    • is_personal boolean nullable
    • is_consortium boolean nullable
• bid_items array (default: [])
  • @type string (default: "ThaiegpBidItem")
  • sequence integer nullable
  • description string nullable
  • bidders array (default: [])
    • @type string (default: "ThaiegpBidder")
    • name string nullable
    • offer_amount number nullable

Errors

• 422 — The id is not 11 digits or the year is outside the covered range 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 project with that id in the given or looked-up fiscal years 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.