Brandywine Homes APIbrandywine-homes.com ↗
Access Brandywine Homes community listings and floor plan data via API. Get pricing, homesite availability, bedroom counts, and move-in dates for Southern California developments.
What is the Brandywine Homes API?
The Brandywine Homes API provides 2 endpoints covering Southern California new-home communities and their floor plan inventory. list_communities returns summary data for all communities — active and sold-out — including price ranges, bedroom counts, and square footage. get_community_plans drills into a specific community to return per-homesite QMI pricing, availability status, move-in dates, and floor plan specs.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/e4edc439-5958-446f-a5a2-83aa5833a613/list_communities' \ -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 brandywine-homes-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: Brandywine Homes SDK — browse communities and their floor plans."""
from parse_apis.Brandywine_Homes_API import BrandywineHomes, CommunityNotFound
client = BrandywineHomes()
# List all communities and print their basic info.
for community in client.communities.list(limit=5):
print(community.title, community.city, community.price_from)
# Drill into a specific community's plans via sub-resource navigation.
alisal = client.community(slug="alisal")
for plan in alisal.plans.list(limit=5):
print(plan.plan_name, plan.square_footage, plan.qmi_price, plan.status)
# Typed error handling: catch a not-found community.
try:
bad = client.community(slug="nonexistent-community")
for p in bad.plans.list(limit=1):
print(p.plan_name)
except CommunityNotFound as exc:
print(f"Community not found: {exc.community_slug}")
print("exercised: communities.list / community.plans.list / CommunityNotFound")
List all Brandywine Homes communities with summary information including name, location, pricing, bedroom counts, and square footage ranges. Returns both active (Now Selling) and sold-out communities.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer",
"communities": "array of community summaries with title, status, price_from, city, state, zip, community_type, bedrooms, sqft_range, url, slug, latitude, longitude"
},
"sample": {
"total": 5,
"communities": [
{
"url": "https://www.brandywine-homes.com/communities/alisal/",
"zip": "91740",
"city": "Glendora",
"slug": "alisal",
"state": "CA",
"title": "Alisal",
"status": "Now Selling!",
"bedrooms": "1-3",
"latitude": 34.130303,
"longitude": -117.854431,
"price_from": "Priced from $699,990",
"sqft_range": "743 - 1,939",
"community_type": "39 New Townhomes"
}
]
}
}About the Brandywine Homes API
Community Listings
The list_communities endpoint returns a full inventory of Brandywine Homes developments with no required parameters. Each community record includes title, status (e.g. Now Selling or sold-out), price_from, city, state, zip, community_type, bedrooms, sqft_range, url, and slug. The slug field is what you pass to the second endpoint to retrieve plan-level detail.
Floor Plans and Homesite Availability
The get_community_plans endpoint accepts a community_slug string — for example solara, alisal, or the-gables — and returns a plans array alongside community-level fields: from_price, builder_name, and community_name. Each record in plans includes plan_name, homesite, square_footage, bedrooms, bathrooms, and qmi_price (quick move-in pricing where applicable), plus move-in date and homesite status. This makes it straightforward to distinguish between configured homesites ready for purchase and base floor plans still in planning.
Coverage Notes
Data covers Brandywine Homes' Southern California portfolio only. Both active communities and those flagged as sold-out appear in list_communities, so you can track when inventory transitions. The total field at the response root gives a count of returned records in both endpoints, useful for pagination logic or change-detection workflows.
The Brandywine Homes API is a managed, monitored endpoint for brandywine-homes.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when brandywine-homes.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 brandywine-homes.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 new Brandywine Homes communities as they become active using the
statusfield fromlist_communities. - Build a price-tracking tool that alerts when
from_pricechanges across communities. - Filter available homesites by
bedroomsandsqft_rangeto match buyer requirements. - Display QMI (quick move-in) listings with
qmi_priceand move-in dates for buyers with near-term timelines. - Aggregate floor plan specs —
square_footage,bedrooms,bathrooms— across all communities for comparison tools. - Track sold-out community history to analyze supply trends in Brandywine's Southern California footprint.
- Integrate homesite availability status into a real estate CRM to flag newly released lots.
| 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 Brandywine Homes offer an official developer API?+
What does `get_community_plans` return beyond basic floor plan specs?+
plan_name, square_footage, bedrooms, and bathrooms, each record includes homesite identifiers, qmi_price for quick move-in units, move-in dates, and homesite status. The response also carries community-level fields — from_price, builder_name, and community_name — at the root.Does the API cover communities outside Southern California?+
list_communities are in that region. The state field on each record will consistently reflect California.Can I retrieve historical pricing or sales data for sold-out communities?+
price_from field visible on the Brandywine Homes site, but it does not expose a historical pricing timeline or transaction records. You can fork this API on Parse and revise it to store and diff responses over time to build your own historical dataset.Does the API expose community amenities, site maps, or photos?+
url field in list_communities points to each community's detail page. You can fork the API on Parse and revise it to add an endpoint that returns amenity descriptions or media assets.