# D.R. Horton Properties and Details Scraper (`realestateapi/drhorton-properties-and-details-scraper`) Actor

Collect publicly displayed D.R. Horton community details and move-in-ready home listings from official community pages. The Actor reports blocked source requests in its run summary; extracted fields depend on the data returned by the source.

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

## D.R. Horton Properties and Details Scraper

This Actor is designed to extract public D.R. Horton move-in-ready home and community fields from official community pages. As of 2026-09-26, Chrome displays a Cloudflare block at the homepage, so current listings and source fields could not be verified. The dataset schema describes 21 possible fields; there are no saved property records to validate against it.

### Input

```json
{
  "communityUrls": [],
  "maxItems": 10
}
```

Empty input makes zero source requests and reports `SUCCEEDED` / `COMPLETED` with zero records. When URLs are explicitly supplied, the Actor uses the direct official page and refuses redirects. It does not use an external rendered-page reader, submit forms, use accounts, or bypass interactive challenges.

### Output

The dataset schema describes 21 possible property and community fields, including pricing, home attributes, shared community details, and floor plans. Only validated home-listing records are written to the dataset. A clean empty result is `SUCCEEDED` / `COMPLETED`; a later failure after one or more home records are saved is `SUCCEEDED` / `PARTIAL`; a failure with no saved home records is `FAILED` / `FAILED`. Only failed runs exit non-zero.

### Dependency review — October 3, 2026

The production dependency lock has been refreshed within compatible declared ranges. The `get-uri` dependency uses patched `basic-ftp@6.2.1`; offline tests cover the Client methods consumed by `get-uri`, valid listing fields, and the adversarial listing parser case. Source permissions and access gates remain unchanged.

The remaining `http-cache-semantics` security advisory [GHSA-ch52-4w7c-c8xp](https://github.com/advisories/GHSA-ch52-4w7c-c8xp) has no published patched release. It remains present through the Apify/Crawlee request stack. This project does not claim the finding is fixed or unreachable, and the audit remains part of the release limitations.

# Actor input Schema

## `communityUrls` (type: `array`):

Optional community page URLs. No URL is selected automatically.

## `communityUrl` (type: `string`):

Optional singular alias for communityUrls.

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

Maximum number of unique home listings to emit across all communities.

## `includeFloorPlans` (type: `boolean`):

Attach public floor-plan links and summary information when exposed on the community page.

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

Maximum time for each public community request.

## `requestDelayMs` (type: `integer`):

Bounded delay between public page requests in milliseconds.

## Actor input object example

```json
{
  "communityUrls": [],
  "maxItems": 10,
  "includeFloorPlans": true,
  "timeoutSecs": 45,
  "requestDelayMs": 150
}
```

# Actor output Schema

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

No description

## `output` (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/drhorton-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/drhorton-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/drhorton-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/drhorton-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/g8kOVfslxPGNAc6Cj/builds/Z8Mt2yM9NqiwbXNTF/openapi.json