NewHomeSource Scraper: New Construction Homes, Floor Plans, Builders and Communities

NewHomeSource Scraper turns NewHomeSource into a clean new-construction data feed. Pick a US state (optionally narrow to one city) and get every matching community and every home or floor plan inside it, or paste specific community and home links to scrape only those. Each result is one flat row with home specs, price, address, geo coordinates, community context and builder contact, ready for JSON, CSV, Excel or your own API.

Why This Scraper?

• Two ways to find data. Walk a whole state, optionally narrowed to one city, in search mode, or paste specific community and home links in URL mode. No need to build URLs by hand.
• One flat row per home. Every result carries the home's own specs, price and status alongside the community's price band, floor-plan count, quick-move-in count and address, and the builder's name, id and phone, all in one record.
• State-wide coverage on demand. Pick a state once and the actor walks its market areas, every community inside them, and every home or floor plan inside each community.
• Optional deep detail. Turn on full detail extraction to add the complete specification, photo gallery, videos, amenities, fees, school districts and sales-office contact per home, billed only for homes actually returned.
• Filters that narrow before you pay. Home type, price, bedroom, bathroom and size bounds apply to both search and URL mode, so filtered-out homes are never collected or charged.
• Built for monitoring. Incremental mode tracks a search over time and returns only new and changed homes on recurring runs, and a run that could not reach the data source fails loudly instead of returning an empty dataset.
• Resume without re-paying. Continue an interrupted run from its run or dataset id and skip everything already collected there.

Use Cases

• Builder and market research: track price bands, floor-plan counts and quick-move-in inventory across a state or metro to see where builders are pricing and releasing homes.
• Real estate lead generation: collect builder and community contact details alongside home specs for outreach or CRM import.
• Listing and price monitoring: schedule the actor with incremental mode to catch new homes, price changes and homes that sell out.
• Market analytics and dashboards: feed home counts, price ranges and geo coordinates into a BI tool or map to visualize new-construction supply.
• Relocation and homebuying tools: power a search or comparison app with structured floor plan, price and school-district data.

Data You Get

Sample shape: values are illustrative placeholders, not from a live record.

Field	Example
homeId	2787050
floorPlan	"The Pearson"
bedrooms / bathrooms	4 / 3
halfBathrooms / garageCount	1 / 2
stories / homeSizeSqft	2 / 2450
homePrice	385990
status / homeType	"Active" / "Single Family"
isSpec	false
moveInDate	"2025-06-01"
address	"123 Example Lane"
city / state / zip	"Example City" / "TX" / "75001"
latitude / longitude	"32.7767" / "-96.7970"
communityId / communityName	202479 / "Sample Community"
communityMinHomePrice / communityMaxHomePrice	320000 / 450000
totalFloorPlans / qmiCount	8 / 3
builderId / builderName	5501 / "Sample Builder Homes"
phone	"555-0100"
homeUrl	link to the home or floor plan page
communityUrl	link to the community page
schoolDistricts	[{"id": null, "name": "Example County Schools"}]
changeType	"NEW" (incremental mode only)

Turning on full detail extraction, or pasting a specific home link (see below), adds a larger set of fields to the same row: description and marketingDescription, lotSqft, the full photo gallery (images, imagesCount), videos, tourUrl and planViewerUrl, the builder's builderUrl, the sales office's salesOfficeAddress, salesOfficeEmail and salesOfficePhone, schools and a detailed schoolDistricts, agents, homeOptions, feesAndRates, utilities, amenities, customAmenities and planAmenities, plus the community's own communityImages, communityVideos, communityHours, communityDirections, communityMapUrl, communitySchoolDistricts, communitySchools and communityAgents. (The brand fields brandId, brandLogo and brandSiteUrl are already present on every record; full detail only refreshes them.) In incremental mode, changedFields, firstSeenAt and lastSeenAt are added alongside changeType.

How to Use

1. Pick a mode: search (walk a US state, optionally one city) or url (paste specific community or home links).
2. Set the home type, price, bedroom, bathroom and size filters. They apply to both modes, and homes they exclude are never collected or charged.
3. Optionally turn on Fetch full home details to add the full specification, photo gallery, amenities and sales-office contact per home, billed only for homes returned.
4. Set Max items to cap run size and cost, then click Start.

Search a whole state:

{
  "mode": "search",
  "state": "Texas",
  "maxItems": 50
}

Search one city with filters:

{
  "mode": "search",
  "state": "Florida",
  "city": "Orlando",
  "homeTypes": ["qmi"],
  "minPrice": 350000,
  "maxPrice": 600000,
  "minBedrooms": 3,
  "maxItems": 100
}

