/vneps/tenders/search

POST /api/vneps/tenders/search

Price: 5 credits

Search Vietnam contractor selection notices on muasamcong.mpi.gov.vn by package name words, field, procurement rules, selection method, stage, online or offline bidding, investor, province, package price and publication or bid closing date. Returns the notice with investor, price, dates, locations, bid counts and winners.

How to use it

Newest first by publication time; without a date range the first 10000 rows reach back about a month, so pass `published_from`/`published_to` for older notices. Pass `id` to vneps/tenders for the full notice, lots, bid opening and award result.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Words of the package name or the notice number (examples: "thiết bị y tế"; minLength: 2)
• invest_field string nullable — Field of the package (one of: "goods", "construction", "non_consulting", "consulting", "mixed")
• procedure string nullable — Procurement rules the package follows (one of: "domestic_law", "world_bank", "adb", "cptpp", "evfta", "ukfta", "other")
• selection_method string nullable — Contractor selection method (one of: "open_bidding", "restricted_bidding", "competitive_quotation", "online_quotation", "shortened_online_quotation", "direct_appointment", "shortened_direct_appointment", "special_case", "individual_consultant", "individual_consultant_selection", "quality_cost_based", "consultant_qualifications", "other")
• stage string nullable — Stage the notice has reached (one of: "notice", "bid_opening", "technical_shortlist", "award", "price_reoffer")
• is_online boolean nullable — Bids are submitted online
• is_domestic boolean nullable — Domestic rather than international bidding
• investor_code string nullable — Investor code, as in `investor.code` (examples: "vn3703487840")
• province_code string nullable — Province code, as in `locations[].province_code` (examples: "08", "01")
• min_price number nullable — Lowest package price, VND (examples: 1000000000; min: 0)
• max_price number nullable — Highest package price, VND (examples: 2000000000; min: 0)
• published_from string nullable — Published on or after (examples: "2026-09-01")
• published_to string nullable — Published on or before (examples: "2026-09-30")
• bid_close_from string nullable — Bid closing on or after (examples: "2026-10-01")
• bid_close_to string nullable — Bid closing on or before (examples: "2026-10-31")
• offset integer — Rows to skip (default: 0; min: 0; max: 9999)
• count integer required — Max number of notices to return (min: 1; max: 10000)

Response

• @type string (default: "VnepsTenderSummary")
• id string required
• notice_id string nullable
• notify_version string nullable
• url string nullable
• name string nullable
• project_name string nullable
• package_number string nullable
• package_id string nullable
• plan_number string nullable
• plan_type string nullable
• stage string nullable
• status string nullable
• notify_status string nullable
• invest_fields array (default: [])
• bid_field string nullable
• procedure string nullable
• selection_method string nullable
• bid_mode string nullable
• work_type string nullable
• is_online boolean nullable
• is_domestic boolean nullable
• is_multi_lot boolean nullable
• is_medicine boolean nullable
• medicine_count integer nullable
• price number nullable
• reoffer_start_price number nullable
• reoffer_price_step number nullable
• investor object nullable
  • @type string (default: "VnepsParty")
  • code string nullable
  • name string nullable
• procuring_entity object nullable
  • @type string (default: "VnepsParty")
  • code string nullable
  • name string nullable
• joint_venture_name string nullable
• locations array (default: [])
  • @type string (default: "VnepsLocation")
  • province_code string nullable
  • province_name string nullable
  • district_code string nullable
  • district_name string nullable
  • ward_code string nullable
  • ward_name string nullable
• published_at integer nullable
• original_published_at integer nullable
• bid_close_at integer nullable
• bid_open_at integer nullable
• actual_bid_open_at integer nullable
• bid_opening_published_at integer nullable
• award_published_at integer nullable
• award_decision_at integer nullable
• approval_at integer nullable
• bidder_count integer nullable
• technical_bidder_count integer nullable
• clarification_count integer nullable
• petition_count integer nullable
• petition_documents_count integer nullable
• petition_selection_count integer nullable
• petition_result_count integer nullable
• is_passed boolean nullable
• winners array (default: [])
  • @type string (default: "VnepsWinner")
  • code string nullable
  • name string nullable
  • price number nullable
  • lot_number string nullable
  • lot_name string nullable
• lot_winning_prices array (default: [])

Errors

• 422 — A date is not YYYY-MM-DD, a range is inverted, the province code is not 2 digits, or the requested rows run past row 10000 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.