/sinafinance/funds

POST /api/sinafinance/funds

Price: 1 credit

Get a Chinese mutual fund from Sina Finance: latest unit and accumulated NAV, trading status, management, custody, purchase and redemption fees with their tiers, top stock and bond holdings, industry and asset allocation

How to use it

Fees are in percent; holdings and allocations come from the latest quarterly report, dated by report_date.

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 Sina fund page URL (examples: "000001", "https://finance.sina.com.cn/fund/quotes/000001/bc.shtml")

Response

• @type string (default: "SinafinanceFund")
• code string required
• url string required
• name string nullable
• nav number nullable
• accumulated_nav number nullable
• previous_nav number nullable
• nav_date integer nullable
• total_shares number nullable
• trading_status string nullable
• management_fee_percent number nullable
• custody_fee_percent number nullable
• sales_service_fee_percent number nullable
• purchase_fee_percent number nullable
• discounted_purchase_fee_percent number nullable
• min_purchase string nullable
• min_redemption string nullable
• purchase_fee_tiers array (default: [])
  • @type string (default: "SinafinanceFeeTier")
  • condition string required
  • fee_percent number nullable
  • discounted_fee_percent number nullable
• redemption_fee_tiers array (default: [])
  • @type string (default: "SinafinanceFeeTier")
  • condition string required
  • fee_percent number nullable
  • discounted_fee_percent number nullable
• top_stocks array (default: [])
  • @type string (default: "SinafinanceFundPosition")
  • symbol string nullable
  • name string required
  • market_value number nullable
  • nav_percent number nullable
  • market_value_change number nullable
  • nav_percent_change number nullable
  • report_date integer nullable
• top_bonds array (default: [])
  • @type string (default: "SinafinanceFundPosition")
  • symbol string nullable
  • name string required
  • market_value number nullable
  • nav_percent number nullable
  • market_value_change number nullable
  • nav_percent_change number nullable
  • report_date integer nullable
• top_funds array (default: [])
  • @type string (default: "SinafinanceFundPosition")
  • symbol string nullable
  • name string required
  • market_value number nullable
  • nav_percent number nullable
  • market_value_change number nullable
  • nav_percent_change number nullable
  • report_date integer nullable
• industry_allocation array (default: [])
  • @type string (default: "SinafinanceIndustryWeight")
  • industry string required
  • nav_percent number nullable
  • market_value number nullable
  • report_date integer nullable
• asset_allocation array (default: [])
  • @type string (default: "SinafinanceAssetLine")
  • name string required
  • value number nullable
  • report_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.