xuangu.eastmoney.com APIxuangu.eastmoney.com ↗
Access EastMoney Xuangu's AI stock screener via API: filter stocks by fundamentals, technicals, news, and popularity. Get hot conditions, community posts, and real-time queries.
curl -X GET 'https://api.parse.bot/scraper/46b5c961-06e6-4621-8f3c-953a5849d606/screen_stocks?query=PE%3C20&page_no=1&page_size=50' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for stocks using natural language or filter conditions on EastMoney's AI stock screener. Returns matching stocks with market data columns and total count.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword or natural language query (e.g. 'PE<20', '市值>1000亿') |
| page_no | integer | Page number |
| page_size | integer | Results per page |
{
"type": "object",
"fields": {
"result": "object containing columns array, dataList array of matching stocks, total count, and meta information",
"resultType": "result type indicator (null for standard results)",
"responseConditionList": "array of parsed filter conditions applied"
},
"sample": {
"data": {
"result": {
"total": 42,
"columns": [
{
"key": "SECURITY_CODE",
"title": "代码"
}
],
"dataList": [
{
"NEWEST_PRICE": "1346.00",
"SECURITY_CODE": "600519",
"SECURITY_SHORT_NAME": "贵州茅台"
}
]
},
"resultType": null,
"responseConditionList": [
{
"isValid": true,
"describe": "PE<20"
}
]
},
"status": "success"
}
}About the xuangu.eastmoney.com API
This API exposes 11 endpoints covering EastMoney's Xuangu AI stock screening platform, letting you search stocks via natural language queries, retrieve hierarchical filter condition trees, and pull real-time trending searches. The screen_stocks endpoint accepts plain-language or formula-style inputs like PE<20 or 市值>1000亿 and returns matching stocks with price, market cap, PE ratio, and trading volume, along with the parsed filter conditions applied to produce the results.
Stock Screening and Filter Conditions
The screen_stocks endpoint is the core of the API. It accepts a query string in natural language or filter notation, plus optional page_no and page_size parameters for pagination. Results come back as a result object containing a columns array describing the data fields, a dataList array of matching stocks, a total count, and a responseConditionList showing how the query was interpreted as structured filters. The get_stock_detail endpoint works similarly but takes a specific stock code and returns that single stock's market data in the same structured format.
Hierarchical Filter Condition Trees
Six dedicated endpoints expose the full filter taxonomy. get_filter_conditions returns the top-level tree for stocks or funds (controlled by the domain param), where each node carries showName, fieldType, children, and domain. The specialized variants — get_filter_conditions_range, get_filter_conditions_fundamentals, get_filter_conditions_technical, get_filter_conditions_news, and get_filter_conditions_popularity — each return the children array and metadata for their respective categories. Coverage spans listing scope, valuation ratios (PE, ROE, EPS), technical indicators (MACD, KDJ, moving averages, candlestick patterns), news events (announcements, institutional research, dragon-tiger list), and popularity/limit-up status.
Trending Data and Community
get_hot_conditions returns currently trending screening presets, paginated via a last_ids JSON array. Each item in the data array includes an id, title, question, stockNum, tags, and chg (change). get_real_time_hot_queries returns a recommendations object with popular search strings and a heat_ranking object for stock heat — note that heat_ranking returns an empty object when the market is closed. get_community_posts retrieves Guba forum discussions tagged to the Xuangu topic, returning post objects with post_id, post_title, post_content, post_publish_time, and user_nickname.
- Build a stock screener UI that lets users type natural language queries and display ranked results with price and PE data from
screen_stocks. - Populate a filter sidebar dynamically using the full condition tree from
get_filter_conditionsfor both stock and fund domains. - Track which screening presets are gaining traction by polling
get_hot_conditionsand monitoringstockNumandchgover time. - Display a real-time search suggestions widget using
get_real_time_hot_queriesrecommendations during market hours. - Aggregate community sentiment signals by ingesting post titles and content from
get_community_postsfor a given period. - Validate whether a stock meets specific fundamental thresholds by querying
get_stock_detailwith its code and checking the returneddataListfields. - Map the technical indicator filter vocabulary from
get_filter_conditions_technicalto build a pattern-matching alert system.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does EastMoney provide an official developer API for the Xuangu platform?+
What does `screen_stocks` return beyond a list of matching stocks?+
result object with a columns array describing the data fields present, a dataList array of matching stocks (each row mapped to those columns), a total count of all matches, and a responseConditionList array that shows how the free-text query was parsed into structured filter conditions. This lets you both display results and inspect the query interpretation.Does the `get_real_time_hot_queries` endpoint always return heat ranking data?+
heat_ranking field returns an empty object when the Chinese stock market is closed. The recommendations object with suggested search sentences is still populated outside market hours, but applications that depend on heat_ranking should handle an empty response gracefully.Does the API support fund screening in addition to stocks?+
get_filter_conditions endpoint accepts a domain parameter set to 'fund' and returns the fund-specific filter tree. However, the screen_stocks endpoint is oriented toward stock queries, and there is no dedicated fund screening results endpoint in the current API. You can fork this API on Parse and revise it to add a fund-specific screening endpoint using the fund filter conditions.