Lennar Homes Scraper

Extract Lennar home listing data from Find-a-Home pages with market-level targeting and clean, structured results. Collect pricing, beds, baths, square footage, community details, plan details, and location metadata in one dataset. Built for real estate monitoring, investment analysis, and listing intelligence workflows.

Features

• Market-focused extraction - Collect listings for specific state and market combinations.
• Clean output records - Null and empty values are removed before saving.
• Rich property coverage - Includes homesite, plan, community, city, market, and state metadata.
• Scalable pagination - Pulls large result sets with configurable limits.
• Flexible filtering input - Supports advanced filter objects when needed.

Use Cases

Real Estate Market Tracking

Monitor available inventory, pricing shifts, and listing status changes in specific Lennar markets.

Investment Research

Build datasets for comparing price bands, home sizes, and community-level opportunity zones.

Competitive Intelligence

Track how inventory and pricing evolve by city, community, and plan type over time.

Lead Qualification Pipelines

Feed structured new-home data into CRM or qualification workflows for sales teams.

---

Input Parameters

Parameter	Type	Required	Default	Description
startUrl	String	No	https://www.lennar.com/find-a-home?state=FL&market=MIA	Find-a-Home URL used to auto-detect state and market query params.
results_wanted	Integer	No	20	Maximum number of output records to save.
max_pages	Integer	No	10	Maximum pages to request.
proxyConfiguration	Object	No	{"useApifyProxy": true}	Proxy settings for stable production runs.

---

Output Data

Each dataset item can contain:

Field	Type	Description
record_type	String	homesite or plan
id	String	Primary listing ID
status	String	Listing status
price	Number	Current price
beds	Number	Bedrooms
baths	Number	Bathrooms
half_baths	Number	Half bathrooms
sqft	Number	Square footage
address	String	Street address
city_name	String	City
market_code	String	Market code
state_code	String	State code
community_name	String	Community name
plan_name	String	Plan name
url	String	Detail URL
collected_at	String	ISO timestamp

Additional community, pricing, media, and metadata fields are included when available.

---

Usage Examples

Basic Miami Market Run

{
  "startUrl": "https://www.lennar.com/find-a-home?state=FL&market=MIA",
  "results_wanted": 20
}

Higher Volume Run

{
  "startUrl": "https://www.lennar.com/find-a-home?state=FL&market=MIA",
  "results_wanted": 50,
  "max_pages": 10
}

Extended Pagination Window

{
  "startUrl": "https://www.lennar.com/find-a-home?state=FL&market=MIA",
  "results_wanted": 40,
  "max_pages": 20
}

---

Sample Output

{
  "record_type": "homesite",
  "id": "h_760409",
  "homesite_id": "h_760409",
  "lot_id": "9396603304",
  "status": "MOVE_IN_READY",
  "price": 376349,
  "beds": 3,
  "baths": 2.5,
  "sqft": 1423,
  "address": "35871 SW 178 CT",
  "city_name": "Miami",
  "market_code": "MIA",
  "state_code": "FL",
  "community_name": "Seaview Collection",
  "plan_name": "Caspian",
  "url": "https://www.lennar.com/new-homes/florida/miami/miami/del-mar/seaview-collection/caspian/9396603304",
  "collected_at": "2026-04-03T00:00:00.000Z"
}

---

Tips for Best Results

Start Small

• Begin with results_wanted: 20 to validate output quickly.
• Increase gradually for larger production collections.

Tune Pagination

• Keep max_pages high enough for your target volume.
• Use results_wanted: 20 for fast QA-friendly runs.

Use Valid Market Codes

• Ensure startUrl includes valid state and market query params.
• Example: https://www.lennar.com/find-a-home?state=FL&market=MIA.

Use Proxies for Reliability

• Enable proxyConfiguration for long-running or frequent jobs.
• Residential traffic pools can improve consistency for high-volume usage.

---

Integrations

Connect your data with:

• Google Sheets - Share listing snapshots with non-technical teams.
• Airtable - Build searchable housing intelligence tables.
• Make - Trigger downstream workflows after every run.
• Zapier - Connect listing updates to alerts and internal tools.
• Webhooks - Deliver records to custom services in real time.

Export Formats

• JSON - Native structured output
• CSV - Spreadsheet workflows
• Excel - Reporting and dashboards
• XML - Legacy system compatibility

---

Frequently Asked Questions

How many listings can I collect?

You can collect as many as available in the selected market, limited by your results_wanted and max_pages settings.

Why are some fields missing in certain rows?

Only values present on the source side are saved. Empty and null values are intentionally removed.

Can I run this for other states and markets?

Yes. Provide a different startUrl with the target state and market query params.

Is this suitable for scheduled monitoring?

Yes. The actor is designed for repeatable runs and works well with scheduling.

---

Support

For issues or feature requests, use the Apify Console issue and support channels.

Resources

• Apify Documentation
• Apify API Reference
• Apify Schedules

---

Legal Notice

This actor is intended for lawful data collection and analysis. You are responsible for complying with website terms, local laws, and all applicable regulations when using extracted data.