/eastmoney/stocks/financials

POST /api/eastmoney/stocks/financials

Price: 20 credits

Get the income statement, balance sheet, cash flow statement or key financial indicators of a Shanghai, Shenzhen or Beijing listed company from East Money, one row per reported period with every line item and, where reported, its year-on-year change

How to use it

Line-item names are East Money's own column names in lower case; amounts are in the report currency and change_yoy_percent is in percent.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbol string required — Stock code of a Shanghai, Shenzhen or Beijing listing, or its East Money quote page URL (examples: "600519", "SZ000001", "https://quote.eastmoney.com/sh600519.html")
• count integer required — Max number of report periods to return, newest first (min: 1)
• statement string — Financial statement (default: "income"; one of: "income", "balance", "cash_flow", "indicators")
• period string — Every reported period, or annual reports only (default: "all"; one of: "all", "annual")

Response

• @type string (default: "EastmoneyFinancialReport")
• secucode string required
• statement string required
• company_name string nullable
• report_name string nullable
• report_type string nullable
• report_date integer nullable
• published_date integer nullable
• updated_date integer nullable
• currency string nullable
• metrics array (default: [])
  • @type string (default: "EastmoneyFinancialMetric")
  • name string required
  • value number nullable
  • change_yoy_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 — No Shanghai, Shenzhen or Beijing listed company under that symbol 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.