# Anjuke Real Estate Properties and Details Scraper (`realestateapi/anjuke-real-estate-properties-and-details-scraper`) Actor

Permission-gated Anjuke resale-listing parser. It makes no source requests unless prior written authorization is confirmed.

- **URL**: https://apify.com/realestateapi/anjuke-real-estate-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Anjuke Real Estate Properties and Details Scraper

This Actor contains an offline parser for Anjuke second-hand property listings. It recognizes structured data and common listing-card HTML, retaining listing URLs, titles, rooms, area, price in 万/RMB, unit price when exposed, and source-page evidence.

Dataset rows require a stable listing identifier or listing URL plus at least one substantive property fact (such as rooms, community, floor, area, or price). A page title and link by themselves are rejected.

The current Anjuke user agreement prohibits commercial use of platform data without prior written consent, rejects crawlers, and prohibits scraping or other use without explicit written permission (agreement version effective 2025-04-10). No permission is recorded for this Actor. By default it makes zero source requests, finishes `SUCCEEDED` with `collectionStatus: SKIPPED_POLICY`, and writes no dataset rows. The checkbox is only an operator attestation; it does not grant permission. Do not enable collection unless current written permission covers it. The Actor does not solve verification challenges and does not follow redirects.

The `OUTPUT` summary uses only `SUCCEEDED` or `FAILED` for `status` and `runStatus`. It includes bounded, generic `failureReasons` and a `policyReason` when collection is skipped. A valid empty search completes successfully without placeholder rows. A source or parsing failure before any listing is saved reports `FAILED`; if a later request or storage write fails after a real listing was saved, the run remains `SUCCEEDED` with `collectionStatus: PARTIAL` and the saved-row count. Errors and access challenges are never written as dataset records.

### Input

- `authorizationConfirmed`: default `false`; set true only if prior written permission explicitly covers automated collection and copying.
- `startUrls`: HTTPS Anjuke sale-listing URLs; the default target is Beijing resale listings.
- `maxItems`: maximum listing rows across all supplied pages.
- `timeoutSecs`: per-request timeout.

### Offline validation

```bash
npm install
apify validate-schema
npm test
```

The parser tests use synthetic HTML and do not verify current source data. No live run is documented here because written permission has not been recorded. `OUTPUT` reports request count, real listing count, status, completion time, and generic failure reasons without diagnostic records.

### Dependency remediation — October 3, 2026

This Actor uses native HTTP and parser code, with a small readable default-storage adapter and the pinned official Apify logger. The unused SDK/crawler/proxy/cache dependency graph was removed because its current http-cache-semantics advisory has no released fix. Cloud storage uses the documented Apify REST interface and bearer headers; local writes append indexed JSON without overwriting historical rows. Storage failures propagate and ambiguous POST writes are not retried. Native exit codes and source authorization/access gates are preserved. Node 22.19+ is required. The source remains unqualified until its existing permission/access prerequisites are met.

Relevant advisory: https://github.com/advisories/GHSA-ch52-4w7c-c8xp. Runtime regression checks: node --test test/platform.test.js.

# Actor input Schema

## `authorizationConfirmed` (type: `boolean`):

Set true only when current written permission covers automated collection and copying of Anjuke data. This checkbox is an operator attestation and does not grant permission.

## `startUrls` (type: `array`):

HTTPS Anjuke sale-listing URLs covered by the written permission.

## `maxItems` (type: `integer`):

Maximum property records emitted across all pages.

## `timeoutSecs` (type: `integer`):

Maximum time allowed for each page request.

## Actor input object example

```json
{
  "authorizationConfirmed": false,
  "startUrls": [
    {
      "url": "https://www.anjuke.com/sale/beijing/"
    }
  ],
  "maxItems": 20,
  "timeoutSecs": 45
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/anjuke-real-estate-properties-and-details-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/anjuke-real-estate-properties-and-details-scraper").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 '{}' |
apify call realestateapi/anjuke-real-estate-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/anjuke-real-estate-properties-and-details-scraper"
        }
    }
}
```

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/epO5jwtba56ktOGMQ/builds/KS6IzYtQdQCHh2WdR/openapi.json