Brookfield Residential APIbrookfieldresidential.com ↗
Retrieve floor plans and quick move-in homes from Brookfield Residential community pages. Get price, beds, baths, sq ft, and address data via one endpoint.
What is the Brookfield Residential API?
The Brookfield Residential API exposes 1 endpoint — get_community_listings — that returns structured data for every floor plan and quick move-in (QMI) home on a given community page. Each response includes up to 13 fields per listing: plan name, square footage, bedroom and bathroom counts, garage count, home type, pricing, address components, and a direct listing URL. It covers any community accessible under the /new-homes/ path on brookfieldresidential.com.
curl -X GET 'https://api.parse.bot/scraper/1495441d-6b97-443b-b774-95fc07f73758/get_community_listings?community_path=%2Fnew-homes%2Fcalifornia%2Flos-angeles-county%2Farcadia%2Fmagnolia' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace brookfieldresidential-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Brookfield Residential SDK — fetch community listings."""
from parse_apis.Brookfield_Residential_Community_Listings_API import (
BrookfieldResidential,
Community,
CommunityNotFound,
)
client = BrookfieldResidential()
# Fetch all listings for the Magnolia community in Arcadia, CA.
community = client.communities.get(community_path="/new-homes/california/los-angeles-county/arcadia/magnolia")
print(f"Community: {community.community_name}")
print(f"Builder: {community.builder_name}")
print(f"Total QMI homes: {community.total_qmi_homes}")
print(f"Total floor plans: {community.total_floor_plans}")
# Inspect quick move-in homes
for home in community.qmi_homes[:3]:
print(f" QMI: {home.address} | Plan: {home.plan_name} | "
f"SqFt: {home.square_footage} | Beds: {home.bedrooms} | "
f"Baths: {home.bathrooms} | Price: ${home.qmi_price:,}")
# Inspect floor plans
for plan in community.floor_plans[:3]:
price_str = f"${plan.from_price:,}" if plan.from_price else "TBD"
print(f" Plan: {plan.plan_name} | SqFt: {plan.square_footage} | "
f"Beds: {plan.bedrooms} | Baths: {plan.bathrooms} | From: {price_str}")
# Typed error handling for an invalid community path
try:
client.communities.get(community_path="/new-homes/invalid/nonexistent/community/xyz")
except CommunityNotFound as exc:
print(f"Community not found: {exc.community_path}")
print("exercised: communities.get / QmiHome fields / FloorPlan fields / CommunityNotFound")
Retrieves all floor plans and quick move-in (QMI) homes for a given Brookfield Residential community page. Returns builder name, community name, plan name, square footage, bedrooms, bathrooms, QMI price, starting/from price, and listing URL for each home or plan. The community_path identifies the community by its URL path on brookfieldresidential.com.
| Param | Type | Description |
|---|---|---|
| community_pathrequired | string | URL path to the community page on brookfieldresidential.com, starting with /new-homes/ (e.g. /new-homes/california/los-angeles-county/arcadia/magnolia). |
{
"type": "object",
"fields": {
"qmi_homes": "array of QMI home objects with builder_name, community_name, plan_name, address, city, state, zip_code, square_footage, bedrooms, bathrooms, garages, home_type, qmi_price, move_in_date, lot_number, listing_url, listing_type",
"floor_plans": "array of floor plan objects with builder_name, community_name, plan_name, square_footage, bedrooms, bathrooms, garages, home_type, from_price, status, listing_url, listing_type",
"builder_name": "string",
"community_url": "string",
"community_name": "string",
"total_qmi_homes": "integer",
"total_floor_plans": "integer"
},
"sample": {
"data": {
"qmi_homes": [
{
"city": "Arcadia",
"state": "California",
"address": "123 Main St, Springfield, IL 62704",
"garages": 2,
"bedrooms": 2,
"zip_code": "91006",
"bathrooms": 3,
"home_type": "Townhome",
"plan_name": "Plan 1",
"qmi_price": 732286,
"lot_number": "184",
"listing_url": "https://www.brookfieldresidential.com/new-homes/california/los-angeles-county/arcadia/magnolia/townhomes/2884-lavender-place-unit-000184",
"builder_name": "Brookfield Residential",
"listing_type": "quick_move_in",
"move_in_date": "10/02/2026",
"community_name": "Magnolia",
"square_footage": 1276
}
],
"floor_plans": [
{
"status": "Active",
"garages": 2,
"bedrooms": 2,
"bathrooms": 3,
"home_type": "Townhome",
"plan_name": "Plan 1",
"from_price": 732286,
"listing_url": "https://www.brookfieldresidential.com/new-homes/california/los-angeles-county/arcadia/magnolia/townhomes/1",
"builder_name": "Brookfield Residential",
"listing_type": "floor_plan",
"community_name": "Magnolia",
"square_footage": 1276
}
],
"builder_name": "Brookfield Residential",
"community_url": "https://www.brookfieldresidential.com/new-homes/california/los-angeles-county/arcadia/magnolia",
"community_name": "Magnolia",
"total_qmi_homes": 15,
"total_floor_plans": 7
},
"status": "success"
}
}About the Brookfield Residential API
What the API Returns
The get_community_listings endpoint accepts a single required parameter, community_path, which is the URL path to a Brookfield Residential community page starting with /new-homes/ (for example, /new-homes/california/los-angeles-county/arcadia/magnolia). The response contains two top-level arrays — qmi_homes and floor_plans — along with summary fields: builder_name, community_name, community_url, total_qmi_homes, and total_floor_plans.
Floor Plans vs. QMI Homes
Objects in the floor_plans array include plan_name, square_footage, bedrooms, bathrooms, garages, home_type, and a from_price (the starting price for that plan). Objects in the qmi_homes array include all of those fields plus full address components — address, city, state, zip_code — and a qmi_price reflecting the specific asking price for that ready-to-purchase home. This distinction lets you separate spec-level plan data from homes that are immediately available.
Scope and Coverage
The API covers any public Brookfield Residential community page reachable via the /new-homes/ path. Each call is scoped to a single community, so querying multiple communities requires one call per community_path. The response does not include community-level amenities, lot maps, or sales office contact details — it is limited to the plan and QMI listing data surfaced on that page.
The Brookfield Residential API is a managed, monitored endpoint for brookfieldresidential.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when brookfieldresidential.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 brookfieldresidential.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?+
- Aggregate floor plan pricing across multiple Brookfield Residential communities for market comparison.
- Monitor QMI home inventory and price changes for a specific community over time.
- Filter available homes by bedroom count, square footage, or home type to match buyer criteria.
- Build a new-construction home search tool using plan names, prices, and listing URLs.
- Track how quickly QMI homes are added or removed from a community page.
- Compare
from_priceacross floor plans within a community to analyze pricing tiers. - Populate a CRM or lead-gen tool with ready-to-purchase QMI addresses and unit details.
| 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 Brookfield Residential have an official developer API?+
What distinguishes a QMI home from a floor plan in the response?+
from_price (the base starting price) but no specific address. QMI home objects represent homes already built or under construction that are available for immediate purchase; they carry a qmi_price — a specific list price — plus full address fields: address, city, state, and zip_code.Can I query multiple communities in a single API call?+
get_community_listings is scoped to one community_path. To retrieve data across multiple communities, you need one request per community. You can fork this API on Parse and revise it to add a batch endpoint that accepts multiple paths in a single call.Does the API return community amenities, lot maps, or sales contact information?+
How fresh is the listing data returned by `get_community_listings`?+
community_path will capture those updates.