# Autohome API (`truefetch/autohome-api`) Actor

Search Autohome's public Mainland China vehicle catalog by keyword. Export normalized model, specification, price, manufacturer, image, and source-link fields.

- **URL**: https://apify.com/truefetch/autohome-api.md
- **Developed by:** [TrueFetch](https://apify.com/truefetch) (community)
- **Categories:** E-commerce, Developer tools, Integrations
- **Stats:** 2 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.48 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

**Autohome API is a autohome api that searches Mainland China vehicle series and specifications and returns 37 normalized catalog fields with guide prices and official source links.**

- **The product is catalog-oriented and does not promise live used-car inventory.**
- **Autohome is fixed by the edition identity rather than user selection.**
- **Chinese make, model, and series phrases are preserved as submitted.**
- **Model, specification, guide-price, manufacturer, and image values remain source-linked.**

[**Run a one-result test**](https://apify.com/truefetch/autohome-api) · [**View API**](https://apify.com/truefetch/autohome-api/api)

Set `max_results` to `1` for the smallest useful test. Billing includes Actor Start and only the result rows actually written to the default Dataset.

### What does Autohome API do?

Autohome API turns a public vehicle search into structured Dataset rows for Mainland China through Autohome series and specification search. It accepts the current schema inputs, follows the edition's routing rules, and writes source-linked records that can move directly into JSON, CSV, Excel, a database, or another Apify workflow.

Autohome's official search surface exposes vehicle series and specification destinations; this Actor describes those catalog records honestly rather than relabeling them as dealer stock. [See the official Autohome search](https://sou.autohome.com.cn/).

The Actor is a collection and normalization tool, not a vehicle-history report, appraisal, inspection, financing decision, or guarantee of current stock. Important commercial facts should be checked on `source_url`, because listings and catalog pages can change after collection.

### How do I run Autohome API?

Run Autohome API by starting with its prefilled scenario, reviewing one source-linked row, and increasing scope only after the data matches the intended workflow.

1. Open the [Autohome API input page](https://apify.com/truefetch/autohome-api) and review every required value.
2. Set `country` to `Mainland China`, `keyword` to `凯美瑞`, and `max_results` to `7`; for the smallest risk test, temporarily use `max_results: 1`.
3. Start the Actor and wait for the default Dataset.
4. Open `source_url` from a returned row before expanding the result ceiling or scheduling repeats.

```json
{
  "max_results": 7,
  "country": "Mainland China",
  "keyword": "凯美瑞"
}
```

The result limit is a ceiling rather than a promise. Live inventory, source access, unique listing URLs, and the fields available on each page determine how many records can be published.

### What data does Autohome API return?

Autohome API returns one object per source record using exactly 37 public fields. Values unavailable from the source remain empty; the Actor does not derive a VIN, seller, mileage, location, or vehicle specification from the keyword.

| Field group | Public fields | Meaning |
| --- | --- | --- |
| Identity and price | `main_image`, `title`, `price`, `currency`, `year`, `make`, `model`, `trim` | Primary media, listing title, asking price, and vehicle identity. |
| Mileage and geography | `mileage`, `mileage_unit`, `location`, `latitude`, `longitude`, `country` | Odometer values and source-published place data. |
| Source and seller | `platform`, `source_url`, `seller`, `seller_type` | Marketplace attribution, original listing link, and public seller context. |
| Vehicle attributes | `condition`, `body_type`, `seats`, `fuel`, `transmission`, `engine`, `drive_type`, `exterior_color`, `interior_color`, `vin` | Source-published condition, dimensions, powertrain, colors, and identifiers. |
| Lifecycle and content | `listing_id`, `posted_at`, `updated_at`, `description`, `images`, `price_text`, `official_url`, `processor`, `processed_at` | Source identity, dates, descriptive content, additional links, and processing attribution. |

This abbreviated illustrative item uses the same scenario; a real row follows the full 37-field schema.

```json
{
  "title": "凯美瑞 2026款 双擎 2.0HGVP 豪华版",
  "price": 199800,
  "currency": "CNY",
  "year": 2026,
  "make": "丰田",
  "model": "凯美瑞",
  "trim": "双擎 2.0HGVP 豪华版",
  "body_type": "中型车",
  "transmission": "E-CVT",
  "country": "China",
  "platform": "Autohome",
  "source_url": "https://www.autohome.com.cn/spec/example/",
  "processed_at": "2026-08-10T08:03:34Z"
}
```

Apify Datasets support JSON, JSONL, CSV, Excel, XML, HTML, and RSS retrieval through the [Dataset items API](https://docs.apify.com/api/v2/dataset-items-get). Keep `source_url` and `processed_at` when exporting so later reviews retain both source provenance and collection time.

### What inputs can I configure?

Autohome API exposes only inputs supported by its current runtime route, with required fields marked explicitly and no invented non-empty fallback for optional filters.

| Input | Type | Required | Behavior | Example |
| --- | --- | --- | --- | --- |
| `max_results` | integer | Yes | Maximum Autohome catalog records returned by the run. | `7` |
| `country` | string | Yes | Required market input; this edition accepts Mainland China. | `"Mainland China"` |
| `keyword` | string | Yes | Required make, model, or series phrase, normally in a source-recognized language. | `"凯美瑞"` |

The complete effective test input is formed from schema defaults overridden by prefills. API callers can replace those values, but must still send each required field with a schema-valid value.

### What platforms and markets does Autohome API cover?

Autohome API covers Mainland China through Autohome series and specification search; coverage follows the source relationships registered for this edition rather than assumptions based on the Actor's title.

The market is Mainland China and the route is Autohome. Input cannot select another platform.

Results are series and specification records. Seller, mileage, VIN, and listing-date fields often do not apply and remain empty.

Source inventory, language, seller-entered fields, and page availability change independently. The Dataset describes what was available when the run processed each record.

### Why use Autohome API?

Autohome API is useful when a repeatable API and Dataset contract matters more than manually copying vehicle cards or maintaining a source-specific export parser.

| Capability | Practical benefit |
| --- | --- |
| Catalog-accurate scope | Use records as model and specification references instead of assuming live inventory. |
| Chinese keyword preservation | Search with source-recognized names such as `凯美瑞` without automatic translation. |
| Guide-price normalization | Compare numeric and formatted catalog prices when the source supplies them. |
| Stable 37-field shape | Join catalog output with other vehicle datasets while preserving nullability. |
| Official source destinations | Review a series or specification page before using a technical value. |

A shared vehicle schema makes export convenient, but catalog records naturally leave listing-oriented fields empty. This is why null handling and source-link retention are part of a reliable downstream design rather than cleanup tasks.

### Who is Autohome API for?

Autohome API is designed for developers, China-market product researchers, automotive catalog teams, model-comparison analysts, and data operations specialists. It works for teams that need a reproducible input, structured output, and a review path back to each public source record.

Series discovery, trim comparison, guide-price sampling, manufacturer catalog review, model-name normalization, and repeat search monitoring are suitable. The seven-record Camry scenario provides a compact example with Chinese source vocabulary.

It is the wrong tool for live dealer stock, private seller leads, VIN history, transaction prices, inspection records, or guaranteed availability. Vehicle purchases, lending, insurance, safety, and regulatory decisions require independent checks beyond a scraped public listing.

### How can I use Autohome API through the API or MCP?

Autohome API has the public Actor ID `h1ZWg0My1ptyHIb2o`; the stable name form `truefetch/autohome-api` is also available for human-readable integrations.

```text
h1ZWg0My1ptyHIb2o
```

This synchronous HTTP request uses the same scenario and returns Dataset items directly:

```bash
curl -L "https://api.apify.com/v2/acts/h1ZWg0My1ptyHIb2o/run-sync-get-dataset-items?maxItems=1" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer <APIFY_TOKEN>" \
  -d '{"max_results":7,"country":"Mainland China","keyword":"凯美瑞"}'
```

Apify also provides a hosted Streamable HTTP MCP server:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=actors,docs"
    }
  }
}
```

After authentication, ask the MCP client to inspect Actor ID `h1ZWg0My1ptyHIb2o`, run the same input, and return the default Dataset rows. The [Autohome API API page](https://apify.com/truefetch/autohome-api/api) provides generated SDK and OpenAPI examples, while the [Apify MCP guide](https://docs.apify.com/integrations/mcp) documents current client setup.

### How much does Autohome API cost?

Autohome API costs $0.00730 per result on the FREE tier plus $0.01000 per Actor Start event; memory determines the number of Start events at one per GB, minimum one.

| Event or tier | Price | Billing unit |
| --- | ---: | --- |
| Actor Start | $0.01000 | Per GB of Actor memory, minimum one event. |
| Result — FREE | $0.00730 | One item written to the default Dataset. |
| Result — BRONZE | $0.00657 | One Dataset item. |
| Result — SILVER | $0.00584 | One Dataset item. |
| Result — GOLD | $0.00548 | One Dataset item. |
| Result — PLATINUM | $0.00548 | One Dataset item. |
| Result — DIAMOND | $0.00548 | One Dataset item. |

Smallest-test calculation, assuming the minimum one Start event: $0.01000 Actor Start + 1 result × $0.00730 = **$0.01730**. A run that writes no row can still incur Actor Start. Check the [live pricing page](https://apify.com/truefetch/autohome-api/pricing) before budgeting a larger workflow because prices can change.

### How does Autohome API compare with alternatives?

Autohome API is the best fit when its documented source and normalized contract match the job; broader, manual, or contractual approaches solve different problems.

| Option | Best fit | Trade-off |
| --- | --- | --- |
| Autohome API | Normalized Autohome series and specification research. | It is not a live used-car inventory feed. |
| Car Listings API | Multi-market listing research across numerous sources. | Catalog-specific Autohome semantics are less central. |
| Manual Autohome search | Exploratory research with full Chinese page context. | Not convenient for structured repeat exports. |
| A licensed catalog source | Contractual identifiers and complete native specification taxonomies. | Separate commercial access and mapping work. |

No option eliminates the need to verify a mutable vehicle advertisement before a purchase or other high-impact decision.

### What are the limits and troubleshooting steps?

Autohome API depends on public source responses, so troubleshooting begins with the exact input, the current source page, and whether the default Dataset contains a row.

| Symptom or limit | Explanation and next step |
| --- | --- |
| Dealer or VIN values are empty | The route returns catalog series/specification data, not guaranteed advertisements. |
| Another market is rejected | Mainland China is the accepted runtime country. |
| No city input exists | The Autohome request is countrywide and does not apply a user-supplied city. |
| A Chinese keyword returns nothing | Try the official model or series name shown by Autohome. |
| A specification URL changes | Catalog pages evolve; rerun and review the current source destination. |

For a reproducible report, use `max_results: 1`, include the run ID and exact input, and add one public source URL when available. Never include an Apify token, private seller data, or credentials in an [Issue](https://apify.com/truefetch/autohome-api/issues).

### Frequently asked questions

#### Which inputs are required?

`max_results`, `country`, and `keyword` are required.

#### Is this an autohome car listings api?

It is an Autohome vehicle API, but the current route returns series and specification catalog records rather than guaranteed used-car ads.

#### Can I treat it as a china car listings api?

Use it for Autohome catalog discovery in Mainland China; choose a listing-focused product when dealer inventory is required.

#### Does it translate Chinese keywords?

No. The Actor preserves the phrase sent by the user.

#### Is there a free China vehicle API?

The Actor follows Apify pay-per-event pricing, although a small test may fit within your account allowances.

#### Can I schedule runs to monitor Autohome models over time?

Yes. Reuse a stable series keyword and compare model, trim, price text, and source URLs between Datasets.

#### Why are mileage and seller empty?

Those concepts may not exist in an Autohome series/specification response.

### Related TrueFetch Actors

Three TrueFetch Actors cover the closest adjacent vehicle markets without duplicating this Actor's exact source scope.

- [Car Listings API](https://apify.com/truefetch/car-listings-api) — Use it for multi-market public listing research.
- [CarDekho API](https://apify.com/truefetch/cardekho-api) — Use it for India vehicle inventory.
- [Webmotors API](https://apify.com/truefetch/webmotors-api) — Use it for Brazil marketplace listings.

### Support

Use the [Store page](https://apify.com/truefetch/autohome-api) for the input, the [API page](https://apify.com/truefetch/autohome-api/api) for generated integration examples, and [Issues](https://apify.com/truefetch/autohome-api/issues) for a reproducible bug. Discuss vehicle-data workflows in the [TrueFetch community on Telegram](https://t.me/TrueFetch).

[**Run a focused Autohome API test**](https://apify.com/truefetch/autohome-api) · [**Open the Autohome API API**](https://apify.com/truefetch/autohome-api/api)

**Last Updated:** August 10, 2026

# Actor input Schema

## `max_results` (type: `integer`):

Maximum Autohome series or specification records returned by this catalog search.

## `country` (type: `string`):

Required market input; this source-locked Autohome API accepts Mainland China.

## `keyword` (type: `string`):

Required Autohome make, model, or series phrase preserved in the source language.

## Actor input object example

```json
{
  "max_results": 7,
  "country": "Mainland China",
  "keyword": "凯美瑞"
}
```

# Actor output Schema

## `results` (type: `string`):

Open the overview table for normalized vehicle listings from the selected supported platforms.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "max_results": 7,
    "country": "Mainland China",
    "keyword": "凯美瑞"
};

// Run the Actor and wait for it to finish
const run = await client.actor("truefetch/autohome-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "max_results": 7,
    "country": "Mainland China",
    "keyword": "凯美瑞",
}

# Run the Actor and wait for it to finish
run = client.actor("truefetch/autohome-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "max_results": 7,
  "country": "Mainland China",
  "keyword": "凯美瑞"
}' |
apify call truefetch/autohome-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,truefetch/autohome-api"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/h1ZWg0My1ptyHIb2o/builds/tcmXBipOsYDhf08bT/openapi.json