/eastmoney/research_reports/search

POST /api/eastmoney/research_reports/search

Price: 5 credits

Search broker research reports on Chinese listed companies collected by East Money, by covered stock, industry, broker, rating, rating change and publication window: title, broker, analysts, rating and its change, target price and EPS and P/E forecasts

How to use it

eps_forecasts years_ahead 0 is the current fiscal year, 1 the next, -1 the last one while its annual report is not out. industry_code and broker_id values appear on each report's industry_code and broker_id.

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 reports to return, newest first (min: 1; max: 5000)
• stock_code string nullable — Six-digit code of the covered stock (examples: "600519", "300750")
• industry_code string nullable — East Money industry code of the covered stocks (examples: "1277", "1250")
• rating string nullable — East Money's normalised rating of the covered stock (one of: "buy", "overweight", "hold", "neutral", "sell")
• rating_change string nullable — How the rating moved against the broker's previous report on the stock (one of: "upgraded", "downgraded", "initiated", "maintained")
• broker_id string nullable — East Money id of the broker that published the report (examples: "80000031", "80036717")
• published_from integer nullable — Earliest publication day, as unix seconds; defaults to two years before published_to (examples: 1727654400)
• published_to integer nullable — Latest publication day, as unix seconds; defaults to today (examples: 1790726400)

Response

• @type string (default: "EastmoneyResearchReport")
• id string required
• stock_code string nullable
• stock_name string nullable
• market string nullable
• industry_code string nullable
• industry_name string nullable
• broker_id string nullable
• broker_name string nullable
• broker_short_name string nullable
• researchers array (default: [])
• rating string nullable
• previous_rating string nullable
• broker_rating string nullable
• target_price_high number nullable
• target_price_low number nullable
• eps_forecasts array (default: [])
  • @type string (default: "EastmoneyEpsForecast")
  • years_ahead integer required
  • eps number nullable
  • pe number nullable
• actual_last_year_eps number nullable
• page_count integer nullable
• published_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 — 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.