Paste community and home links:

{
  "mode": "url",
  "urls": [
    "https://www.newhomesource.com/community/id/kuna/medallion-at-valor-by-tresidio-homes/202479",
    "https://www.newhomesource.com/plan/the-pearson-smith-douglas-homes-columbiana-al/2787050"
  ]
}

Recurring monitoring with incremental mode:

{
  "mode": "search",
  "state": "North Carolina",
  "incrementalMode": true,
  "stateKey": "nc-monitor",
  "maxItems": 0
}

Run it from your code

Python:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/newhomesource-scraper").call(run_input={"mode": "search", "state": "Texas", "maxItems": 50})
for home in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(home["floorPlan"], home["homePrice"], home["city"])

JavaScript:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/newhomesource-scraper').call({ mode: 'search', state: 'Texas', maxItems: 50 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the Integrations tab.

Detail enrichment and billing

Turning on Fetch full home details adds one extra request per home for the full specification, gallery, videos, amenities, fees, utilities and sales-office contact, plus one request for the home's community details. The detail-enrichment surcharge is charged once per home that is both enriched and actually returned in the dataset, never per fetch alone. A home suppressed by incremental mode because it is unchanged since the last run still has its detail page read to compute the comparison, but it is never billed the surcharge if it is not returned. Pasted single-home links (plan, specdetail, basichome) always fetch and return full detail and community context, and are always charged the surcharge, because those links only resolve through the detail endpoint; the toggle only controls whether homes found by a state or city search, or by a pasted community link, also fetch full detail per home.

Resume and recurring updates

• Resume (resumeFromRunId): paste a previous run or dataset id to continue an interrupted run without returning or re-charging homes already collected there.
• Incremental mode (incrementalMode): for scheduled runs over the same search. Each home is classified NEW the first time it is seen, UPDATED (with changedFields listing what changed) when its data differs from the stored baseline, or UNCHANGED (suppressed and not billed unless emitUnchanged is on). Turning on emitExpired marks homes no longer found as EXPIRED, but only once a run reaches the natural end of every scope it tracks, not when Max items or Max pages cut a walk short, and not on a Resume run; a partial run leaves the previous state untouched instead of guessing. REAPPEARED is not a routine result: it only appears for a home that an earlier complete run, with emitExpired on, had already marked EXPIRED, and that is then found again on a later run. stateKey names or shares the stored state; leave it empty and the actor derives one automatically from the state, city, URLs and filters, so different searches never mix state with each other.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape; the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each home, not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify > Settings > Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. If the picker is empty, you have not authorized a connector yet.
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Input Parameters

Parameter	Type	Default	Description
mode	string	search	search walks a state (optionally one city); url scrapes only pasted links.
state	string	Alabama	US state to walk in search mode. The default is just a starting example, pick any state.
city	string	(none)	Optional. Narrow a state search to one city. Search mode only.
urls	array	none (prefill: 2 sample NewHomeSource links)	NewHomeSource community or home links. URL mode only.
homeTypes	array	["floorplan", "qmi"]	Which kinds of listings to include: floor plans, QMI / spec homes, or both.
minPrice	integer	(none)	Only keep homes priced at or above this amount.
maxPrice	integer	(none)	Only keep homes priced at or below this amount.
minBedrooms	integer	(none)	Only keep homes with at least this many bedrooms.
minBathrooms	integer	(none)	Only keep homes with at least this many bathrooms.
minSqft	integer	(none)	Only keep homes at least this many square feet.
maxSqft	integer	(none)	Only keep homes at most this many square feet.
fetchDetails	boolean	false	Fetch the full specification, gallery, videos and sales-office contact per home. Billed as a per-home surcharge for homes returned.
maxItems	integer	20	Stop after this many home rows across all searches or URLs. 0 = unlimited.
maxPages	integer	0	Optional hard cap on result pages walked per state, city or URL. 0 = unlimited.
resumeFromRunId	string	(none)	Continue one interrupted run without re-collecting or re-charging its homes.
incrementalMode	boolean	false	Turn on for recurring runs over the same search: classify homes as new, updated, unchanged, expired or reappeared.
stateKey	string	(none)	Name or share an incremental-mode state. Leave empty to derive one automatically from the search setup.
emitUnchanged	boolean	false	Also return (and bill) homes unchanged since the last run. Incremental mode only.
emitExpired	boolean	false	Also return (and bill) homes no longer found, once a run completes a full scan. Incremental mode only.
proxy	object	Apify Proxy enabled	Connection settings.
mcpConnectors	array	(none)	Optional: send a summary of each home to apps you authorized under Integrations.
notionParentPageUrl	string	(none)	Notion connector only: page under which home pages are created.
maxNotifyListings	integer	50	Cap on items written to each connector per run.

