/cninfo/companies/shareholders

POST /api/cninfo/companies/shareholders

Price: 5 credits

Get the shareholder structure of a company listed in Shenzhen, Shanghai or Beijing from CNINFO: top ten shareholders and top ten float shareholders for up to the last five report dates, shareholder counts, fund holdings and share pledges

How to use it

`top_holders` repeats the ten holders for each report date, so group by `report_date`. `holding_percent_change` is the change in percentage points against the previous report date. Share counts are in shares.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — A-share stock code or CNINFO company page URL (examples: "300750", "600519", "https://www.cninfo.com.cn/new/disclosure/stock?stockCode=300750&orgId=GD165627"; minLength: 1)

Response

• @type string (default: "CninfoShareholders")
• company_code string required
• top_holders array (default: [])
  • @type string (default: "CninfoTopHolder")
  • report_date integer nullable
  • rank integer nullable
  • name string nullable
  • shares_held number nullable
  • holding_percent number nullable
  • holding_percent_change number nullable
  • share_type string nullable
• top_float_holders array (default: [])
  • @type string (default: "CninfoTopHolder")
  • report_date integer nullable
  • rank integer nullable
  • name string nullable
  • shares_held number nullable
  • holding_percent number nullable
  • holding_percent_change number nullable
  • share_type string nullable
• holder_counts array (default: [])
  • @type string (default: "CninfoHolderCount")
  • report_date integer nullable
  • holder_count integer nullable
  • holder_count_change_percent number nullable
• fund_holdings array (default: [])
  • @type string (default: "CninfoFundHolding")
  • report_date integer nullable
  • fund_count integer nullable
  • shares_held number nullable
• pledges array (default: [])
  • @type string (default: "CninfoPledge")
  • announced_date integer nullable
  • pledgor string nullable
  • pledgee string nullable
  • pledged_shares number nullable
  • released_shares number nullable
  • total_shares_percent number nullable
  • pledgor_holding_percent number nullable
  • description string nullable

Errors

• 422 — company is not a six-digit stock code or CNINFO company URL 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 listed company under that stock 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.