Lennar Scraper: 40 Data Fields, Up to 1,000 Free Results/Month (2026)

Lennar Scraper extracts detailed new-home listings across 95+ US markets, providing crucial data points such as homesite ID, address, city, state code, zip code, current and original prices, bedroom and bathroom counts, square footage, availability status, and specific offer details. Each record carries 40 output fields, including plan names, community information, and GPS coordinates. You can try it before committing; Apify's free plan includes up to 1,000 results of this Actor. This Actor is for real estate analysts, market researchers, and competitive intelligence professionals tracking new construction. It is not for anyone needing historical sales data or detailed mortgage estimates, which are not included in the public-facing records.

Try it: open Lennar Scraper on Apify, sign in on the free plan and run the prefilled example.

Can you try Lennar Scraper before paying?

Yes. Apify's free plan includes $5.00 of prepaid usage every month and asks for no credit card. At $0.005 per result, that covers up to 1,000 results of Lennar Scraper a month, before run-start charges and platform usage.

The example request further down caps maxItems at 50, so a first run returns at most 50 results and costs at most $0.25 in result charges. That is enough to see the real shape of the data before deciding anything.

Lennar Scraper was last updated on 2026-07-21. It is one of 1,725 Actors CrawlerBros publishes on Apify, which together have 692,561 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

What does it cost to run Lennar Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

The primary driver of cost for this Actor is the number of results it writes to your dataset, charged at $0.005 per result. This means the "maxItems" input control has the largest effect on your bill, as it directly limits the number of homes returned. To find out if this Actor meets your needs before a significant spend, start with the example input, which caps "maxItems" at 50 results and costs at most $0.25 in result charges.

How do you run Lennar Scraper from the API?

None of its 15 controls is strictly required, so the defaults below produce a valid run on their own. Every value in the payload below comes from the published schema's own prefills, which means you can paste it, swap the token, and get a real result.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~lennar-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"byMarket","marketCodes":["AUS"],"communityUrls":["https://www.lennar.com/new-homes/texas/austin-central-texas/hutto/cotton-brook"],"maxItems":50,"statuses":[],"isHotwOnly":false,"offerAvailableOnly":false}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "byMarket",
  "marketCodes": [
    "AUS"
  ],
  "communityUrls": [
    "https://www.lennar.com/new-homes/texas/austin-central-texas/hutto/cotton-brook"
  ],
  "maxItems": 50,
  "statuses": [],
  "isHotwOnly": False,
  "offerAvailableOnly": False
}

run = client.actor("crawlerbros~lennar-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "byMarket",
  "marketCodes": [
    "AUS"
  ],
  "communityUrls": [
    "https://www.lennar.com/new-homes/texas/austin-central-texas/hutto/cotton-brook"
  ],
  "maxItems": 50,
  "statuses": [],
  "isHotwOnly": false,
  "offerAvailableOnly": false
}

