/eastmoney/funds/search

POST /api/eastmoney/funds/search

Price: 5 credits

Rank Chinese open-end mutual funds on East Money (Tiantian Fund) by category and return over a day, week, month, quarter, half-year, year, two or three years, year to date or since inception, with NAV, five-year return and fees

How to use it

Returns are percent. Pass a code to eastmoney/funds for the profile or eastmoney/funds/nav for 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: 5000)
• fund_type string — Fund category (default: "all"; one of: "all", "equity", "mixed", "bond", "index", "qdii", "fof")
• sort_by string — Ranking field (default: "return_1y"; one of: "return_1d", "return_1w", "return_1m", "return_3m", "return_6m", "return_1y", "return_2y", "return_3y", "return_ytd", "return_since_inception", "nav")
• order string — Ranking direction (default: "desc"; one of: "desc", "asc")

Response

• @type string (default: "EastmoneyRankedFund")
• code string required
• name string nullable
• url string nullable
• pinyin string nullable
• nav_date integer nullable
• nav number nullable
• accumulated_nav number nullable
• return_1d number nullable
• return_1w number nullable
• return_1m number nullable
• return_3m number nullable
• return_6m number nullable
• return_1y number nullable
• return_2y number nullable
• return_3y number nullable
• return_5y number nullable
• return_ytd number nullable
• return_since_inception number nullable
• inception_date integer nullable
• max_purchase_fee_percent number nullable
• discounted_purchase_fee_percent number nullable

Errors

• 422 — The request body did not validate 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.