Lennar APIlennar.com ↗
Retrieve Lennar community floor plans and quick move-in homes via API. Get plan details, pricing, beds, baths, sqft, homesite numbers, and listing URLs.
What is the Lennar API?
The Lennar.com API exposes 1 endpoint — get_community_plans — that returns both floor plan data and available quick move-in (QMI) homesites for any Lennar community or master-planned community (MPC). A single call returns up to 15+ response fields per plan or homesite, including plan name, plan number, square footage, bedroom and bathroom counts, starting price, homesite number, and a direct listing URL.
curl -X GET 'https://api.parse.bot/scraper/6e9ed9ce-b1c1-4122-864b-81e18e87512c/get_community_plans?community_url_path=california%2Forange-county%2Firvine%2Fgreat-park-neighborhoods' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve all floor plans and available quick move-in (QMI) homes for a Lennar community or master-planned community (MPC). Returns plan-level data (name, number, sqft, beds, baths, starting price) and individual available homesites with QMI pricing. Sold homes are excluded from the available_homes list. The endpoint fetches the community page and extracts structured data from the server-side rendered Apollo cache.
| Param | Type | Description |
|---|---|---|
| community_url_pathrequired | string | URL path segment identifying the community, e.g. 'california/orange-county/irvine/great-park-neighborhoods' or 'california/orange-county/irvine/great-park-neighborhoods/isla-at-luna-park'. The 'new-homes/' prefix is optional and stripped automatically. |
{
"type": "object",
"fields": {
"plans": "array of plan objects with builder, community_name, plan_name, plan_number, sqft, bedrooms, bathrooms, half_baths, starting_price, custom_price, status, listing_url",
"mpc_name": "string - master-planned community name",
"total_plans": "integer - count of floor plans",
"available_homes": "array of QMI home objects with builder, community_name, plan_name, plan_number, homesite_number, sqft, bedrooms, bathrooms, half_baths, qmi_price, address, status, listing_url",
"total_available_homes": "integer - count of non-sold homesites"
},
"sample": {
"plans": [
{
"sqft": 2013,
"status": "ACTIVE",
"builder": "Lennar",
"bedrooms": 3,
"bathrooms": 3,
"plan_name": "Isla 1A",
"half_baths": 1,
"listing_url": "https://www.lennar.com/new-homes/california/orange-county/irvine/great-park-neighborhoods/isla-at-luna-park/isla-1a",
"plan_number": "001A",
"custom_price": "Low $1.2 Millions",
"community_name": "Isla at Luna Park",
"starting_price": 1224990
}
],
"mpc_name": "Great Park Neighborhoods",
"total_plans": 15,
"available_homes": [
{
"sqft": 2013,
"status": "UNDEFINED",
"address": "820 Sonia",
"builder": "Lennar",
"bedrooms": 3,
"bathrooms": 3,
"plan_name": "Isla 1A",
"qmi_price": 1224990,
"half_baths": 1,
"listing_url": "",
"plan_number": "001A",
"community_name": "Isla at Luna Park",
"homesite_number": "0060"
}
],
"total_available_homes": 179
}
}About the Lennar API
What the API Returns
The get_community_plans endpoint accepts a community_url_path parameter — the geographic path segment from a Lennar community URL, such as california/orange-county/irvine/great-park-neighborhoods — and returns two parallel datasets: a plans array of floor plan objects and an available_homes array of QMI homesites. Summary integers total_plans and total_available_homes are included at the top level, along with mpc_name for master-planned communities.
Floor Plan Fields
Each object in the plans array includes builder, community_name, plan_name, plan_number, sqft, bedrooms, bathrooms, half_baths, and starting_price. These fields reflect the floor plan configuration as listed on the community page, giving you a structured view of what's being offered before drilling into specific homesites.
QMI Homesite Fields
Objects in the available_homes array mirror the plan-level fields and add homesite-specific data: homesite_number, QMI-specific pricing (which may differ from the plan's starting_price), and a direct listing URL. Sold homesites are excluded — only homes currently available for purchase appear. This makes the array suitable for availability monitoring or inventory snapshots without filtering on your end.
The Lennar API is a managed, monitored endpoint for lennar.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when lennar.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official lennar.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor price changes on specific Lennar floor plans across a target community by polling
starting_priceand QMI pricing fields. - Build a homesite availability tracker that alerts buyers when new QMI homes appear in a given community.
- Compare bedroom-to-price ratios across floor plans within a master-planned community using
bedrooms,sqft, andstarting_price. - Aggregate Lennar inventory across multiple communities by calling
get_community_planswith differentcommunity_url_pathvalues. - Populate a real estate research dashboard with structured new-construction data including plan numbers, sqft, and direct listing URLs.
- Feed new-construction inventory into a buyer-facing search tool that filters by beds, baths, and price for Lennar communities.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Lennar have an official public developer API?+
What distinguishes `plans` from `available_homes` in the response?+
plans represents floor plan configurations — the abstract designs a builder offers — each with a plan_number, sqft, bedroom/bathroom counts, and a starting_price. available_homes represents specific homesites currently for sale that are tied to those plans; each includes a homesite_number and a QMI price that reflects the actual lot, which can differ from the plan's starting price. Sold homesites are excluded from available_homes.Does the API cover all Lennar communities across the US?+
community_url_path, so you can target communities in different states by changing that parameter. Coverage depends on the community having an active Lennar listing page. Communities that have been closed or fully sold out may return empty or limited results.Does the API return community amenity details, lot dimensions, or HOA fees?+
Can I retrieve historical price data or track price changes over time?+
starting_price and QMI pricing reflect the live state of the community page at request time. You can fork this API on Parse and revise it to store and diff results across scheduled calls to build your own price history.