/mofcom/statistics/fie_trade_by_province

POST /api/mofcom/statistics/fie_trade_by_province

Price: 1 credit

Get one month of foreign-invested enterprise imports and exports by Chinese province and special economic zone

How to use it

Values are in USD thousand; region 合计 is the national total. A month the ministry has not published returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of rows (min: 1)
• date integer nullable — Month to return, unix seconds; omit for the latest published month (examples: 1575158400; min: 0)

Response

• @type string (default: "MofcomFieProvinceTrade")
• period string required
• period_start integer required
• region string required
• enterprise_type string nullable
• trade_month number nullable
• exports_month number nullable
• imports_month number nullable
• trade_ytd number nullable
• exports_ytd number nullable
• imports_ytd number nullable
• trade_ytd_yoy number nullable
• exports_ytd_yoy number nullable
• imports_ytd_yoy number nullable

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.