Output Example

Sample shape: values are illustrative placeholders, not from a live record.

{
  "homeId": 2787050,
  "planId": 145201,
  "specId": null,
  "floorPlan": "The Pearson",
  "bedrooms": 4,
  "bathrooms": 3,
  "halfBathrooms": 1,
  "garageCount": 2,
  "stories": 2,
  "homeSizeSqft": 2450,
  "homePrice": 385990,
  "status": "Active",
  "homeType": "Single Family",
  "isSpec": false,
  "moveInDate": "2025-06-01",
  "address": "123 Example Lane",
  "city": "Example City",
  "county": "Example County",
  "state": "TX",
  "zip": "75001",
  "latitude": "32.7767",
  "longitude": "-96.7970",
  "communityId": 202479,
  "communityName": "Sample Community",
  "communityMinHomePrice": 320000,
  "communityMaxHomePrice": 450000,
  "totalFloorPlans": 8,
  "qmiCount": 3,
  "builderId": 5501,
  "builderName": "Sample Builder Homes",
  "phone": "555-0100",
  "brandId": 12,
  "brandLogo": "https://example.com/logo.png",
  "homeUrl": "https://www.newhomesource.com/plan-detail/2787050",
  "communityUrl": "https://www.newhomesource.com/community/tx/example-city/sample-community/202479",
  "searchMode": "search",
  "schoolDistricts": [{ "id": null, "name": "Example County Schools" }]
}

Plan Requirement

Apify Proxy works out of the box; leave it enabled under Connection. The storefront's listing data is served only to US connections, so keep Apify Proxy enabled, or supply your own US connection, for reliable results outside the US. If a connection attempt is refused, the actor automatically switches to a different connection for the rest of the run instead of failing outright.

FAQ

How much does it cost?

You are charged per home returned in the dataset, plus a smaller per-home charge only for homes returned with full detail extraction enabled, plus a small per-run start charge. The Pricing tab on the actor page shows the current rates. Use Max items to cap the cost of any run.

Is it legal to scrape NewHomeSource?

This actor collects only publicly available new-construction listing data. You are responsible for how you use it: follow NewHomeSource's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Listing facts like price, specs and address are generally not protected, but photos, floor-plan renderings and marketing copy may be subject to third-party rights.

Can I get only new or changed homes on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Later runs then return only new and updated homes, and unchanged homes are not billed unless you also turn on Emit unchanged.

Do pasted single-home links always come back with full detail?

Yes, and this is the most common source of confusion. A pasted plan, specdetail or basichome link only exists as a detail record on the storefront, so the actor always fetches and returns its full detail and community context for that link, and always applies the detail-enrichment surcharge, no matter how Fetch full home details is set. That toggle only controls whether homes found by a state or city search, or by a pasted community link, also get the extra fetch.

Why does a run sometimes fail instead of returning an empty dataset?

If every attempt to reach the listing data failed this run and nothing was scanned, the actor fails the run with a clear message instead of reporting a false empty success, so a saved incremental baseline is never corrupted by a single outage. Try again shortly. If the account's connection specifically was refused, the message says so; that points to a plan or connection-access limit, not an empty result.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push a summary of results into Notion, Linear or Airtable.

🔗 Want more real estate data?

Pair this actor with these related scrapers from the same team:

🏠 Lennar Homes, Communities & Floor Plans Scraper Scrape Lennar new-home communities, move-in-ready homes and floor plans. Extract prices...	🏠 DR Horton From $1/1K. Extract new-home data from drhorton.com, America’s largest homebuilder. Pull...
🏠 Redfin Scraper Scrape redfin.com home listings: price, beds, baths, sqft, lot, year built, coordinates...	🏠 Rent.com Scraper Extract rental listings from rent.com. Get comprehensive data including monthly rent...
🏠 Homes.co.nz Scraper Scrape Homes.co.nz listings by location or URL with pagination. Extract property details...	🏠 Properstar Extract property listings from Properstar across global domains like .com, .co.uk, .ch...

👉 Browse all abotapi scrapers

💬 Support & custom scrapers

• 🐞 Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
• 🛠️ Need another site, extra fields or a private build? Email abotapi@proton.me or message Telegram @abotapi.
• ⭐ Enjoying it? A quick review on the actor page helps other users find it.