# Batdongsan Properties and Details Scraper (`realestateapi/batdongsan-properties-and-details-scraper`) Actor

Permission-gated parser for source-backed Vietnamese property listings. Collection is disabled by default while public access remains unverified.

- **URL**: https://apify.com/realestateapi/batdongsan-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

## Batdongsan Properties and Details Scraper

### Review status

This folder contains an extractor implementation intended for public Vietnamese property pages, but its current field coverage is **not live-verified**. Chrome displayed the source's security-verification page during the September 24, 2026 review. The actor-local instructions require skipping enrichment after a challenge and prohibit alternate clients or bypass routes.

There are no saved dataset or key-value-store records. The dataset schema's 26 fields describe a possible output contract only; the synthetic parser fixture is not source evidence. No current listing values have been verified.

### Inputs

The input schema accepts explicit official HTTPS search/detail URLs and a maximum result count. By default `sourceAccessConfirmed` is false, so the Actor makes zero source requests and reports `SUCCEEDED / SKIPPED_POLICY`. Set it true only after ordinary public access is confirmed and applicable terms permit this use. The flag does not clear or bypass a security challenge.

### Output contract

The schema lists possible listing identifiers, prices, areas, property attributes, location, descriptions, agent fields, images, and publication/update dates. Until a permitted source page can be reviewed, do not claim that these fields are emitted accurately.

### Access and offline checks

Do not interact with the security challenge or retry through another browser, HTTP client, proxy, or indirect route. The input no longer allows a caller-supplied User-Agent, and parser tests verify that a visible security-verification page is not emitted as a property listing. No Actor run or source request was made for this review. `npm test` and `apify validate-schema` check only offline parser fixtures and Actor schemas; they do not prove live extraction.

### Run status

The Actor saves only listing rows with a title, official listing URL, and at least one substantive property fact, along with source URL, HTTP status, and capture time. Diagnostics are kept out of the dataset. Run summaries report run-local counts and bounded failure reasons. Redirects and access challenges stop later requests. An unrecognized or blocked page is FAILED / FAILED when no property row has been saved; a later request failure after property rows is SUCCEEDED / PARTIAL.

### Runtime dependency remediation

Batch input and JSON storage use the documented Apify REST API and isolated local JSON storage, with environment-only credentials, bounded requests, no platform redirects, and no automatic dataset-POST retry. The Actor does not import the full Apify/Crawlee SDK. Source collection rules and authorization gates are unchanged. This adapter does not provide request queues, proxies, browser automation, encrypted input fields, or long-running system-event migration. Those capabilities are not used by this implementation.

# Actor input Schema

## `sourceAccessConfirmed` (type: `boolean`):

Only set true after a normal public page has been confirmed and current terms allow this use. This is an operator attestation and does not bypass a security challenge.

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

Explicit official HTTPS search or property-detail URLs. Required when source access is confirmed.

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

Maximum property listing records to emit.

## `timeoutMs` (type: `integer`):

Maximum time for each public page request.

## Actor input object example

```json
{
  "sourceAccessConfirmed": false,
  "startUrls": [],
  "maxItems": 50,
  "timeoutMs": 20000
}
```

# Actor output Schema

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

Property listing records parsed from supplied Batdongsan pages.

## `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/batdongsan-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/batdongsan-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/batdongsan-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/batdongsan-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/UNeni1og1PpRO193R/builds/PAdDaM9Rls87nBtkA/openapi.json