/eastmoney/funds

POST /api/eastmoney/funds

Price: 5 credits

Get a Chinese mutual fund's profile from East Money (Tiantian Fund): names, type, management company, custodian, managers, benchmark, net assets, shares, fees, investment objective, scope, strategy and inception date

How to use it

Management, custody and sales-service fees are percent per year; net_assets is in CNY. Find fund codes with eastmoney/funds/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• fund string required — Six-digit fund code or East Money fund page URL (examples: "110011", "https://fund.eastmoney.com/110011.html", "https://fundf10.eastmoney.com/jbgk_110011.html")

Response

• @type string (default: "EastmoneyFund")
• code string required
• url string nullable
• name string nullable
• short_name string nullable
• fund_type string nullable
• company_id string nullable
• company_name string nullable
• custodian string nullable
• managers array (default: [])
  • @type string (default: "EastmoneyFundManager")
  • id string required
  • name string nullable
• benchmark string nullable
• tracking_index string nullable
• net_assets number nullable
• net_assets_date integer nullable
• shares_outstanding number nullable
• inception_shares number nullable
• dividends_summary string nullable
• management_fee_percent number nullable
• custody_fee_percent number nullable
• sales_service_fee_percent number nullable
• max_subscription_fee_percent number nullable
• max_purchase_fee_percent number nullable
• max_redemption_fee_percent number nullable
• investment_objective string nullable
• investment_philosophy string nullable
• investment_scope string nullable
• investment_strategy string nullable
• dividend_policy string nullable
• risk_return_profile string nullable
• issue_date integer nullable
• inception_date integer 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 — No fund under that code 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.