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.

Yes. The Free tier on Parse includes 100 API calls per month at no cost with a 5 request-per-minute rate limit. Paid tiers add more credits and higher rate limits: Hobby ($30/month, 1,000 credits, 20 req/min) and Developer ($100/month, 5,000 credits, 250 req/min).

What are the rate limits?

Rate limits are per Parse account, not per API: 5 requests/minute on Free, 20 on Hobby, and 250 on Developer. Exceeding the limit returns a 429 status code. The same limit applies regardless of which marketplace API you call.

How do I authenticate?

Send your Parse API key in the X-API-Key header on every request. Get a key by signing up at parse.bot — no credit card required for the free tier.

Discover/risewellhomes.com API

live

risewellhomes.com APIrisewellhomes.com ↗

Browse floor plans, explore available homes, and discover communities offered by Risewell Homes directly from their new home builder catalog. Find detailed information about QMI homes and community listings to compare options and plan your next purchase.

Endpoint health

monitored

get_community_plans

list_communities

Checks pendingself-healing

Endpoints

Updated

3h ago

Try it

community_slug*

URL slug identifying the community (e.g. 'gage', 'brickline', 'valor-at-liberty'). Obtain from list_communities endpoint.

→ api.parse.bot/scraper/cf2a3ea3-6712-4faa-bd60-3afd87ca9320/<endpoint>

Ready to send

Fill in the parameters and hit sign in to send to see live response data here.

Call it over HTTPgrab a free API key at signup

curl -X GET 'https://api.parse.bot/scraper/cf2a3ea3-6712-4faa-bd60-3afd87ca9320/get_community_plans' \
  -H 'X-API-Key: $PARSE_API_KEY'

Python SDK · recommended

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 risewellhomes-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: Risewell Homes SDK — browse communities, drill into plans and QMI homes."""
from parse_apis.Risewell_Homes_API import RisewellHomes, CommunityNotFound

client = RisewellHomes()

# List communities, capped to 5
for community in client.communities.list(limit=5):
    print(community.name, community.division, community.status)

# Drill into a specific community's floor plans
gage = client.community(slug="gage")
for plan in gage.plans.list(limit=3):
    print(plan.plan_name, plan.square_footage, plan.starting_price, plan.bathrooms)

# Check QMI (quick move-in) homes for same community
for home in gage.qmi_homes.list(limit=3):
    print(home.plan_name, home.qmi_price, home.address, home.status)

# Typed error handling: attempt to fetch a non-existent community
try:
    bad = client.community(slug="nonexistent-community-xyz")
    for plan in bad.plans.list(limit=1):
        print(plan.plan_name)
except CommunityNotFound as exc:
    print(f"Community not found: {exc.community_slug}")

print("exercised: communities.list / community.plans.list / community.qmi_homes.list / CommunityNotFound")

All endpoints · 2 totalmissing one? ·

Retrieve all floor plans and Quick Move-In homes for a specific community. Returns builder name, community name, plan names, square footage, bedrooms, bathrooms, pricing, status, and listing URLs. Each community contains both floor plans (with starting 'from' prices) and QMI homes (with current sale prices, addresses, and move-in dates).

Input

Param	Type	Description
community_slugrequired	string	URL slug identifying the community (e.g. 'gage', 'brickline', 'valor-at-liberty'). Obtain from list_communities endpoint.

Response

{
  "type": "object",
  "fields": {
    "qmi_homes": "array of QMI home objects",
    "floor_plans": "array of floor plan objects",
    "builder_name": "string",
    "community_url": "string",
    "community_name": "string",
    "total_qmi_homes": "integer",
    "total_floor_plans": "integer"
  },
  "sample": {
    "data": {
      "qmi_homes": [
        {
          "city": "Huntington Beach",
          "state": "CA",
          "garage": 2,
          "status": "Move-In Ready",
          "address": "7256 Aura Circle",
          "bedrooms": 2,
          "homesite": "29",
          "bathrooms": 2.5,
          "plan_name": "Plan Two",
          "qmi_price": 969990,
          "listing_url": "https://risewellhomes.com/southern-california/orange-county-new-homes/neighborhoods/gage/lot-29-plan-two/",
          "plan_number": null,
          "postal_code": "92647",
          "builder_name": "Risewell Homes",
          "listing_type": "qmi",
          "community_name": "Gage",
          "square_footage": 1266,
          "starting_price": null,
          "completion_date": "2025-12-01T00:00:00+00:00"
        }
      ],
      "floor_plans": [
        {
          "garage": 2,
          "status": "Now Selling",
          "bedrooms": 3,
          "bathrooms": 2.5,
          "plan_name": "Plan Three",
          "qmi_price": null,
          "listing_url": "https://risewellhomes.com/southern-california/orange-county-new-homes/neighborhoods/gage/plan-three-3/",
          "plan_number": null,
          "bedrooms_max": 3,
          "builder_name": "Risewell Homes",
          "listing_type": "floor_plan",
          "bathrooms_max": 2.5,
          "community_name": "Gage",
          "square_footage": 1389,
          "starting_price": 1124050,
          "square_footage_max": 1389
        }
      ],
      "builder_name": "Risewell Homes",
      "community_url": "https://risewellhomes.com/southern-california/orange-county-new-homes/neighborhoods/gage/",
      "community_name": "Gage",
      "total_qmi_homes": 1,
      "total_floor_plans": 6
    },
    "status": "success"
  }
}

About the risewellhomes.com API

The risewellhomes.com API on Parse exposes 2 endpoints for the publicly available data on risewellhomes.com. Calls return JSON over HTTPS and are billed per successful response.

Pin a release with the API-Snapshot-Version header so canonical updates don't silently change your contract.

Related APIs

zillow.com API

Search for homes for sale, rent, or recently sold listings on Zillow while accessing detailed property information, Zestimates, agent profiles, and current mortgage rates all in one place. Streamline your real estate research by gathering comprehensive property details, agent information, and financing options without navigating multiple pages.

zoopla.co.uk API

Search for properties available for sale or rent, view detailed listing information, check sold house prices, and find local estate agents all in one place. Get access to live marketplace data to help you research properties, compare prices, and connect with agents on the Zoopla platform.

domain.com.au API

Search and compare property listings for sale, rent, or sold properties across Australia, view detailed property information and agent profiles, and explore suburb insights to make informed real estate decisions. Access comprehensive data on agents, neighborhoods, and properties all in one place.

funda.nl API

Search for property listings on Funda.nl, the largest Dutch real estate platform. Access prices, addresses, property details, and agent contact information across Dutch cities and neighbourhoods. Supports paginated browsing and bulk retrieval of listings by area.

rightmove.co.uk API

Search for properties across the UK's largest property portal and retrieve detailed listings for homes for sale or to rent, including prices, descriptions, and key property information. Find your next home or investment opportunity by browsing available properties and getting comprehensive details on individual listings.