const run = await client.actor('crawlerbros~lennar-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

That endpoint blocks until the run completes. Fine while you are testing a handful of records, risky once a run takes minutes: a dropped connection loses the response even though the run itself finished. Switch to an asynchronous start with polling or a webhook before you schedule anything.

Which Lennar Scraper inputs matter, and which can you skip?

This Actor offers 15 input controls, none of which are required, providing flexibility in how you define your scrape. The "mode" control is key, allowing you to choose between scraping by specific "marketCodes", by "communityUrls", or across "allMarkets". For your first run, most users should focus on selecting their desired mode and market/community inputs, leaving other filters like "minPrice" or "isHotwOnly" at their defaults until you understand the basic output.

• mode (string): Choose how to find homes: by market code(s), by direct community URL(s), or scrape all markets. Default: "byMarket".
• marketCodes (array): One or more Lennar market codes to scrape (used when mode=byMarket). Each code maps to a metro area. Default: ["AUS"].
• communityUrls (array): Full Lennar community/MPC page URLs to scrape (used when mode=byCommunityUrl). E.g. https://www.lennar.com/new-homes/texas/austin-central-texas/hutto/cotton-brook
• maxItems (integer): Maximum number of home records to return. Default: 50.
• statuses (array): Only return homes with these statuses. Leave empty to include all statuses. Default: [].
• isHotwOnly (boolean): Only return homes flagged as 'Hot of the Week' by Lennar. Default: false.
• offerAvailableOnly (boolean): Only return homes that currently have an active offer/incentive. Default: false.
• minPrice (integer): Minimum asking price in dollars.
• maxPrice (integer): Maximum asking price in dollars.
• minBeds (integer): Minimum number of bedrooms.
• maxBeds (integer): Maximum number of bedrooms.
• minBaths (integer): Minimum number of bathrooms (full baths only).

The other 3 controls, with their defaults, are listed in the input schema on Lennar Scraper on Apify.

Fixed-choice controls: mode accepts byMarket (scrape one or more Lennar markets (e.g. AUS, CHI, MIA)), byCommunityUrl (scrape specific community pages), allMarkets (scrape every Lennar market (~95 markets)).

What does Lennar Scraper return?

The returned records are ideal for market analysis and competitive tracking, providing granular details on new-home inventory, pricing, and availability. Crucially, the output conspicuously does not contain floor-plan-only listings without assigned lots, historical sold data, or features requiring a Lennar account such as personal offer details or saved favorites.

• homesiteId: Lennar's internal homesite identifier
• lotId / lotNumber: Lot identifier and lot/unit number
• address: Street address of the home
• city / stateCode / zipCode: Location
• marketCode / marketName: Lennar market (e.g. AUS → Austin / Central Texas)
• price: Current asking price (USD)
• wasPrice: Original price (when reduced)
• beds / baths / halfBaths: Bedroom and bathroom counts
• sqft: Living area in square feet
• status: Availability: MOVE_IN_READY, UNDER_CONSTRUCTION, AVAILABLE, etc.
• isHotw: True if marked as Lennar's "Hot of the Week"
• offerAvailable: True if an active incentive/offer is available
• offerEndDate: Expiration date of the active incentive/offer (when available)
• url: Direct link to the homesite on Lennar.com
• elevationImageUrl: Exterior image of this specific homesite
• planName / planId / planUrl: Floor plan details
• planStartingPrice: Starting price for this floor plan
• planHeroImageUrl: Interior/hero image for the floor plan
• communityNumber / communityAddress / communityZipCode: Sub-community info
• communityTypes: Property types (e.g. Single Family, Townhome)
• mpcName / mpcId / mpcUrl: Master Planned Community details
• mpcLatitude / mpcLongitude: GPS coordinates of the community
• mpcBedRange / mpcBathRange / mpcSqftRange: Community-wide ranges
• mpcPriceRange: Community price range (e.g. $279,999 - $472,999)
• scrapedAt: ISO 8601 UTC timestamp

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Lennar Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Set the "mode" to "byMarket" and add one or more "marketCodes" to begin, then run the Actor.
2. Review the first few results in the Dataset tab to ensure records are being returned as expected and that the "price" and "status" fields are populated.
3. If initial results look good, adjust the "maxItems" to your desired record count. For market research, set it higher than the default 50.
4. Consider adding filters like "minPrice", "maxPrice", or "statuses" (e.g., "MOVE_IN_READY") to narrow down results.
5. Schedule the Actor to run periodically, checking the output records for changes in "price" or "status" over time.
6. Use the "offerAvailableOnly" filter if you are specifically looking for homes with active incentives, then verify the "offerAvailable" field is true in the output.
7. Review the "wasPrice" field alongside "price" to identify any recent price reductions for homes.

How do you apply it? Three worked playbooks

These are Lennar Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Real estate market research

Outcome: Track Lennar inventory and pricing trends across US markets

Configure: Set "mode" to "allMarkets" for comprehensive coverage. Leave filter fields like "statuses" and "minPrice" empty to get all available data without restrictions.

Working method: Begin with a smaller "maxItems" value, such as 500, to understand the data structure and content. Once you're comfortable, remove the "maxItems" limit (or set it high) to capture all available inventory. Run this Actor on a schedule, perhaps weekly, and compare the price and status fields over time to identify trends in availability and pricing.

Deliverable: A time-series dataset of Lennar new-home listings, including changes in pricing and availability, suitable for trend analysis.

Stop condition: The count of new listings in a market drops significantly without an external reason, indicating a potential issue with the scraper's coverage.

Use case 2: Competitive intelligence

Outcome: Compare pricing, floor plans, and availability across communities

Configure: Set "mode" to "byCommunityUrl" and provide a list of "communityUrls" for the specific communities you wish to compare. Set "maxItems" to a value that ensures all homes within those communities are captured, or remove the cap entirely.

Working method: Start by scraping a single community to verify the output fields are complete for your comparison needs. Then, expand your input to include all communities of interest. Focus on fields like "price", "planName", "beds", "baths", and "sqft" for direct comparisons.

Deliverable: A spreadsheet or database containing detailed home and floor plan data for multiple specified Lennar communities, enabling direct comparison.

Stop condition: Records for a specific community consistently return zero homes, even when manually checking Lennar.com shows available listings.

Use case 3: Lead generation

Outcome: Find move-in-ready homes with active offers for real estate agents

Configure: Set "mode" to "byMarket" and provide relevant "marketCodes". Set "statuses" to ["MOVE_IN_READY"] and "offerAvailableOnly" to true.

Working method: Run the Actor for a target market and review the output, paying close attention to homes where "offerAvailable" is true. Use the "offerEndDate" to prioritize leads and contact agents. Refine your market codes based on agent demand.

Deliverable: A filtered list of Lennar homes that are move-in-ready and have active offers, suitable for direct use by real estate agents as sales leads.

Stop condition: The "offerAvailable" field is false for all records, even when Lennar.com explicitly shows offers on some move-in-ready homes.

What breaks, and how do you design around it?

• Floor-plan-only listings: Some Lennar communities sell at the floor-plan level without assigned lots. These are not included (they have no specific homesite address/price).
• Auth-required features: Mortgage estimates, personal offer details, and favorite lists require a Lennar account and are not scraped.
• Historical sold data: Only current active/under-construction/move-in-ready homesites are available via the public API.

When dealing with communities that offer only floor plans and no specific homesites, you'll find these listings are not included in the output. If you need to monitor these, consider supplementing with manual checks on Lennar.com or exploring alternative data sources that track architectural plans. For features requiring a Lennar account, such as personal offer details, the only solution is to use a different data collection method, as the Actor cannot access authenticated content. Historical sold data is not available through this Actor, so if you require past sales figures, an official Lennar API or a third-party real estate data provider would be necessary.

When should you not use Lennar Scraper?

This Actor is not suitable if your primary need is to track mortgage estimates, detailed personal offer specifics, or create lists of favorited homes, as these features require a Lennar account and are not scraped. Similarly, if you require historical sold data for market trend analysis, this Actor will fall short, as it only returns current active, under-construction, or move-in-ready homesites. Instead, you might consider using an official Lennar API if available, or a broader real estate data provider that specializes in historical transactions. For general real estate listings that include resale homes, the Compass Real Estate Scraper could be a more appropriate tool. If your project involves a wider scope of new-construction builders beyond Lennar, you might explore Actors like the Pulte Homes Scraper or the Toll Brothers Scraper for broader coverage of other major homebuilders.

What should you check before trusting the output?

• Watch for records where essential fields like "price", "sqft", or "status" are null or missing, which can indicate an issue with the source data for that specific homesite.
• Check for malformed URLs in the "url" field or missing image links in "elevationImageUrl" and "planHeroImageUrl", as these are critical for further research.
• If filtering by "statuses", ensure that all returned records strictly adhere to the selected statuses (e.g., if only "MOVE_IN_READY" is selected, no "UNDER_CONSTRUCTION" homes should appear).
• Monitor for a significant drop in the number of results compared to previous runs when scraping the same market or communities, as this could signal a change on Lennar.com or a broken selector.
• Verify that price ranges like "minPrice" and "maxPrice" are being respected in the output; if a record falls outside the specified range, it suggests a problem with the input or data extraction.
• Confirm that the "scrapedAt" timestamp is recent for all records, indicating that the data is fresh and not stale from a previous run.

None of this proves a record is correct. It gives a scheduled Lennar Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

How many Lennar new-home listings can this Actor scrape?

Lennar has thousands of available homesites nationwide. A single run in "allMarkets" mode can return anywhere from 5,000 to over 15,000 records, depending on Lennar's current inventory. The "maxItems" input control allows you to set an upper limit on the number of home records returned by any given run, up to 10,000 items per run.

What does it cost to scrape Lennar homes with this Actor?

On Apify's free plan, each result from this Actor costs $0.005, which amounts to $5.00 per 1,000 results. Apify's free plan includes $5.00 of monthly usage without requiring a credit card, covering up to 1,000 results before factoring in platform usage and run-start fees. A run-start fee is charged every time a run begins, regardless of whether it returns results, while per-result charges apply only to items written to the dataset. For example, a first run with the default example input caps results at 50, costing at most $0.25 in result charges.

Does this Actor require me to use proxies or authentication?

No, this Actor does not require any credentials, API keys, or specific proxy configurations. It operates by interacting with Lennar's public Next.js server-side rendering data endpoint, which is openly accessible. This simplifies its use significantly, allowing you to run it directly without additional setup for authentication or proxy rotation.

How often is the data updated when I run this Actor?

The Actor fetches live data directly from Lennar.com during each run. Lennar continuously updates their listings throughout the day, ensuring that the data you receive is as current as possible at the time of your scrape. You can schedule the Actor to run at your desired frequency to keep your dataset fresh and up-to-date with the latest changes.

Can I use this Actor to find only homes with active offers?

Yes, you can filter the results to include only homes that currently have an active offer or incentive. To do this, set the "offerAvailableOnly" input control to true. This will refine your dataset to show only homes that Lennar has flagged with an active offer, which is particularly useful for lead generation or identifying special deals.

Where to go next

When you are ready to run it, open Lennar Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the Lennar Scraper Actor page for the current input schema, pricing tier, and run history.

Other Actors we maintain for related data:

• Pulte Homes Scraper: Scrape new-construction home communities, floor plans, and quick-move-in homes from Pulte Homes and sister PulteGroup brands (Centex, Del Webb, DiVosta) across 26 US states.
• Toll Brothers Scraper: Scrape luxury new-construction home communities, floor plans, and quick-move-in homes from Toll Brothers across 78 US states and metro areas.
• Coverfox Scraper - Indian Insurance Comparison Plans: Scrape Coverfox.com for Indian insurance plans across car, health, term life, and two-wheeler categories.
• Compass Real Estate Scraper: Scrape Compass.com real estate listings - homes for sale and for rent across US markets.
• MHVillage Manufactured & Mobile Home Scraper: Scrape MHVillage.com - the largest US manufactured/mobile home marketplace.
• Jiwu Scraper (Chinese resale homes, 吉屋二手房): Scrape jiwu.com - Chinese resale-home listings portal.
• FreeCampsites Scraper: Scrape FreeCampsites.net's community-sourced directory of free and low-cost dispersed camping, boondocking, and budget campground listings across all 50 US states - names, descriptions, amenities, pricing, and campsite counts.

Related guides:

• Coverfox Scraper: Extract 1,000 Insurance Plans for $5.00 (2026)

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-28.

• Actor last updated by its maintainers on 2026-07-21.

• Run outcome figures cover the 30 day public window ending 2026-09-28.

• Lennar Scraper on Apify