/mofcom/investment_projects

POST /api/mofcom/investment_projects

Price: 1 credit

Get one MOFCOM investment project: amounts, description, investor requirements and contacts

How to use it

Takes an id from mofcom/investment_projects/search; an unknown id answers 412.

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 from the project search, or the project's detail page URL (examples: "115597", "https://project.mofcom.gov.cn/fdip_swb_xmkweb/business/controllers/xiangMuGuanLiAction/xiangMuLook?id=115597"; minLength: 1)

Response

• @type string (default: "MofcomInvestmentProject")
• id string required
• url string required
• name string required
• published_at integer nullable
• category string nullable
• project_type string nullable
• investment_mode string nullable
• industry string nullable
• location string nullable
• validity string nullable
• fund_type string nullable
• total_amount number nullable
• total_amount_unit string nullable
• investment_sought number nullable
• investment_sought_unit string nullable
• description string nullable
• mark string nullable
• nature string nullable
• advantages string nullable
• investor_type string nullable
• investor_requirements string nullable
• organization string nullable
• contact_name string nullable
• phone string nullable
• fax string nullable
• email string nullable
• remarks string nullable
• attachments array (default: [])
  • @type string (default: "MofcomProjectAttachment")
  • url string required

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 — 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.