Lennar.com Scraper

What does Lennar Homes Scraper do?

Lennar Homes Scraper is a Lennar new home listings scraper that collects structured inventory from Lennar Find-a-Home market pages. Enter a Lennar URL containing a state and market code, such as Florida and Miami, and receive homesite, floor plan, and community records with prices, specifications, locations, URLs, and available media.

The dataset is useful for real estate market research, new-construction inventory monitoring, investment analysis, builder comparison, and lead qualification. Each run can collect a controlled number of records across multiple result pages and can be repeated on a schedule to compare changes over time.

Why use Lennar Homes Scraper?

• New-construction inventory data - Collect active Lennar homesites, plans, and communities from a selected market.
• Market-focused searches - Use a Lennar Find-a-Home URL for a specific state and market instead of collecting unrelated locations.
• Property research fields - Compare prices, bedrooms, bathrooms, square footage, addresses, plan names, communities, and availability details.
• Media-ready records - Save image URLs and plan virtual tour URLs when Lennar publishes them.
• Clean datasets - Empty values are removed and duplicate records are skipped within a run.
• Repeatable monitoring - Schedule runs in Apify to track new-home supply, price changes, and community availability.
• Workflow-friendly exports - Download JSON, CSV, Excel, or XML, or connect the dataset to other systems through Apify integrations.

What data can you extract from Lennar?

The Actor can return three record types: homesite, plan, and community. Fields vary by record type and by the information published for each market.

Field	Type	Description
record_type	String	Record category: homesite, plan, or community.
id	String	Primary Lennar record identifier.
homesite_id	String	Homesite identifier when the record represents an available home.
plan_id	String	Floor plan identifier when available.
status	String	Homesite status, such as move-in-ready, when published.
price	Number	Current homesite price when available.
formatted_price	String	Display-formatted price from Lennar.
beds	Number	Bedroom count.
baths	Number	Full bathroom count.
half_baths	Number	Half bathroom count.
sqft	Number	Home or plan square footage.
address	String	Homesite or community address.
plan_name	String	Floor plan name.
plan_url	String	Direct floor plan page URL.
plan_starting_price	Number	Starting price for the plan when published.
plan_virtual_tour_url	String	Virtual tour URL for the plan when available.
community_name	String	Lennar community name.
community_url	String	Direct community page URL.
community_overview	String	Community description when available.
community_base_price	Number	Community base price when published.
community_bed_range	String	Community bedroom range.
community_bath_range	String	Community bathroom range.
community_sqft_range	String	Community square-footage range.
community_address	String	Community address.
community_zip_code	String	Community ZIP code.
community_latitude	Number	Community latitude.
community_longitude	Number	Community longitude.
city_name	String	City associated with the community.
market_code	String	Lennar market code, such as MIA.
state_code	String	State code, such as FL.
state_name	String	State name when available.
image_url	String	Primary image URL.
image_urls	Array	Available listing, plan, floor plan, room, or feature image URLs.
image_count	Number	Number of URLs in image_urls.
estimated_monthly_payment	Object	Payment estimate components when published.
page_views	Object	Available page-view statistics.
url	String	Direct homesite, plan, or community page URL.
search_url	String	Lennar market URL used for the collection.
collected_at	String	ISO timestamp for the collection.

Additional fields may be included when Lennar publishes them, including badges, offer dates, lot IDs, payment components, MPC details, and Google Place IDs.

How to scrape Lennar new home listings

1. Open Lennar Homes Scraper on Apify.
2. Enter a public Lennar Find-a-Home URL with state and market query parameters.
3. Set results_wanted for the maximum number of records to save.
4. Set max_pages to control how many result pages the Actor can request.
5. Run the Actor and review the dataset preview.
6. Download the results or connect the dataset to a spreadsheet, webhook, API, or automation.

For a first run, use the default Miami market URL and a small result limit. Once the output matches your research needs, increase the record and page limits or schedule recurring runs.

Input Parameters

Parameter	Type	Required	Default	Description
startUrl	String	No	https://www.lennar.com/find-a-home?state=FL&market=MIA	Lennar Find-a-Home URL. The URL should contain a two-letter state code and Lennar market code.
results_wanted	Integer	No	20	Maximum number of unique homesite, plan, and community records to save.
max_pages	Integer	No	10	Maximum number of result pages to request for listings and communities.
proxyConfiguration	Object	No	Not set	Optional Apify Proxy configuration for the run.

The Actor also accepts url as an alternate single-URL input and recognizes startUrls when supplied as an array, using the first valid URL. startUrl is the recommended field for normal runs.

Output Data

The dataset contains one JSON object per saved record. Homesite and plan records include related community fields when Lennar provides them. Community records contain community-level information and may not include homesite-specific fields such as price, beds, or address.

Usage Examples

Basic Miami market run

Collect up to 20 records from Lennar's Miami, Florida market page:

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

Larger market snapshot

