/vneps/investors

POST /api/vneps/investors

Price: 1 credit

Vietnam approved investor (procuring owner) from muasamcong.mpi.gov.vn by code: legal name in Vietnamese and English, tax registration, address, legal representative, business lines and, where the investor filed one, its capability profile with staff count, scale, bidding fields and registration documents.

How to use it

Takes the `id` of a vneps/investors/search row or an `investor.code` from vneps/tenders.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Investor code (examples: "vn0111426410")

Response

• @type string (default: "VnepsInvestor")
• id string required
• name string nullable
• tax_code string nullable
• address string nullable
• province_code string nullable
• district_code string nullable
• ward_code string nullable
• status integer nullable
• pending_since_date string nullable
• name_en string nullable
• business_type string nullable
• id_type string nullable
• tax_country string nullable
• tax_registration_date string nullable
• decision_number string nullable
• phone string nullable
• website string nullable
• zipcode string nullable
• representative_name string nullable
• representative_position string nullable
• agency_code string nullable
• budget_code string nullable
• is_foreign boolean nullable
• business_lines array (default: [])
  • @type string (default: "VnepsBusinessLine")
  • id string nullable
  • code string nullable
  • name string nullable
  • is_main boolean nullable
• capability_profile object nullable
  • @type string (default: "VnepsCapabilityProfile")
  • id string nullable
  • version string nullable
  • status string nullable
  • org_scale string nullable
  • employee_count integer nullable
  • bid_fields array (default: [])
  • investor_selection_fields array (default: [])
  • fiscal_year_start string nullable
  • fiscal_year_end string nullable
  • is_startup boolean nullable
  • business_registration_date string nullable
  • business_registration_country string nullable
  • business_registration_file object nullable
    • @type string (default: "VnepsFile")
    • id string nullable
    • name string nullable
    • kind string nullable
  • charter_file object nullable
    • @type string (default: "VnepsFile")
    • id string nullable
    • name string nullable
    • kind string nullable
  • org_chart_file object nullable
    • @type string (default: "VnepsFile")
    • id string nullable
    • name string nullable
    • kind string nullable
  • decision_number string nullable
  • decision_date string nullable
  • decision_agency string nullable
  • decision_country string nullable
  • decision_file object nullable
    • @type string (default: "VnepsFile")
    • id string nullable
    • name string nullable
    • kind string nullable
  • shareholders_file object nullable
    • @type string (default: "VnepsFile")
    • id string nullable
    • name string nullable
    • kind string nullable
  • legal_representative_name string nullable
  • province_code string nullable
  • district_code string nullable
  • ward_code string nullable
  • address string nullable
  • phone string nullable
  • zipcode string nullable
  • website string nullable
  • business_lines array (default: [])
    • @type string (default: "VnepsBusinessLine")
    • id string nullable
    • code string nullable
    • name string nullable
    • is_main boolean nullable
  • created_at integer nullable
  • updated_at integer nullable

Errors

• 422 — The value is not an investor code like vn0111426410 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 investor with that code 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.