lennar-marketplace.locatealpha.com APIlennar-marketplace.locatealpha.com ↗
Access Lennar Investor Marketplace listings, property financials, demographics, rental comps, and PM fee data via 7 structured endpoints.
curl -X GET 'https://api.parse.bot/scraper/c852d5b7-6ed2-484b-a8f3-fbca9eb9b7e6/get_listings?limit=3&offset=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch property listings from the Lennar Investor Marketplace. Supports pagination via limit and offset parameters. Each listing includes property details, financials, and metadata.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of listings to return. Capped at 400 per request due to response size constraints. |
| offset | integer | Number of listings to skip for pagination. |
{
"type": "object",
"fields": {
"data": "array of property listing objects with keys: property_id, city, full_address, postal_code, state, decisions, meta, misc",
"status": "string, always 'success'"
},
"sample": {
"data": [
{
"city": "Oxford",
"meta": {
"community": "Carterton Heights",
"plan_name": "RC Carlie II"
},
"misc": {
"cap_rate": 0.057,
"projected_monthly_rent": 1133.49
},
"state": "AL",
"decisions": [
{
"id": 100298,
"decision": "flash approve"
}
],
"postal_code": "36260",
"property_id": 599826,
"full_address": "193 Skyline Loop"
}
],
"status": "success"
}
}About the lennar-marketplace.locatealpha.com API
The Lennar Investor Marketplace API exposes 7 endpoints covering active single-family investment property listings, per-property underwriting data, area demographics, rental comparables, and property management fee benchmarks. Starting with get_listings or search_listings, you can retrieve paginated inventory and then drill into individual properties using get_property_details, get_property_demographics, get_property_comps, and get_property_resources — all keyed by a numeric property_id.
Listings and Search
get_listings returns paginated arrays of active investment property listings, each containing property_id, full_address, city, state, postal_code, decisions, meta, and misc fields. Pagination is controlled via limit (capped at 400 per request) and offset. search_listings accepts a query string matched against city name or state abbreviation — passing 'FL' or 'Florida' or a specific city name like 'Trappe' filters the full inventory to matching records and returns the same object shape. get_markets returns a deduplicated list of all states and cities currently represented in active listings, useful for building filter UIs or enumerating available markets.
Property-Level Detail
get_property_details takes a property_id and returns a single property object with financials, photos, descriptions, and underwriting fields nested under decisions, meta, and misc. The property_id must correspond to a currently active listing — IDs from delisted properties will not resolve. get_property_demographics returns one demographic record per property, including crime_score, medianhhincome, fiveyearpopgrowth, school, fld_zone, and bachelorsanda — area-level signals commonly used in rental investment underwriting.
Comparables and Management Fees
get_property_comps returns a rental comparable summary keyed to the property's location: total_parcels, owner_count, and institution_count. This gives a quick read on the ownership mix and institutional activity in the immediate area. Note that some locations may experience upstream timeouts on this endpoint. get_property_resources returns property management fee data for the property's market from multiple PM providers — hr_pm_fee, mph_pm_fee, and evernest_pm_fee — along with associated leasing and renewal fee fields, enabling side-by-side comparison of management cost assumptions across providers.
- Screen Lennar investment properties by market using
search_listingswith state or city queries before deeper analysis - Pull
medianhhincome,fiveyearpopgrowth, andcrime_scorefromget_property_demographicsto rank neighborhoods for buy-to-rent underwriting - Compare institutional vs. individual ownership ratios via
institution_countandowner_countfromget_property_compsto assess rental market saturation - Build cash-flow models using property financials from
get_property_detailscombined with PM fee benchmarks fromget_property_resources - Enumerate all available markets with
get_marketsto populate filter dropdowns in an investment deal-flow tool - Automate portfolio monitoring by paginating
get_listingson a schedule and diffingproperty_idsets to detect new or removed inventory - Compare
hr_pm_fee,mph_pm_fee, andevernest_pm_feeacross markets to estimate net operating income sensitivity to management costs
| 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 | 250 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 developer API for its Investor Marketplace?+
What does `get_property_demographics` return and how granular is it?+
get_property_demographics returns one record per property with six area-level fields: crime_score, medianhhincome, fiveyearpopgrowth, school, fld_zone, and bachelorsanda. These are location-level aggregates tied to the property's address, not individual parcel-level measurements. They reflect the characteristics of the surrounding area rather than the property itself.Does `get_property_comps` return individual comparable sale or rental transaction records?+
get_property_comps returns a summary with three aggregate fields (total_parcels, owner_count, institution_count) representing the ownership mix near the listing, not a list of individual comp transactions with price or rent data. You can fork the API on Parse and revise it to add an endpoint targeting individual comparable transactions if that data is available from the source.Can I retrieve historical listings or properties that are no longer active?+
get_property_details, get_property_demographics, get_property_comps, and get_property_resources all require a property_id from a live listing — IDs for delisted properties will not return data. You can fork the API on Parse and revise it to add a historical snapshot endpoint if you need to track removed listings over time.What is the pagination behavior for `get_listings`, and are there any size limits?+
get_listings supports limit and offset parameters for standard offset-based pagination. The limit parameter is capped at 400 per request due to response size constraints. To retrieve more than 400 listings, increment offset by your limit value across successive requests.