/twse/funds

POST /api/twse/funds

Price: 10 credits

ETFs and other funds listed on the Taiwan Stock Exchange: names, fund type, tracked index or benchmark, founding and listing dates, fund manager, units issued, management company contacts and custodian

How to use it

Pass `fund_code` to twse/stocks/quotes for its trading history.

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 funds to return (min: 1; max: 1000)
• query string nullable — Text matched against the code and names (examples: "0050", "元大")

Response

• @type string (default: "TwseFund")
• fund_code string required
• short_name string nullable
• name string nullable
• name_en string nullable
• fund_type string nullable
• tracked_index string nullable
• is_custom_index string nullable
• asset_allocation string nullable
• has_benchmark boolean nullable
• benchmark string nullable
• benchmark_en string nullable
• holds_foreign_securities boolean nullable
• tax_id string nullable
• founded_date integer nullable
• listed_date integer nullable
• fund_manager string nullable
• units_issued integer nullable
• management_company_phone string nullable
• management_company_address string nullable
• management_company_chairman string nullable
• management_company_president string nullable
• management_company_spokesperson string nullable
• management_company_deputy_spokesperson string nullable
• master_agent string nullable
• custodian string nullable
• custodian_phone string nullable
• custodian_address string nullable
• note string nullable

Errors

• 422 — query is blank 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 — The entity was not found, or a precondition failed 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.