rchomesinc.com APIrchomesinc.com ↗
Access RC Homes California communities, floor plan specs, and quick move-in home listings including pricing, homesite numbers, and square footage via 2 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/f9e19ff8-c4fd-4af4-acc5-312d29621472/list_communities' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed Python client. Install the CLI, sign in, then pull this API’s generated client:
pip install parse-sdk parse login parse add --marketplace rchomesinc-com-api
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: RC Homes API — list communities, browse floor plans and QMI homes."""
from parse_apis.RC_Homes_API import RCHomes, CommunityNotFound
client = RCHomes()
# List all communities — limit caps total items fetched.
for community in client.communities.list(limit=5):
print(community.title, community.slug)
# Drill into a specific community's plans and QMI homes.
heights = client.community(slug="the-heights-ponte-vista")
detail = heights.plans()
# Browse floor plans for this community.
for plan in detail.floor_plans:
print(plan.plan_name, plan.square_footage, plan.bedrooms, plan.bathrooms)
# Browse QMI homes with pricing.
for home in detail.qmi_homes:
print(home.plan_name, home.qmi_price, home.bedrooms, home.bathrooms, home.listing_url)
# Typed error handling: catch a missing community.
try:
bad = client.community(slug="nonexistent-community").plans()
except CommunityNotFound as exc:
print(f"Community not found: {exc.community_slug}")
print("exercised: communities.list / community.plans / CommunityNotFound")
List all RC Homes communities with basic metadata including slug, title, and URL. Use the slug from this response as input to get_community_plans for detailed floor plan and QMI home data.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of communities",
"communities": "array of community summaries (id, slug, title, url, modified)"
},
"sample": {
"data": {
"total": 13,
"communities": [
{
"id": 26817,
"url": "https://rchomesinc.com/community/the-heights-ponte-vista/",
"slug": "the-heights-ponte-vista",
"title": "The Heights at Ponte Vista",
"modified": "2026-06-10T22:24:14"
}
]
},
"status": "success"
}
}About the rchomesinc.com API
The RC Homes API provides structured access to RC Homes' California new-construction communities and their associated floor plans and quick move-in (QMI) homes across 2 endpoints. The list_communities endpoint returns every active community with its slug, title, and URL, while get_community_plans exposes 15+ fields per community including floor plan specifications, QMI pricing, homesite numbers, bedroom and bathroom counts, and move-in dates.
Community Discovery
The list_communities endpoint returns a complete index of RC Homes communities in California. Each entry includes an id, slug, title, url, and modified timestamp. The slug field is the key input for drilling into community-level detail — pass it directly as the community_slug parameter to get_community_plans.
Floor Plans and QMI Homes
The get_community_plans endpoint accepts a single required parameter, community_slug, and returns three structured objects. The community object carries header-level metadata: name, builder, home_type, sq_ft_range, bedrooms, bathrooms, garage, status, and the community url. The floor_plans array lists every available plan with plan_name, square_footage, bedrooms, bathrooms, and a features list. The qmi_homes array covers move-ready inventory with title, plan_name, homesite, qmi_price, square_footage, bedrooms, bathrooms, and move_in_date.
Coverage Scope
Data covers RC Homes communities in California only. The list_communities endpoint surfaces all currently published communities without any filtering parameter — community selection happens by iterating the returned slugs and calling get_community_plans for each. The modified field on each community listing can be used to detect recently updated entries without re-fetching all detail pages.
The rchomesinc.com API is a managed, monitored endpoint for rchomesinc.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when rchomesinc.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 rchomesinc.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?+
- Build a new-construction home search tool filtered by bedroom count and square footage using
floor_plansdata. - Track QMI home inventory changes over time by comparing
qmi_priceandhomesitefields across periodic fetches. - Generate a move-in availability calendar from
move_in_datefields across all QMI listings. - Compare
sq_ft_rangeandgaragespecs across multiple communities by iterating slugs fromlist_communities. - Power a real estate CRM sync by monitoring
modifiedtimestamps for community updates. - Aggregate RC Homes floor plan features for competitive new-construction market analysis in California.
| 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 RC Homes have an official developer API?+
What does `get_community_plans` return beyond basic floor plan specs?+
plan_name, square_footage, bedrooms, and bathrooms, the endpoint returns a qmi_homes array with move-ready inventory. Each QMI record includes qmi_price, homesite, move_in_date, and the specific plan_name it is built on, so you can cross-reference a listed price against its parent floor plan spec.Does the API cover communities outside California?+
list_communities returns only California communities. You can fork this API on Parse and revise it to target additional builder sites or regional markets if needed.Can I filter `list_communities` results by region, city, or status?+
list_communities endpoint does not accept filter parameters — it returns all published communities at once. City-level or status-based filtering is not currently exposed. You can fork the API on Parse and revise it to add a filtered endpoint if your use case requires it.Are lot-level details like lot dimensions or elevation options included?+
homesite and qmi_price, but does not expose lot dimensions, elevation packages, or option upgrades. You can fork this API on Parse and revise it to add endpoints covering that additional detail.