/twse/companies/insiders

POST /api/twse/companies/insiders

Price: 5 credits

Shareholdings of the directors, supervisors and managers of a Taiwan listed or OTC company for one month: title, shares at election and now, shares pledged, and holdings of spouses, minor children and nominees

How to use it

Without a month it returns the latest filed month. Titles and names are in Chinese as filed. Rows of the company itself come first; for a financial holding the holdings of each subsidiary follow, marked by `subsidiary_id` and `subsidiary_name`, which are empty on the company's own rows.

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 insiders to return (min: 1; max: 2000)
• company string required — Stock code of the company (examples: "2330", "6488")
• month integer nullable — Month of the holdings report, as unix seconds; the latest when omitted (examples: 1764547200)

Response

• @type string (default: "TwseInsiderHolding")
• company_code string required
• month integer required
• name string required
• election_shares integer nullable
• shares integer nullable
• pledged_shares integer nullable
• pledged_percent number nullable
• related_party_shares integer nullable
• related_party_pledged_shares integer nullable
• related_party_pledged_percent number nullable
• subsidiary_id string nullable
• subsidiary_name string nullable

Errors

• 422 — company is not a 4-6 character stock code, or month is before 2006 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 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.