FAQ
Grouped into data conventions / using the API / service and boundaries. These are the problems that actually come up during integration, not filler questions.
Data conventions
Which funds are covered? Will ETFs or QDII be added?+
Currently open-end mutual funds in mainland China, including money-market funds. ETFs, LOFs and QDII funds are planned; new products arrive as new endpoints without changing existing tool names or call patterns.
How often is NAV updated? Is it realtime?+
No, it is not realtime. NAV for open-end funds is calculated and published by the fund company after the market closes on a trading day, and ours is updated that evening — so refreshing intraday will not show today's NAV. If you need an intraday move, use the estimate endpoint (Institutional); that is an estimate and not NAV.
Why does 600519 return nothing?+
This is an open-end fund API. It only accepts 6-digit open-end fund codes (e.g. 110022). 600519 is a stock code and returns "no matching data". Stock data lives on a different product line, not here.
What point in time do quarterly holdings reflect? Can they show the current position?+
No. Holdings come from fund quarterly reports, disclosed only after the reporting period ends — the sample uses Q3 2026. They are always in the past tense; treating them as "what it holds now" will lead you wrong. For recent position trend, use the holdings-changes endpoint (Institutional).
The rating field returns null — is that 0 stars or a failed lookup?+
Neither. null means that agency did not rate this fund in that period. In practice many funds only have values from some agencies, with the others null for a long time. Do not read null as a low score, and do not judge a fund by it.
Why is there no intraday estimate for bond and money-market funds?+
They hold no equities, so the estimate model has no input and both estimates are empty. In that case the response is ok:true + has_estimate:false + reason — that is a normal result, not a failure.
What is the difference between stale and degraded?+
stale means "data was returned but it is not fresh", with stale_age_s telling you how many seconds old it is — a fallback when the upstream source is failing, not an indicator that the data is wrong. degraded means "nothing could be returned", retry later. They are mutually exclusive.
Why are return periods keyed as 1w / 1m / 1y?+
1w = last week, 1m = last month, 1y = last year; also 3m / 6m / 2y / 3y / 5y / ytd (year to date) / since (since inception). Note that "since inception" has no peer average, CSI 300 comparison or rank — those three fields return an empty string rather than 0.
Using the API
How do I send the API key — header or query?+
Use the header Authorization: Bearer YOUR_KEY — the key then never appears in a URL, access log or browser history. Adding ?key= to the URL also works, but only for quick tests in a browser. X-API-Key is not supported.
It returned 200 but ok is false — is the API broken?+
No. Business failures (fund code not found, source temporarily unavailable) come back as HTTP 200 + ok:false. Only auth, parameter, path and rate-limit problems use non-200 status codes. Check the ok field to determine success.
How many NAV rows can I get at once?+
1–50 per page, paged with page. Fund 110022 has 3,923 NAV days, which is 79 pages at 50 per page. Request a date range you actually need rather than pulling everything.
What do I do with a 429? Will I get banned?+
Wait for the number of seconds in the Retry-After header and retry. Nothing is charged and nothing is banned. There are three triggers: per-minute rate exceeded, more than 8 concurrent connections from one IP, or the daily quota exhausted (500/day without a key).
How fast are the endpoints?+
Most endpoints respond in 0.3–1.1s. Portfolio diagnostics, multi-fund comparison and the intraday estimate take about 2–3s on the first call, then well under 1s from cache. Set your client timeout to at least 10 seconds.
Can I query several hundred funds concurrently?+
Yes, but the concurrency limit is 8 per IP; beyond that you get 429. The right approach is a pipeline capped at 8, or an endpoint that already accepts multiple funds (portfolio look-through, fund comparison) so one call covers many.
Service and boundaries
Can you export a full-market dataset for me?+
We do not provide dataset exports. What we sell is API access, not data files — for a full-market cross-section, page through the screener endpoint (200 rows per page).
Where does the data come from? Is it accurate?+
From public disclosures by fund companies and distributors. We do not post-process: the value in the response is the source value, with no rewriting beyond unit conversion, and no derived figures such as computed change percentages.
How do I know when the API is down?+
GET /health needs no API key and consumes no quota, so you can wire it straight into monitoring. It returns the service name and version. Note that it also returns 429 when your source is rate limited — the protection is uniform across endpoints, with no back door for health checks.
Do you provide investment advice?+
No. We are a data API: we turn disclosed data into structured JSON. Scores, ratings and rankings are the rating agencies' own values over their own history, and constitute no investment advice. Funds carry risk.
Not answered here? Check the API reference, or get in touch.