/eastmoney/stocks/fund_flow

POST /api/eastmoney/stocks/fund_flow

Price: 1 credit

Get the money flow of a Shanghai, Shenzhen, Beijing or Hong Kong security or an East Money board from East Money, per minute of the latest session or per trading day: main-force, super-large, large, medium and small order net inflow

How to use it

Main-force net inflow is the sum of super-large and large orders; ratios are percent of the day's amount. Daily rows cover about the last 120 trading days.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbol string required — Security code, East Money secid or quote page URL (examples: "600519", "SZ000001", "1.600519", "00700", "AAPL", "https://quote.eastmoney.com/sh600519.html")
• count integer required — Max number of rows to return, newest first (min: 1)
• period string — Per minute of the latest trading day, or per trading day (default: "day"; one of: "minute", "day")

Response

• @type string (default: "EastmoneyFundFlow")
• secid string required
• period string required
• ended_at integer required
• main_net_inflow number nullable
• super_large_net_inflow number nullable
• large_net_inflow number nullable
• medium_net_inflow number nullable
• small_net_inflow number nullable
• main_net_inflow_ratio number nullable
• super_large_net_inflow_ratio number nullable
• large_net_inflow_ratio number nullable
• medium_net_inflow_ratio number nullable
• small_net_inflow_ratio number nullable
• close number nullable
• change_percent 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 — East Money has no security under that symbol 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.