California Pacific Homes APIcaliforniapacifichomes.com ↗
Access California Pacific Homes communities, floor plans, and quick move-in listings across Southern California via a structured REST API.
What is the California Pacific Homes API?
This API exposes 3 endpoints covering California Pacific Homes new-home communities in Southern California, including community summaries, detailed floor plans, and quick move-in inventory. The list_communities endpoint returns all active neighborhoods with pricing, bedroom/bathroom counts, and square footage ranges in a single call, while get_community_plans and get_quick_move_ins provide plan-level and ready-inventory detail for any of the five supported community slugs.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/c846f122-7341-4b41-83ed-d23144a71d22/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 californiapacifichomes-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: California Pacific Homes SDK — browse communities, plans, and move-in ready homes."""
from parse_apis.California_Pacific_Homes_API import CaliforniaPacificHomes, CommunityNotFound
client = CaliforniaPacificHomes()
# List all communities with summary info
for community in client.communities.list(limit=5):
print(community.name, community.city, community.starting_price)
# Drill into a specific community's floor plans
irvine = client.community(slug="fiore")
for plan in irvine.plans.list(limit=5):
print(plan.plan_name, plan.square_footage, plan.bedrooms, plan.bathrooms)
# Browse quick move-in homes for a community
for home in irvine.quick_move_ins.list(limit=5):
print(home.plan_name, home.address, home.qmi_price)
# Handle a community that doesn't exist
try:
bad = client.community(slug="nonexistent")
for plan in bad.plans.list(limit=1):
print(plan.plan_name)
except CommunityNotFound as exc:
print(f"Community not found: {exc}")
print("exercised: communities.list / plans.list / quick_move_ins.list / CommunityNotFound")
Lists all active California Pacific Homes communities (neighborhoods) with summary details including city, home type, square footage range, bedroom/bathroom counts, and starting price. Returns one entry per community.
No input parameters required.
{
"type": "object",
"fields": {
"communities": "array of community summary objects"
},
"sample": {
"data": {
"communities": [
{
"url": "https://californiapacifichomes.com/neighborhoods/andalucia/",
"city": "Irvine",
"name": "Andalucia",
"slug": "andalucia",
"qmi_url": "https://californiapacifichomes.com/neighborhoods/andalucia/quick-move-ins",
"bedrooms": "2 to 4 Bedrooms",
"bathrooms": "2.5 Baths",
"home_type": "Detached Homes",
"floorplans_url": "https://californiapacifichomes.com/neighborhoods/andalucia/floorplans/1/",
"square_footage": "Approximately 1,326 to 1,752 Sq. Ft.",
"starting_price": "From $1.5 Million"
},
{
"url": "https://californiapacifichomes.com/neighborhoods/fiore/",
"city": "Irvine",
"name": "Fiore",
"slug": "fiore",
"qmi_url": "https://californiapacifichomes.com/neighborhoods/fiore/quick-move-ins",
"bedrooms": "3 to 4 Bedrooms",
"bathrooms": "2.5 to 3 Baths",
"home_type": "Detached Homes",
"floorplans_url": "https://californiapacifichomes.com/neighborhoods/fiore/floorplans/1/",
"square_footage": "Approximately 2,035 to 2,410 Sq. Ft.",
"starting_price": "From the High $1 Millions"
}
]
},
"status": "success"
}
}About the California Pacific Homes API
Community Listings and Summaries
The list_communities endpoint returns an array of all active California Pacific Homes neighborhoods. Each community summary object includes the city, home type, square footage range, bedroom and bathroom counts, and a starting price. No parameters are required — one call retrieves the full active portfolio across communities like Fiore, Azul, Paloma, Andalucia, and Sierra.
Floor Plans by Community
The get_community_plans endpoint accepts a community slug (one of andalucia, paloma, fiore, azul, or sierra) and returns an array of floor plan objects. Each plan includes the builder name, community name, plan name or number, square footage, bedroom and bathroom counts, additional distinguishing features, and a direct listing URL. The response also surfaces the community's current starting price from the overview page as a top-level starting_price field, which may be null if not published.
Quick Move-In Homes
The get_quick_move_ins endpoint uses the same community slug parameter and returns homes that are completed or near completion and available for immediate purchase. Each QMI object includes the builder name, community name, a plan name combined with homesite number, street address, square footage, bedroom count, bathroom count, and QMI-specific fields. The response mirrors the structure of get_community_plans with community_name, community_slug, and starting_price at the top level alongside the homes array.
Coverage and Scope
All three endpoints are scoped to California Pacific Homes' active Southern California developments. The five supported community slugs map directly to the builder's current neighborhood portfolio. Data reflects what is published on the community and floor plan pages, including pricing and availability as listed.
The California Pacific Homes API is a managed, monitored endpoint for californiapacifichomes.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when californiapacifichomes.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 californiapacifichomes.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 all active California Pacific Homes communities and their starting prices into a single comparison table
- Display floor plan options with square footage and bedroom counts for a specific community like Fiore or Azul
- Surface quick move-in inventory for buyers who need immediate availability at a specific community
- Track starting price changes across communities over time using repeated
list_communitiescalls - Build a new-home search tool filtered by community, bedrooms, and square footage using floor plan data
- Generate community profile pages with plan count, QMI count, and pricing for each of the five neighborhoods
| 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 California Pacific Homes offer an official developer API?+
What distinguishes a Quick Move-In home from a floor plan in the API response?+
get_community_plans returns abstract floor plan configurations — square footage, bedroom/bathroom counts, and a listing URL — without a specific address or homesite. get_quick_move_ins returns specific homes tied to a street address and homesite number, indicating units that are completed or near completion and available for immediate purchase.Are communities outside the five supported slugs accessible?+
Does the API return lot availability, pricing per homesite, or buyer incentive details?+
How many communities does `list_communities` return, and can the response be filtered?+
list_communities takes no parameters and returns all active communities as a single array — currently five neighborhoods. There is no server-side filtering; any filtering by city, home type, price, or bedroom count would need to be applied client-side after receiving the full response.