Building an AI agent? Start with /llms.txt for the full site index.
Companies & Events
Governance — chairman/GM duality (t187ap33_L)
Governance — chairman/GM duality (t187ap33_L)
GET /v2/datasets/governance-t187ap33-lGovernance — chairman/GM duality (t187ap33_L) is a Taiwan market dataset sourced from TWSE, served by TW Market Data as GET /v2/datasets/governance-t187ap33-l.
Overview
Governance — chairman/GM duality (t187ap33_L) — the backend metadata exposes no grain, so none is stated here.
| Field | Type | Description |
|---|---|---|
ticker | string | |
company_name | string | |
as_of_date | string | |
chairperson_name | string | |
general_manager_name | string | |
chairperson_concurrent_general_manager | boolean | |
status_code | string | |
status_text | string | |
source_dataset_code | string |
Example response
A real response from this endpoint. Rows are returned under "data", and provenance is carried in the shape shown below — it is not identical across datasets, so read this page's rather than assuming another's.
{ "dataset_id": "governance_t187ap33_l", "request_context": { "scope": "listed_company_chair_gm_concurrency", "coverage_type": "as_of_date_snapshot", "filters": { "ticker": "5269", "as_of_date": null, "date_from": null, "date_to": null, "concurrent_only": false, "limit": 50 }, "min_as_of_date": "2026-06-26", "max_as_of_date": "2026-08-04" }, "quality": { "row_count": 7, "ticker_count": 1, "concurrent_chair_gm_count": 0, "sensitive_fields_exposed": false }, "lineage": { "source_dataset_codes": [ "t187ap33_L" ], "semantics": "MOPS t187ap33_L: whether a listed company's chairperson also serves as general manager, with both names, as observed on as_of_date. A governance concentration signal, not a performance metric." }, "error": null, "data": [ { "ticker": "5269", "company_name": "<Chinese value - see the zh page>", "as_of_date": "2026-08-04", "chairperson_name": "<Chinese value - see the zh page>", "general_manager_name": "<Chinese value - see the zh page>", "chairperson_concurrent_general_manager": false, "status_code": "not_concurrent", "status_text": "<Chinese value - see the zh page>", "source_dataset_code": "t187ap33_L", "source_url": "https://openapi.twse.com.tw/v1/opendata/t187ap33_L", "source_role": "official_governance_openapi", "lineage": { "source": "TWSE OpenAPI t187ap33_L", "source_url": "https://openapi.twse.com.tw/v1/opendata/t187ap33_L", "latest_only": true, "source_role": "official_governance_openapi", "report_date_roc": "1150804" } }, { "ticker": "5269", "company_name": "<Chinese value - see the zh page>", "as_of_date": "2026-08-03", "chairperson_name": "<Chinese value - see the zh page>", "general_manager_name": "<Chinese value - see the zh page>", "chairperson_concurrent_general_manager": false, "status_code": "not_concurrent", "status_text": "<Chinese value - see the zh page>", "source_dataset_code": "t187ap33_L", "source_url": "https://openapi.twse.com.tw/v1/opendata/t187ap33_L", "source_role": "official_governance_openapi", "lineage": { "source": "TWSE OpenAPI t187ap33_L", "source_url": "https://openapi.twse.com.tw/v1/opendata/t187ap33_L", "latest_only": true, "source_role": "official_governance_openapi", "report_date_roc": "1150803" } } ], "data_count": 7, "known_gaps": [ "as_of_date_is_the_observation_date_not_the_appointment_date", "listed_companies_only_t187ap33_L_scope", "not_investment_advice" ], "warnings": [ "not_investment_advice" ], "envelope": { "dataset_id": "governance_t187ap33_l", "scope": "listed_company_chair_gm_concurrency", "row_count": 7 }}Captured from the live API on 2026-07-20.
Chinese data values are shown as a marker here so this page stays in English; the /zh page shows them verbatim.
Provenance
These columns are returned alongside the data and record where the row came from. They are provenance, not the dataset's subject matter, so they are listed here rather than in the field table.
source_urlsource_rolelineageRelated datasets
Datasets that join with this one. The key each pair aligns on is shown, so you can plan a multi-table query without guessing.
- GHG Carbon Disclosure (Scope 1/2/3)
Joins on as_of_date + ticker
- Institutional flow
Joins on as_of_date + ticker
- Margin & short
Joins on as_of_date + ticker
- Market value weight
Joins on as_of_date + ticker
- Securities lending
Joins on as_of_date + ticker
Getting started
- Put your key in the X-API-Key header.
- Add query parameters (symbol, date range, limit).
- Send the request and read the data array.
curl "https://api.twmarketdata.com/v2/datasets/governance-t187ap33-l?symbol=2330" \ -H "X-API-Key: sk_live_..."Filtering
| Parameter | Required | Type | Description |
|---|---|---|---|
symbol | No | string | Ticker to filter to a single security. |
limit | No | integer | Maximum rows to return. |
Python
A first call:
import requests resp = requests.get( "https://api.twmarketdata.com/v2/datasets/governance-t187ap33-l", params={"symbol": "2330"}, headers={"X-API-Key": "sk_live_..."},)resp.raise_for_status()print(resp.json()["data"])With a date-range filter:
import requests # The full verified example — the same call with every supported filter set.resp = requests.get( "https://api.twmarketdata.com/v2/datasets/governance-t187ap33-l", params={"symbol": "2330"}, headers={"X-API-Key": "sk_live_..."},)resp.raise_for_status()for row in resp.json()["data"]: print(row)OpenAPI
This endpoint is GET /v2/datasets/governance-t187ap33-l. The full machine-readable schema (parameters, security, response envelope) lives in the OpenAPI spec.
Notes & limitations
- The backend metadata exposes no grain or field list, so no field table is shown. The knowledge-time field is as_of_date.