Lennar.com Scraper
Pricing
Pay per usage
Lennar.com Scraper
Extract Lennar home listings, prices, and developer data for real estate intelligence. Automate property scraping with floor plans, community details, and pricing. Perfect for market research, competitive analysis, and real estate platforms.
Pricing
Pay per usage
Rating
5.0
(2)
Developer
Shahid Irfan
Maintained by CommunityActor stats
2
Bookmarked
9
Total users
3
Monthly active users
8 days ago
Last modified
Categories
Share
Lennar Homes Scraper
Extract Lennar new home listings with pricing, inventory, plan, community, location, and media data. This Lennar scraper is built for fast market monitoring, real estate research, and repeatable housing datasets across state and market pages.
Features
- Market-based collection - Use a Lennar Find-a-Home URL to target a state and market.
- Listing and plan coverage - Collect available homesites, plans, and community records when present.
- Rich media fields - Save a primary
image_urlplus availableimage_urlsfrom listing, plan, floorplan, room, and feature media. - Clean records - Empty strings and null values are removed before data is saved.
- Configurable limits - Control result count and pagination depth for quick tests or larger runs.
Use Cases
Real Estate Market Tracking
Monitor Lennar inventory by market, city, community, and plan. Use repeat runs to compare prices, availability, square footage, and listing status over time.
Investment Research
Build datasets for comparing price ranges, bedroom counts, monthly payment data, and community details. This helps analysts evaluate where new-home supply is concentrated.
Competitive Intelligence
Track new construction inventory and media assets across active Lennar communities. Compare homesite pricing, plan availability, and community-level positioning.
Lead Qualification
Feed structured home data into CRM, alerting, or reporting workflows. Use fields such as address, beds, baths, price, plan name, and community name to route opportunities.
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 with state and market query parameters. |
results_wanted | Integer | No | 20 | Maximum number of records to save. |
max_pages | Integer | No | 10 | Maximum pagination pages to request. |
proxyConfiguration | Object | No | {"useApifyProxy": true} | Proxy settings for production runs. |
Output Data
Each item in the dataset can contain:
| Field | Type | Description |
|---|---|---|
record_type | String | Record category: homesite, plan, or community. |
id | String | Primary record ID. |
homesite_id | String | Homesite ID when the record is a home listing. |
plan_id | String | Related plan ID. |
status | String | Homesite or plan status. |
price | Number | Current homesite price. |
formatted_price | String | Display price when available. |
beds | Number | Bedroom count. |
baths | Number | Bathroom count. |
half_baths | Number | Half bathroom count. |
sqft | Number | Square footage. |
address | String | Homesite or community address. |
image_url | String | Primary image URL. |
image_urls | Array | Available media URLs from listing and plan data. |
image_count | Number | Count of URLs in image_urls. |
plan_virtual_tour_url | String | Plan virtual tour URL when available. |
community_name | String | Community name. |
community_url | String | Community page URL. |
city_name | String | City name. |
market_code | String | Lennar market code. |
state_code | String | State code. |
url | String | Detail page URL. |
collected_at | String | Collection timestamp. |
Additional pricing, payment, page view, MPC, and community 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}
Larger Market Snapshot
{"startUrl": "https://www.lennar.com/find-a-home?state=FL&market=MIA","results_wanted": 100,"max_pages": 10}
Different State and Market
{"startUrl": "https://www.lennar.com/find-a-home?state=TX&market=HOU","results_wanted": 50,"max_pages": 10}
Sample Output
{"record_type": "homesite","id": "h_751681","homesite_id": "h_751681","status": "MOVE_IN_READY","price": 394340,"beds": 3,"baths": 2.5,"sqft": 1338,"address": "17871 SW 359 TER","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,"plan_name": "Breezeway","community_name": "Seaview Collection","city_name": "Miami","market_code": "MIA","state_code": "FL","url": "https://www.lennar.com/new-homes/florida/miami/miami/del-mar/seaview-collection/breezeway/9396604001","collected_at": "2026-07-04T11:09:33.882Z"}
Tips for Best Results
Start With QA-Friendly Limits
- Use
results_wanted: 20for quick validation. - Increase the limit after confirming the market URL works.
Use Valid Market URLs
- Make sure
startUrlincludesstateandmarket. - Copy URLs from Lennar Find-a-Home pages for best matching.
Tune Pagination
- Increase
max_pageswhen requesting larger datasets. - If fewer records are saved than requested, the selected market may have fewer unique records available.
Integrations
Connect your data with:
- Google Sheets - Review listing snapshots with your team.
- Airtable - Build searchable housing inventory tables.
- Make - Trigger workflows from completed runs.
- Zapier - Send new records to business tools.
- Webhooks - Deliver data to custom systems.
Export Formats
- JSON - For structured data pipelines.
- CSV - For spreadsheet analysis.
- Excel - For reporting.
- XML - For legacy tools.
Frequently Asked Questions
Can I collect all available listings in a market?
Yes. Set results_wanted and max_pages high enough to cover the selected market.
Why did I receive fewer records than requested?
The selected market may have fewer unique homesite, plan, and community records available than your requested limit.
Are empty values included?
No. Empty strings and null values are removed so the dataset stays clean.
Can I collect media URLs?
Yes. Records include a primary image_url and image_urls when media is available.
Can I run this on a schedule?
Yes. Scheduled runs are useful for tracking price and inventory changes.
Support
For issues or feature requests, contact support through the Apify Console.
Resources
Legal Notice
This actor is designed for legitimate data collection and analysis. You are responsible for complying with website terms, local laws, and all applicable regulations.