Discover/terracesatwalnut.com API
live

terracesatwalnut.com APIterracesatwalnut.com

Access neighborhood summaries, floor plan specs, and homesite details for The Terraces at Walnut new home community in Walnut, CA via a structured API.

Endpoint health
verified 56m ago
get_plan_details
list_neighborhoods
list_floor_plans
3/3 passing latest checkself-healing
Endpoints
3
Updated
4h ago
Try it

No input parameters required.

api.parse.bot/scraper/c0b15a27-3de9-4868-9198-b84723c79625/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Use it in your codegrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/c0b15a27-3de9-4868-9198-b84723c79625/list_neighborhoods' \
  -H 'X-API-Key: $PARSE_API_KEY'
Or use the typed Python SDKfully typed · autocompletes

Typed Python client. Install the CLI, sign in, then pull this API’s generated client:

pip install parse-sdk
parse login
parse add --marketplace terracesatwalnut-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: The Terraces at Walnut SDK — browse neighborhoods and floor plans."""
from parse_apis.The_Terraces_at_Walnut_API import TerracesAtWalnut, Neighborhood_, HomesiteNotFound

client = TerracesAtWalnut()

# List all neighborhoods with starting prices and home types.
for hood in client.neighborhoods.list(limit=4):
    print(hood.name, hood.starting_price, hood.type)

# Drill into Felice to see available floor plans.
felice = client.neighborhood(slug=Neighborhood_.FELICE)
for plan in felice.plans(limit=5):
    print(plan.plan_name, plan.square_footage, plan.status, plan.bedrooms)

# Get full details (including caption) for one homesite.
first_plan = felice.plans(limit=1).first()
if first_plan:
    detail = first_plan.details()
    print(detail.plan_name, detail.caption)

# Typed error handling — homesite not found.
try:
    bad = client.neighborhood(slug=Neighborhood_.TRENTO)
    for p in bad.plans(limit=1):
        p_detail = p.details()
except HomesiteNotFound as exc:
    print(f"Homesite gone: {exc}")

print("exercised: neighborhoods.list / neighborhood.plans / plan.details")
All endpoints · 3 totalmissing one? ·

List all neighborhoods in The Terraces at Walnut community with their starting prices, home types, and size ranges. Returns community-level summary data for Felice, Trento, Altea, and Las Vistas.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "total": "integer",
    "neighborhoods": "array of neighborhood summaries including name, slug, type, starting_price, square_footage_range, bedrooms, bathrooms, gated, url"
  },
  "sample": {
    "data": {
      "total": 4,
      "neighborhoods": [
        {
          "url": "https://terracesatwalnut.com/neighborhoods/felice/",
          "name": "Felice",
          "slug": "felice",
          "type": "Two-Story Townhomes",
          "gated": false,
          "bedrooms": "3 – 4 Bedrooms",
          "bathrooms": "2.5 – 3 Baths",
          "starting_price": "Starting from $1.083M",
          "square_footage_range": "Approx. 1,570 – 1,927 Sq. Ft."
        },
        {
          "url": "https://terracesatwalnut.com/neighborhoods/trento/",
          "name": "Trento",
          "slug": "trento",
          "type": "Two-Story Single-Family Homes",
          "gated": true,
          "bedrooms": "Up to 5 Bedrooms + Den + Bonus",
          "bathrooms": "5.5 Baths",
          "starting_price": "Starting from Mid $1.6M",
          "square_footage_range": "Approx. 4,167 - 4,488 Sq. Ft."
        }
      ]
    },
    "status": "success"
  }
}

About the terracesatwalnut.com API

The Terraces at Walnut API provides 3 endpoints covering neighborhood listings, floor plan records, and individual homesite details for CBC Home's Walnut, CA community. list_floor_plans returns plan names, square footage, bedroom and bathroom counts, availability status, and QMI pricing across all four neighborhoods — Felice, Trento, Altea, and Las Vistas — in a single call.

Neighborhoods and Community Overview

list_neighborhoods returns a summary array for all four neighborhoods in The Terraces at Walnut community. Each record includes name, slug, type, starting_price, square_footage_range, bedrooms, bathrooms, a gated flag, and a direct url. This endpoint takes no parameters and gives a fast top-level view of what the community offers without requiring a homesite-level query.

Floor Plans by Neighborhood

list_floor_plans accepts an optional neighborhood parameter (accepted slugs: felice, trento, altea, las-vistas). Omitting the parameter returns every floor plan across all neighborhoods. Each record in the plans array includes builder_name, community_name, neighborhood_slug, plan_name, homesite_number, square_footage, bedrooms, bathrooms, availability_status, qmi_price (present when a quick move-in price is listed), starting_price, and listing_url. The total field gives the count of matched records.

Homesite Detail

get_plan_details requires both a neighborhood slug and a homesite number (e.g. '28'). Valid homesite numbers can be discovered through list_floor_plans. The response adds a caption and a description field that contain plan-specific feature text not present in the list endpoint, alongside the full pricing and spec fields. The status field reflects current availability at the time of the request.

Reliability & maintenanceVerified

The terracesatwalnut.com API is a managed, monitored endpoint for terracesatwalnut.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when terracesatwalnut.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 terracesatwalnut.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.

Last verified
56m ago
Latest check
3/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Display a filterable grid of available homesites sorted by square footage or price for a new-home search tool.
  • Track QMI (quick move-in) pricing changes across Felice, Trento, Altea, and Las Vistas over time.
  • Populate a neighborhood comparison table with starting prices and bedroom ranges from list_neighborhoods.
  • Build a homesite availability alert system using the status field from get_plan_details.
  • Aggregate floor plan data across all neighborhoods to identify which plan sizes and configurations are most available.
  • Feed homesite listing URLs and pricing into a real estate CRM or lead-generation workflow.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000250 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.

Frequently asked questions
Does terracesatwalnut.com have an official developer API?+
No. The terracesatwalnut.com website does not publish a public developer API or data feed.
What does list_floor_plans return when no neighborhood filter is provided?+
It returns every floor plan record across all four neighborhoods — Felice, Trento, Altea, and Las Vistas — in a single response. Each record includes plan_name, homesite_number, square_footage, bedrooms, bathrooms, availability_status, qmi_price (when available), starting_price, and listing_url. You can narrow results by passing the neighborhood parameter with one of the four accepted slugs.
Does the API expose community amenities, site maps, or photo galleries?+
Not currently. The API covers neighborhood summaries, floor plan specs, homesite availability, and pricing. Amenity descriptions, interactive site maps, and photo assets are not included in the current endpoints. You can fork this API on Parse and revise it to add an endpoint for those data points.
How do I find valid homesite numbers to use with get_plan_details?+
Call list_floor_plans with the relevant neighborhood slug. Each record in the returned plans array includes a homesite_number field. Pass that value as the homesite parameter in get_plan_details along with the matching neighborhood slug.
Is pricing data available for every homesite?+
Not for every record. The qmi_price field is present only when a quick move-in price is actively listed for that homesite. The starting_price field is available at the plan level. Homesites without a QMI price will return null for that field. The API covers what is publicly listed; contract or negotiated pricing is not exposed. You can fork this API on Parse and revise it to surface additional pricing signals if they become available on the site.
Page content last updated . Spec covers 3 endpoints from terracesatwalnut.com.