/aiqicha/companies/shareholders

POST /api/aiqicha/companies/shareholders

Price: 1 credit

Get the shareholders or partners of a Chinese company from Aiqicha, with holding percentage, subscribed capital and date, shares held for listed companies, and the holder's company or person id

How to use it

Take the company id from aiqicha/companies/search. source latest_disclosure is the most recent published list (the top ten holders for a listed company), registration is the business registration record; a company without the requested list returns an empty list. Recently registered companies often return an empty list too.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Aiqicha company id or company page URL (examples: "29453261288626", "https://aiqicha.baidu.com/company_detail_29453261288626")
• count integer required — Max number of results (min: 1)
• source string nullable — Shareholder list to read; defaults to the one Aiqicha shows first (one of: "latest_disclosure", "registration")

Response

• @type string (default: "AiqichaShareholder")
• company_id string required
• source string nullable
• as_of_date integer nullable
• name string required
• holder_company_id string nullable
• holder_person_id string nullable
• holder_url string nullable
• image string nullable
• holding_percent number nullable
• shares_held number nullable
• share_types array (default: [])
• subscribed_capital number nullable
• subscribed_capital_currency string nullable
• subscribed_date integer nullable
• related_company_count integer nullable
• investment_count integer nullable
• labels array (default: [])
  • @type string (default: "AiqichaLabel")
  • key string required
  • text string required
  • former_names array (default: [])
    • @type string (default: "AiqichaFormerName")
    • name string required
    • start_month string nullable
    • end_month string 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 — Aiqicha has no company under that id 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.