/vneps/contracts/search

POST /api/vneps/contracts/search

Price: 10 credits

Search the Vietnam contract performance registry on muasamcong.mpi.gov.vn by contractor name or tax code, investor, package name, contract code or number, and publication or signing date. Returns the contract with investor, contractor, signing and completion dates and performance status.

How to use it

Most recently updated first. Pass `id` to vneps/contracts for prices, VAT, contract type, goods and completion progress. `notify_number` is the `id` for vneps/tenders except on rows whose `source` is `KQ_KHAC`: those record a result filed without a portal notice, and vneps/tenders answers 412 for them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• contractor_name string nullable — Words of the contractor name (examples: "TOYOTA"; minLength: 2)
• contractor_tax_code string nullable — Tax code of the contractor or a joint-venture member (examples: "0105348644"; minLength: 3)
• investor_name string nullable — Words of the investor name (examples: "Bệnh viện"; minLength: 2)
• package_name string nullable — Words of the package name (examples: "xe ô tô"; minLength: 2)
• contract_code string nullable — Contract code or its leading characters (examples: "HD2500202334"; minLength: 3)
• contract_number string nullable — Contract number or part of it (examples: "05251361/HĐMB"; minLength: 2)
• published_from string nullable — Published on or after (examples: "2026-09-01")
• published_to string nullable — Published on or before (examples: "2026-09-30")
• signed_from string nullable — Signed on or after (examples: "2025-01-01")
• signed_to string nullable — Signed on or before (examples: "2025-12-31")
• offset integer — Rows to skip (default: 0; min: 0)
• count integer required — Max number of contracts to return (min: 1; max: 10000)

Response

• @type string (default: "VnepsContractSummary")
• id string required
• record_id string nullable
• contract_version string nullable
• record_number string nullable
• record_version string nullable
• contract_number string nullable
• contract_name string nullable
• project_name string nullable
• package_name string nullable
• notify_number string nullable
• notify_version string nullable
• result_version string nullable
• invest_field string nullable
• source string nullable
• perform_type string nullable
• investor object nullable
  • @type string (default: "VnepsParty")
  • code string nullable
  • name string nullable
• contractor object nullable
  • @type string (default: "VnepsParty")
  • code string nullable
  • name string nullable
• contractor_tax_code string nullable
• joint_venture object nullable
  • @type string (default: "VnepsParty")
  • code string nullable
  • name string nullable
• publisher_role string nullable
• published_by string nullable
• status string nullable
• performance_status string nullable
• quality string nullable
• termination string nullable
• violation string nullable
• sign_date string nullable
• planned_completion_date string nullable
• actual_completion_date string nullable
• contract_published_at integer nullable
• published_at integer nullable
• created_at integer nullable
• updated_at integer nullable

Errors

• 422 — A date is not YYYY-MM-DD or a date range is inverted 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.