nelavida.com APInelavida.com ↗
Access floor plan listings, pricing, and real-time availability for the Nelavida Glassell community in Los Angeles via a single API endpoint.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/eb277da5-3755-4f2e-912f-cb76340593d8/get_floor_plans' \ -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 nelavida-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: Nelavida SDK — retrieve community floor plans and pricing."""
from parse_apis.Nelavida_Homes_API import Nelavida, NotFoundError
client = Nelavida()
# Fetch the full community data including all listings and floor plan details.
try:
community = client.communities.get()
print(f"Community: {community.community}, Builder: {community.builder}")
print(f"Address: {community.address}")
except NotFoundError as exc:
print(f"Community not found: {exc}")
raise SystemExit(1)
# Iterate listings and display plan details.
for listing in community.listings[:5]:
print(f"Lot {listing.lot_number}: {listing.plan_name} | "
f"{listing.bedrooms} bed, {listing.bathrooms} bath | "
f"{listing.square_footage} sqft | {listing.price}")
# Access floor plan summary for base square footage per plan type.
for plan_id, summary in community.floor_plan_summary.items():
print(f"Plan {plan_id} base sqft: {summary.square_footage}")
print("exercised: communities.get / Listing fields / FloorPlanSummary fields")
Retrieves all available floor plan listings for the Nelavida Glassell community. Each listing includes builder name, community name, plan name, lot number, square footage, bedrooms, bathrooms, price (QMI or 'Under Contract'), garage type, and the listing URL. Also returns a floor plan summary with base square footage per plan type. Results reflect current availability and pricing from the community page.
No input parameters required.
{
"type": "object",
"fields": {
"address": "string",
"builder": "string",
"listings": "array of listing objects with builder_name, community_name, plan_name, lot_number, square_footage, bedrooms, bathrooms, price, garage, listing_url",
"community": "string",
"floor_plan_summary": "object mapping plan number to base square footage"
},
"sample": {
"data": {
"address": "3845 Fletcher Drive, Los Angeles, CA 90065",
"builder": "Comstock",
"listings": [
{
"price": "Under Contract",
"garage": "Side x Side",
"bedrooms": "3+ Bonus",
"bathrooms": "2.5",
"plan_name": "Plan 2",
"lot_number": "12",
"listing_url": "https://nelavida.com/pricing/",
"builder_name": "Comstock",
"community_name": "Nelavida Glassell",
"square_footage": "1680"
},
{
"price": "$1,099,000",
"garage": "Side x Side",
"bedrooms": "2+ Bonus",
"bathrooms": "2.5",
"plan_name": "Plan 1",
"lot_number": "25",
"listing_url": "https://nelavida.com/pricing/",
"builder_name": "Comstock",
"community_name": "Nelavida Glassell",
"square_footage": "1642"
}
],
"community": "Nelavida Glassell",
"floor_plan_summary": {
"1": {
"square_footage": "1,642"
},
"2": {
"square_footage": "1,680"
},
"3": {
"square_footage": "1,835"
}
}
},
"status": "success"
}
}About the nelavida.com API
The Nelavida API exposes 1 endpoint — get_floor_plans — that returns all current home listings for the Nelavida Glassell community in Los Angeles. Each listing includes 8 structured fields covering plan name, lot number, square footage, bedroom and bathroom counts, price (or contract status), garage type, and a direct listing URL, plus a community-level floor plan summary object.
What the API Returns
The get_floor_plans endpoint returns all active floor plan listings for the Nelavida Glassell new-construction community in Los Angeles. The response includes a top-level address and community string identifying the development, a builder field naming the builder, and a listings array containing individual home objects.
Listing-Level Fields
Each object in the listings array contains builder_name, community_name, plan_name, lot_number, square_footage, bedrooms, bathrooms, price, garage type, and a listing_url pointing directly to that home's detail page. The price field reflects either a quoted market-inventory (QMI) price or the string "Under Contract" when the lot is no longer available for purchase — useful for filtering active vs. contracted inventory.
Floor Plan Summary
Beyond individual listings, the response includes a floor_plan_summary object that maps each plan number to its base square footage. This lets you quickly compare layout sizes across plans without iterating the full listings array. The endpoint takes no input parameters; it always returns the full current inventory for the community.
The nelavida.com API is a managed, monitored endpoint for nelavida.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nelavida.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 nelavida.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?+
- Track which lots at Nelavida Glassell are still available vs. under contract using the
pricefield - Build a price-per-square-foot calculator from the
priceandsquare_footagefields - Filter listings by
bedroomsorbathroomscount to match buyer requirements - Display an inventory table sorted by
lot_numberfor a new-home sales dashboard - Compare base square footage across plan types using the
floor_plan_summaryobject - Monitor inventory shrinkage over time by polling the
listingsarray for status changes
| 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 Nelavida have an official developer API?+
What does the `price` field actually contain?+
price field returns either a numeric QMI (quoted market inventory) price string for homes available for purchase, or the literal string "Under Contract" for lots that have already been reserved. You can use this to filter active vs. contracted inventory in your application.Does the API cover multiple Nelavida communities or locations beyond Glassell?+
Are individual home photos or virtual tour links included in the response?+
listing_url you can follow for the full detail page. You can fork the API on Parse and revise it to pull media assets from those detail pages.How fresh is the availability data?+
get_floor_plans endpoint reflects the current state of the Nelavida Glassell listing inventory at the time of the request. Because new-construction inventory can change when lots are contracted or released, polling the endpoint periodically will give you the most up-to-date picture.