Trumark Homes APItrumarkhomes.com ↗
Access Trumark Homes community listings, floor plans, QMI inventory, pricing, and specs across California and Colorado via two API endpoints.
What is the Trumark Homes API?
The Trumark Homes API exposes new-construction community data across California and Colorado through 2 endpoints. Use list_communities to enumerate all communities with their slugs, then pass any slug to get_community_listings to retrieve floor plans and available quick move-in (QMI) homes — each with square footage, bedroom/bathroom counts, garage details, and pricing.
curl -X GET 'https://api.parse.bot/scraper/f9276554-7a8e-480a-8846-6c82ffd5d68a/get_community_listings' \ -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 trumarkhomes-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: TrumarkHomes SDK — browse communities and drill into listings."""
from parse_apis.Trumark_Homes_API import TrumarkHomes, CommunityNotFound
client = TrumarkHomes()
# List communities in Colorado, capped at 5 results.
for community in client.communities.list(state="co", limit=5):
print(community.community_name, community.url)
# Drill into a specific community's floor plans and available homes.
community = client.communities.list(state="ca", limit=1).first()
if community:
listings = community.listings()
print(listings.builder_name, listings.community_name)
# Inspect floor plans
for plan in listings.floor_plans:
print(plan.plan_name, plan.square_footage, plan.from_price)
# Inspect available homes (QMI)
for home in listings.available_homes:
print(home.address, home.plan_name, home.qmi_price)
# Typed error handling: catch a missing community.
try:
missing = client.community("/new-homes/ca/nowhere/fake/").listings()
except CommunityNotFound as exc:
print(f"Community not found: {exc.community_slug}")
print("exercised: communities.list / community.listings / floor_plans / available_homes")
Retrieve all floor plans and available homes (quick move-in / QMI) for a specific Trumark Homes community. Returns builder name, community name, and two arrays: floor_plans (with plan name, square footage, bedrooms, bathrooms, from price, and listing URL) and available_homes (with address, lot number, QMI price, availability date, and listing URL). Communities without available homes return an empty available_homes array.
| Param | Type | Description |
|---|---|---|
| community_slugrequired | string | URL path slug identifying the community, in the format '<state>/<city>/<community-name>' (e.g. 'ca/rancho-mission-viejo/lotus-at-rienda'). Also accepts the full path with '/new-homes/' prefix. Obtain valid slugs from the list_communities endpoint's href field. |
{
"type": "object",
"fields": {
"floor_plans": "array of floor plan objects with plan_name, square_footage, bedrooms, bathrooms, garage, from_price, qmi_price, listing_url",
"builder_name": "string",
"community_url": "string",
"community_name": "string",
"available_homes": "array of available home objects with plan_name, address, lot, square_footage, bedrooms, bathrooms, garage, from_price, qmi_price, availability, listing_url"
},
"sample": {
"data": {
"floor_plans": [
{
"garage": "2",
"bedrooms": "3 - 5",
"bathrooms": "3 Ba",
"plan_name": "Plan 1",
"qmi_price": "",
"from_price": "$1,650,370",
"listing_url": "https://trumarkhomes.com/new-homes/ca/rancho-mission-viejo/lotus-at-rienda/plan-1/",
"builder_name": "Trumark Homes",
"community_name": "Lotus at Rienda",
"square_footage": "2,769"
}
],
"builder_name": "Trumark Homes",
"community_url": "https://trumarkhomes.com/new-homes/ca/rancho-mission-viejo/lotus-at-rienda/",
"community_name": "Lotus at Rienda",
"available_homes": [
{
"lot": "Lot #32",
"garage": "2",
"address": "266 Renewal Rd",
"bedrooms": "4",
"bathrooms": "4 Ba, 1 Half Ba",
"plan_name": "Plan 3",
"qmi_price": "",
"from_price": "",
"listing_url": "https://trumarkhomes.com/new-homes/ca/rancho-mission-viejo/lotus-at-rienda/plan-3/266-renewal-rd/",
"availability": "Available November 2026",
"builder_name": "Trumark Homes",
"community_name": "Lotus at Rienda",
"square_footage": "3,129"
}
]
},
"status": "success"
}
}About the Trumark Homes API
Endpoints
The API has two endpoints. list_communities returns every active Trumark Homes community as an array of objects containing community_name, href (the slug), and url. The optional state parameter accepts ca or co to narrow results; omitting it returns all communities. The response also includes a total integer showing the count of matched communities.
Community Detail
get_community_listings accepts a community_slug in the format <state>/<city>/<community-name> — exactly the href value from list_communities. It returns two arrays: floor_plans and available_homes. Each floor plan object includes plan_name, square_footage, bedrooms, bathrooms, garage, from_price, qmi_price, and listing_url. Available home objects carry the same spec fields plus an address and lot identifier, distinguishing a specific build-ready or move-in-ready unit from a base floor plan.
Data Coverage
Coverage is limited to Trumark Homes communities in California and Colorado. Pricing fields (from_price, qmi_price) reflect the listed base and quick move-in prices for each plan or specific home. The community_url and listing_url fields link back to the canonical pages on trumarkhomes.com, useful for deeplinking users to the builder's site for further detail or contact.
The Trumark Homes API is a managed, monitored endpoint for trumarkhomes.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when trumarkhomes.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 trumarkhomes.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 Trumark Homes new-construction listings alongside MLS data for a real estate search portal
- Monitor
from_priceandqmi_pricechanges across California communities for market analysis - Build a new-home finder that filters communities by state using the
stateparameter inlist_communities - Display available inventory with
addressandlotfields to show buyers which specific homes are ready to close - Compare floor plan specs (
square_footage,bedrooms,bathrooms,garage) across multiple communities - Feed community slugs from
list_communitiesinto automated nightly pulls ofget_community_listingsto track inventory 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 | 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 Trumark Homes have an official public developer API?+
What distinguishes `floor_plans` from `available_homes` in the `get_community_listings` response?+
floor_plans objects represent plan templates — they carry plan_name, size, bed/bath/garage specs, and a base from_price. available_homes objects represent specific lots or units that are built or under construction, adding address and lot fields and a qmi_price that may differ from the base plan price.Does the API cover communities outside California and Colorado?+
list_communities endpoint only returns communities in California (ca) and Colorado (co), matching Trumark Homes' current geographic footprint. You can fork this API on Parse and revise it to add coverage if Trumark expands to additional states.Can I retrieve community amenities, neighborhood details, or photo galleries?+
How do I get the correct `community_slug` value for `get_community_listings`?+
list_communities first and read the href field from any returned community object. That value is the slug in <state>/<city>/<community-name> format and can be passed directly as the community_slug parameter.