Collect a larger dataset while allowing the Actor to request up to 10 result pages:

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

Houston market with proxy configuration

Collect new-home records from the Houston, Texas market and enable Apify Proxy for the run:

{
  "startUrl": "https://www.lennar.com/find-a-home?state=TX&market=HOU",
  "results_wanted": 50,
  "max_pages": 10,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Sample Output

This is an example of a homesite record. Some optional values are omitted when the source does not publish them.

{
  "record_type": "homesite",
  "id": "h_751681",
  "homesite_id": "h_751681",
  "lot_id": "42",
  "status": "MOVE_IN_READY",
  "address": "17871 SW 359 TER",
  "price": 394340,
  "formatted_price": "$394,340",
  "beds": 3,
  "baths": 2.5,
  "sqft": 1338,
  "plan_id": "p_93821",
  "plan_name": "Breezeway",
  "plan_url": "https://www.lennar.com/new-homes/florida/miami/miami/del-mar/seaview-collection/breezeway",
  "plan_starting_price": 389340,
  "community_name": "Seaview Collection",
  "community_url": "https://www.lennar.com/new-homes/florida/miami/miami/del-mar/seaview-collection",
  "city_name": "Miami",
  "market_code": "MIA",
  "state_code": "FL",
  "image_url": "https://cdn.lennar.com/api/images/contentassets/example/exterior.jpg",
  "image_urls": [
    "https://cdn.lennar.com/api/images/contentassets/example/exterior.jpg",
    "https://cdn.lennar.com/api/images/contentassets/example/kitchen.jpg"
  ],
  "image_count": 2,
  "url": "https://www.lennar.com/new-homes/florida/miami/miami/del-mar/seaview-collection/breezeway/9396604001",
  "search_url": "https://www.lennar.com/find-a-home?state=FL&market=MIA",
  "collected_at": "2026-07-04T11:09:33.882Z"
}

Tips for Best Results

• Use a complete public Lennar Find-a-Home URL with both state and market parameters.
• Start with results_wanted: 20 to validate a market before requesting a larger dataset.
• Increase max_pages when the selected market contains more inventory than one page can return.
• Expect fewer records when a market has limited homesite, plan, or community inventory.
• Use record_type to separate available homes, floor plans, and communities in downstream analysis.
• Schedule repeat runs with the same market URL to compare price, status, plan, and inventory changes.
• Check the dataset preview because optional fields depend on the data Lennar publishes for each record.

Integrations and Export Formats

• Google Sheets - Review market snapshots and compare inventory changes over time.
• Airtable - Build searchable tables of homesites, plans, and communities.
• Make or Zapier - Route new records into reporting, CRM, or alerting workflows.
• Webhooks - Notify another service after a run finishes.
• Apify API - Read datasets programmatically from your own application.

Format	Best for
JSON	Data pipelines, APIs, and application development.
CSV	Spreadsheet analysis and bulk review.
Excel	Reporting and stakeholder sharing.
XML	Structured integrations and legacy systems.

Frequently Asked Questions

Which Lennar markets can I collect?

You can collect a market supported by a public Lennar Find-a-Home URL. Pass its state and market query values in startUrl.

Does the Actor return homes, plans, and communities?

Yes. The dataset can include homesite, plan, and community records, depending on the inventory returned for the selected market.

Why did I receive fewer records than requested?

The market may contain fewer unique records than the results_wanted value, or the max_pages limit may stop collection before the requested total is reached.

Are all fields present on every record?

No. Field availability depends on the record type and the information Lennar publishes. Optional empty values are removed from saved records.

Can I collect home images and virtual tours?

Yes. image_url, image_urls, and plan_virtual_tour_url are saved when those media links are available.

Can I run Lennar data collection on a schedule?

Yes. Create an Apify schedule to run the Actor hourly, daily, weekly, or at another interval and compare the resulting datasets.

Can I export Lennar data to CSV or Excel?

Yes. Apify datasets can be downloaded in CSV, Excel, JSON, XML, and other supported formats.

Is collecting public Lennar data legal?

You are responsible for complying with Lennar's terms, applicable laws, privacy requirements, and any limits on how collected data may be used. Collect only data you are permitted to access and use it responsibly.

Related Actors

• Propertyfinder Scraper 🏠 - Collect UAE property listings with prices, specifications, locations, agents, and media.
• Private Property Scraper 🏡 - Collect South African property listings for market research, investment analysis, and lead generation.
• iProperty Scraper - Collect Malaysian property listings, new projects, prices, locations, and agent details.

Support

For issues, missing fields, or feature requests, use the Issues tab on the Actor page and include the input URL, market, run ID, and an example of the unexpected output when possible.

Legal Notice

This Actor is intended for legitimate collection and analysis of publicly available Lennar data. Users are responsible for complying with Lennar's website terms, applicable laws, privacy rules, and any restrictions on storing, sharing, or using the collected information.