/eastmoney/stocks/profile

POST /api/eastmoney/stocks/profile

Price: 1 credit

Get the company profile of a Shanghai, Shenzhen or Beijing listed company from East Money: names, industry and concept boards, business description and revenue mix, management, controlling holder and actual controller, staff, registered capital, auditor, contacts and listing dates

How to use it

registered_capital is in the listed currency; board codes work as board in eastmoney/stocks/search.

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")

Response

• @type string (default: "EastmoneyProfile")
• secucode string required
• code string nullable
• short_name string nullable
• name string nullable
• name_en string nullable
• former_names array (default: [])
• pinyin string nullable
• org_code string nullable
• security_type string nullable
• listing_venue string nullable
• exchange string nullable
• org_form string nullable
• industry string nullable
• csrc_industry string nullable
• industry_boards array (default: [])
  • @type string (default: "EastmoneyBoard")
  • code string required
  • name string nullable
  • level integer nullable
• region_board object nullable
  • @type string (default: "EastmoneyBoard")
  • code string required
  • name string nullable
  • level integer nullable
• concept_boards array (default: [])
  • @type string (default: "EastmoneyBoard")
  • code string required
  • name string nullable
  • level integer nullable
• province string nullable
• description string nullable
• summary string nullable
• main_business string nullable
• business_scope string nullable
• top_product string nullable
• gross_margin number nullable
• revenue_segments array (default: [])
  • @type string (default: "EastmoneyRevenueSegment")
  • name string required
  • share_percent number nullable
• chairman string nullable
• legal_representative string nullable
• general_manager string nullable
• secretary string nullable
• securities_representative string nullable
• independent_directors array (default: [])
• controlling_holder string nullable
• controlling_holder_direct_percent number nullable
• controlling_holder_indirect_percent number nullable
• actual_controller string nullable
• actual_controller_direct_percent number nullable
• actual_controller_indirect_percent number nullable
• employee_count integer nullable
• executives_count integer nullable
• registered_capital number nullable
• currency string nullable
• issue_price number nullable
• registration_number string nullable
• auditor string nullable
• legal_adviser string nullable
• phone string nullable
• fax string nullable
• email string nullable
• website string nullable
• office_address string nullable
• registered_address string nullable
• postcode string nullable
• b_share_code string nullable
• h_share_code string nullable
• established_date integer nullable
• listed_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 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.