/eastmoney/stocks/shareholders

POST /api/eastmoney/stocks/shareholders

Price: 1 credit

Get the ten largest shareholders, or the ten largest holders of tradable shares, of a Shanghai, Shenzhen or Beijing listed company for a report period from East Money, with shares held, holding percent, change and holder category

How to use it

report_date takes a quarter-end day such as 2026-03-31; change_note is East Money's Chinese label for the change.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbol string required — Stock code of a Shanghai, Shenzhen or Beijing listing, or its East Money quote page URL (examples: "600519", "SZ000001", "https://quote.eastmoney.com/sh600519.html")
• holder_type string — All shareholders, or holders of tradable shares (default: "all"; one of: "all", "tradable")
• report_date integer nullable — Report period end day, as unix seconds; defaults to the latest (examples: 1774915200)

Response

• @type string (default: "EastmoneyShareholder")
• secucode string required
• holder_type string required
• report_date integer nullable
• rank integer nullable
• holder_id string nullable
• name string nullable
• holder_category string nullable
• is_institution boolean nullable
• share_type string nullable
• shares_held number nullable
• holding_percent number nullable
• change_note string nullable
• holding_market_value number nullable
• published_date integer 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 — No shareholder list for that company and period 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.