/szse/funds/search

POST /api/szse/funds/search

Price: 1 credit

List the funds listed on the Shenzhen Stock Exchange (ETFs, LOFs, closed-end funds and REITs), by code or name, manager, structure and investment category: fund type, asset class, listing date, units outstanding and manager

How to use it

`units_outstanding` counts fund units. Filter ETFs with `fund_type=etf`; `manager` matches part of the manager's Chinese name.

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: 1200)
• keyword string nullable — Fund code or short name (examples: "159915", "创业板"; minLength: 1)
• manager string nullable — Fund manager name (examples: "易方达基金管理有限公司", "华夏"; minLength: 1)
• fund_type string nullable — Fund structure (one of: "etf", "lof", "closed_end", "reit")
• asset_class string nullable — Investment category (one of: "equity", "mixed", "bond", "money_market")

Response

• @type string (default: "SzseFund")
• fund_code string required
• name string nullable
• fund_type string nullable
• asset_class string nullable
• listed_date integer nullable
• units_outstanding number nullable
• manager string nullable
• as_of_date integer nullable

Errors

• 422 — An unknown fund_type or asset_class 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.