Active Adult Living APIactiveadultliving.com ↗
Access 55+ active adult retirement community data across the USA and Canada. Browse by state, lifestyle, pricing, amenities, and community details.
What is the Active Adult Living API?
The Active Adult Living API provides structured access to 55+ and active adult retirement community data across all 50 US states and Canadian provinces through 5 endpoints. Starting with get_states, you can retrieve every covered jurisdiction along with community counts, then drill into individual listings via get_community_detail to pull full records including street address, price ranges, amenities, gallery images, and HTML descriptions.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/0ceb27ed-b293-475f-9637-8df608916b94/get_states' \ -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 activeadultliving-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: Active Adult Living API — discover 55+ communities by state."""
from parse_apis.active_adult_living_api import ActiveAdultLiving, CommunityNotFound
client = ActiveAdultLiving()
# List all available lifestyles (community categories)
for lifestyle in client.lifestyles.list(limit=5):
print(lifestyle.name, lifestyle.url)
# List states with their community counts
for state in client.states.list(limit=5):
print(state.name, state.abbreviation, state.communities_count)
# Construct a state and browse its communities
florida = client.state(abbreviation="FL")
for community in florida.communities(limit=3):
print(community.community_name, community.zip, community.home_type)
# Get showcase (premium/featured) communities for a state
showcase = florida.showcase(limit=1).first()
if showcase:
print(showcase.community_name, showcase.priced_from, showcase.community_desc[:80])
# Get full community detail using params from listing results
try:
detail = client.communitydetails.get(
state_abbr="FL", state_name="Florida",
lifestyle_slug="55-plus-communities", city_slug="ocala",
zip="34482", community_slug="shea-homes-at-ocala-preserve"
)
print(detail.community_name, detail.address, detail.priced_from)
except CommunityNotFound as exc:
print(f"Community not found: {exc.community_slug}")
print("exercised: lifestyles.list / states.list / state().communities / state().showcase / communitydetails.get / CommunityNotFound")
Returns all US states and Canadian provinces that have active adult communities listed. Each entry includes the state name, two-letter abbreviation, URL slug, and a count of communities in that state. No parameters required.
No input parameters required.
{
"type": "object",
"fields": {
"states": "array of state objects with id, name, abbreviation, url, and communities_count"
},
"sample": {
"data": {
"states": [
{
"id": 8,
"url": "alabama-active-adult-55-plus-communities",
"name": "Alabama",
"abbreviation": "AL",
"communities_count": 85
},
{
"id": 10,
"url": "arizona-active-55-plus-adult-communities",
"name": "Arizona",
"abbreviation": "AZ",
"communities_count": 492
}
]
},
"status": "success"
}
}About the Active Adult Living API
Coverage and Structure
The API covers active adult and 55+ retirement communities listed on activeadultliving.com across the USA and Canada. get_states returns every state and province that has at least one listing, including the two-letter abbreviation, URL slug, and a count of communities. get_lifestyles returns the full taxonomy of lifestyle categories — such as Golf Course Communities and Waterfront — each with a name and URL slug used for filtering elsewhere.
Browsing Communities
get_communities_by_state accepts a required abbreviation parameter (e.g. FL, AZ, ON) and optional limit and offset integers for pagination. Each returned community object includes community_name, community_url, home_type, phone, zip, and nested city, state, and lifestyle objects. get_showcase_communities accepts the same abbreviation and returns premium listings that add image, priced_from, and community_desc fields.
Community Detail
get_community_detail requires six parameters sourced from listing results: zip, city_slug, state_abbr, state_name, community_slug, and lifestyle_slug. The response contains the most complete record in the API: a full address, an overview object with key-value stats (Number of Homes, Home Type, Sq Ft), an amenities array, home_types array, priced_from and priced_to price strings, a description in HTML, and an images array of gallery URLs. All lookup parameters come directly from fields returned by the listing endpoints, so a typical workflow is state browse → listing page → detail record.
Limitations and Scope
Canadian provinces are supported by get_communities_by_state but get_showcase_communities is documented for US states only. Pagination in get_communities_by_state is controlled manually via offset and limit; there is no cursor-based or total-count field in the response to automate full traversal without tracking offsets yourself.
The Active Adult Living API is a managed, monitored endpoint for activeadultliving.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when activeadultliving.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 activeadultliving.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?+
- Build a retirement community search tool filtered by state using
get_communities_by_stateand lifestyle category fromget_lifestyles. - Aggregate pricing data (
priced_from,priced_to) across communities in a target state for market research. - Generate comparison pages for 55+ communities using amenities arrays and overview stats from
get_community_detail. - Populate a map interface with community addresses, ZIP codes, and phone numbers pulled from detail records.
- Create a featured listings widget for a real estate portal using showcase community images and descriptions from
get_showcase_communities. - Track community counts per state over time using the
communities_countfield fromget_states. - Build a lifestyle-based recommendation engine matching users to community categories returned by
get_lifestyles.
| 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 activeadultliving.com have an official developer API?+
What does `get_community_detail` return beyond what the listing endpoints provide?+
get_community_detail returns the full street address, an overview object with stats like Number of Homes and square footage, an amenities string array, a home_types array, both priced_from and priced_to price strings, an HTML description, and a gallery images array. The listing endpoints (get_communities_by_state, get_showcase_communities) return only summary-level fields like phone, ZIP, and city.How does pagination work in `get_communities_by_state`?+
offset (number of items to skip) and an integer limit (items per page). The response does not include a total count field, so you need to keep fetching with increasing offsets until you receive fewer results than your limit value.Does the API support searching communities by lifestyle category or amenity directly?+
get_communities_by_state filters only by state abbreviation. Lifestyle category data is available on individual community records via the nested lifestyle object, but there is no endpoint that accepts a lifestyle slug as a filter parameter. You can fork this API on Parse and revise it to add a lifestyle-filtered communities endpoint.