Liveoakpointe APIliveoakpointe.com ↗
Access Oakpointe Fountain Valley floor plan data including square footage, bedrooms, bathrooms, garages, elevations, and pricing via 2 REST endpoints.
What is the Liveoakpointe API?
The liveoakpointe.com API provides 2 endpoints for retrieving floor plan data from the Oakpointe Fountain Valley new-home community. Call get_floor_plans to list all available plans with pricing, bedroom and bathroom counts, and listing URLs, or use get_plan_details to fetch full specifications for a single plan including garage count, number of levels, and elevation styles.
curl -X GET 'https://api.parse.bot/scraper/08492f18-89f0-4c23-ba97-3cdb7eb6a04c/get_floor_plans?community_id=23221_A_8572TalbertAve' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieves all floor plans for the Oakpointe community from the static site page. Returns builder name, community name, plan name/code, square footage, bedrooms, bathrooms, garages, levels, and listing URL for each plan. The community_id parameter is accepted for compatibility but the site currently serves a single community.
| Param | Type | Description |
|---|---|---|
| community_id | string | Focus360 community identifier. |
{
"type": "object",
"fields": {
"plans": "array of floor plan objects",
"total": "integer"
},
"sample": {
"data": {
"plans": [
{
"levels": 2,
"garages": 2,
"bedrooms": 3,
"bathrooms": 2.5,
"plan_code": "1",
"plan_name": "Plan 1",
"qmi_price": null,
"listing_url": "https://liveoakpointe.com/homes/",
"builder_name": "Bonanni Development",
"community_name": "Oakpointe Fountain Valley",
"square_footage": 1811,
"starting_price": null
}
],
"total": 1
},
"status": "success"
}
}About the Liveoakpointe API
Endpoints and Coverage
The API covers the Oakpointe Fountain Valley community, defaulting to that community's identifier on both endpoints so no extra configuration is needed for the primary use case. get_floor_plans returns an array of plan objects and a total count, with each object including builder_name, community_name, plan_name, plan_code, square footage, bedrooms, bathrooms, a pricing field, and a listing_url pointing to the plan page on liveoakpointe.com.
Plan-Level Detail
get_plan_details accepts a plan_code string (e.g. '1', '2', '3', '4') obtained from get_floor_plans results, plus an optional community_id. The response adds fields not present in the list view: levels (number of stories), garages, an elevations array describing available exterior style options, and qmi_price (which is a number when a quick move-in price is available, or null otherwise). This makes it straightforward to build a detail page or comparison table without a second lookup to the source site.
Community Scope and Parameters
Both endpoints accept an optional community_id parameter to target a specific Focus360 community identifier. The default targets Oakpointe Fountain Valley, so passing community_id is only necessary when querying an alternate community. Plan codes are short numeric strings and should be sourced from the get_floor_plans response rather than assumed, since available codes depend on what the community currently lists.
The Liveoakpointe API is a managed, monitored endpoint for liveoakpointe.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when liveoakpointe.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 liveoakpointe.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?+
- Display a floor plan comparison table showing square footage, bedrooms, bathrooms, and pricing for all available Oakpointe plans.
- Build a new-home search widget that surfaces
qmi_priceto highlight quick move-in availability. - Render elevation style thumbnails or labels from the
elevationsarray on a plan detail page. - Filter plans by
bedroomsorbathroomscount to match buyer criteria in a home-search tool. - Track pricing changes across floor plans over time by polling
get_floor_plansand storing the results. - Generate deep links to individual plan pages on liveoakpointe.com using the
listing_urlfield from each plan object. - Populate a CRM or lead-routing tool with structured plan data keyed on
plan_codeandbuilder_name.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does liveoakpointe.com have an official developer API?+
What does `get_plan_details` return that `get_floor_plans` does not?+
get_plan_details adds levels (number of stories), garages, an elevations array of exterior style options, and a qmi_price field that is null when no quick move-in price is listed. The list endpoint omits those fields and focuses on summary data suitable for browsing.Does the API cover lot availability, site maps, or inventory status beyond QMI pricing?+
How do I get the right `plan_code` values for `get_plan_details`?+
get_floor_plans first. Each object in the returned plans array includes a plan_code string (e.g. '1', '2'). Pass that value directly to get_plan_details. Assuming codes without checking the list risks a failed lookup if the community's available plans change.Is data available for communities other than Oakpointe Fountain Valley?+
community_id parameter accepts a Focus360 community identifier, so other Focus360-backed communities are addressable in principle, but only Oakpointe Fountain Valley is tested and covered by default. You can fork this API on Parse and revise it to target additional communities.