jiage.autohome.com.cn APIjiage.autohome.com.cn ↗
Retrieve owner-reported car purchase prices and trim specs from Autohome's jiage platform. Filter by city, spec ID, and pagination across 2 endpoints.
curl -X GET 'https://api.parse.bot/scraper/afeac0a0-7928-4c84-a531-d368a6734bfa/get_price_list?page=1&max_pages=1' \ -H 'X-API-Key: $PARSE_API_KEY'
Get car owner price listings with pagination. Returns purchase details including user info, dates, location, and price data. Price values may be partially decoded due to site-side obfuscation techniques.
| Param | Type | Description |
|---|---|---|
| page | integer | Starting page number. |
| spec_id | string | Car spec ID. Use get_spec_list to find available IDs for a series. |
| max_pages | integer | Number of pages to fetch (10 entries per page). |
| user_city | string | User city code for regional display. |
| city_filter | string | City code filter. 0 for nationwide, or a city code such as 310100 for Shanghai, 320500 for Suzhou. |
{
"type": "object",
"fields": {
"page": "integer - starting page number",
"entries": "array of objects with user_name, post_date, car_name, bought_time, location, naked_price, full_price, msrp, vehicle_tax, purchase_tax, compulsory_insurance, commercial_insurance, registration_fee, payment_method, helpful_count, price_id",
"spec_id": "string - the spec ID queried",
"city_filter": "string - city filter applied",
"total_count": "integer - total number of entries available",
"total_pages": "integer - total pages available",
"pages_fetched": "integer - number of pages actually fetched"
},
"sample": {
"data": {
"page": 1,
"entries": [
{
"msrp": "14.99",
"car_name": "2026款 3000万辆甄选款 300TSI DSG 飞越版",
"location": "四川,泸州",
"price_id": "43091024",
"post_date": "2026-01-21",
"user_name": "之家车友0161702",
"full_price": ".0",
"bought_time": "2026年01月19日",
"naked_price": "0",
"vehicle_tax": "4",
"purchase_tax": "4446",
"helpful_count": "0",
"payment_method": "全款",
"registration_fee": "",
"commercial_insurance": ",433,,",
"compulsory_insurance": "9"
}
],
"spec_id": "75178",
"city_filter": "0",
"total_count": 10,
"total_pages": 1,
"pages_fetched": 1
},
"status": "success"
}
}About the jiage.autohome.com.cn API
The Autohome Jiage API exposes 2 endpoints for pulling real owner-reported vehicle purchase data from jiage.autohome.com.cn, China's largest automotive pricing community. The get_price_list endpoint returns paginated entries with naked price, full price, MSRP, vehicle tax, location, and purchase date for a given spec. The get_spec_list endpoint maps a series ID to its available trims and year groups, giving you the spec IDs needed to query pricing data.
What the API Returns
The get_price_list endpoint returns owner-submitted transaction records for a specific car trim (spec_id). Each entry includes user_name, post_date, bought_time, location, naked_price (pre-tax vehicle price), full_price (total out-of-pocket), msrp, and vehicle_tax. Results are paginated at 10 entries per page; you control the starting page with page and how many pages to pull with max_pages. The total_count and total_pages fields in the response let you plan full crawls without guessing.
Filtering by Region and Trim
Set city_filter to 0 for nationwide results or pass a city code such as 310100 (Shanghai) or 320500 (Suzhou) to narrow to a specific market. The user_city parameter adjusts regional display context. To target a specific trim, pass a spec_id; use get_spec_list first to enumerate available specs for a series_id. That endpoint returns year groups (e.g. 2026款) each containing an array of specitems with id, name, state, and minprice/maxprice range strings.
Known Data Quirks
Price fields in get_price_list may be partially decoded. The source site applies obfuscation to some price values, so a minority of naked_price or full_price entries may appear incomplete or encoded rather than as clean numeric values. Build defensive parsing in any pipeline that depends on these fields.
Finding Series and Spec IDs
Neither endpoint auto-discovers series IDs. You need to supply a valid series_id to get_spec_list. Series IDs follow Autohome's standard vehicle taxonomy — cross-reference the Autohome series listing pages to map a make/model to its numeric ID before querying.
- Compare owner-paid
naked_pricevsmsrpacross trims to estimate real-world dealer discounts - Filter
city_filterby city code to analyze regional pricing variation for the same spec - Aggregate
full_priceentries over time usingpost_dateandbought_timeto track transaction price trends - Use
get_spec_listto enumerate all active trims and price bands for a model year before targeting specific spec IDs - Build a new-car budget tool for Chinese buyers by combining MSRP, vehicle tax, and full price fields
- Monitor
total_countchanges over spec IDs to estimate relative sales volume by trim
| 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 Autohome provide an official developer API?+
What does get_spec_list return and how do I use it with get_price_list?+
series_id to get_spec_list and it returns year groups, each containing a specitems array. Each spec item has an id, name (trim label), state (availability), and minprice/maxprice strings. Take any id from that array and pass it as spec_id to get_price_list to pull owner transaction records for that exact trim.Why are some price values incomplete or encoded?+
naked_price and full_price values in some entries may not decode to clean numbers. This is a known limitation documented in the get_price_list endpoint description. Plan for null-checking or fallback handling when processing these fields at scale.Does the API cover used-car prices or dealer inventory listings?+
Can I retrieve full specifications like engine displacement, fuel type, or safety ratings?+
get_spec_list returns trim identifiers, names, and MSRP price ranges, but not detailed mechanical or safety specifications. You can fork this API on Parse and revise it to add an endpoint that fetches full spec sheets for individual trim IDs.