activeadultliving.com APIactiveadultliving.com ↗
Access 55+ and active adult community data across the USA and Canada. Search by state, lifestyle, pricing, amenities, and more via 5 structured endpoints.
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'
Returns a list of all US states and Canadian provinces with community counts. No parameters required.
No input parameters required.
{
"type": "array",
"fields": {
"id": "integer, unique state identifier",
"url": "string, URL slug for the state",
"name": "string, full state/province name",
"abbreviation": "string, two-letter abbreviation",
"communities_count": "integer, number of communities in that state"
},
"sample": {
"data": [
{
"id": 8,
"url": "alabama-active-adult-55-plus-communities",
"name": "Alabama",
"abbreviation": "AL",
"communities_count": 82
},
{
"id": 10,
"url": "arizona-active-55-plus-adult-communities",
"name": "Arizona",
"abbreviation": "AZ",
"communities_count": 492
}
],
"status": "success"
}
}About the activeadultliving.com API
The Active Adult Living API exposes 5 endpoints that return structured data on 55+ and active adult communities across the USA and Canada, sourced from activeadultliving.com. Using get_communities_by_state, you can retrieve paginated listings with city, ZIP, phone, home type, and lifestyle category for any US state or Canadian province. Companion endpoints cover showcase listings with pricing and images, full community detail pages, state/province inventory counts, and lifestyle filter categories.
Coverage and Navigation
get_states returns every US state and Canadian province tracked on the site, each with a communities_count and a URL slug usable as a navigation key. get_lifestyles returns the lifestyle taxonomy — categories like 55+ Communities or Golf Course Communities — with slugs that appear in community-level responses. Both endpoints take no parameters and are the natural starting point for building browse or search interfaces.
Community Listings by State
get_communities_by_state accepts a required abbreviation (e.g., FL, AZ, ON) plus optional limit and offset for pagination. Each result includes community_name, community_url, city (with id, name, and slug), state, zip, phone, home_type, and a nested lifestyle object. The slugs returned in city.url, community_url, and lifestyle.url are the exact parameters needed to call get_community_detail.
get_showcase_communities takes the same abbreviation input and returns featured listings that carry additional fields: an image thumbnail URL, an HTML community_desc, and a priced_from value. These are the premium placements on the site and typically have richer editorial content than standard listings.
Full Community Detail
get_community_detail requires six parameters — zip, city_slug, state_abbr, state_name, community_slug, and lifestyle_slug — all obtainable directly from get_communities_by_state results. The response includes address, description, priced_from, priced_to, an amenities array, a home_types array, an images gallery array, and an overview object containing key-value pairs of structured community facts. This endpoint is the primary source of actionable detail for any individual property.
- Build a state-by-state directory of 55+ communities using
communities_countfromget_statesto size each category page. - Generate comparison pages for active adult communities in a given state, surfacing
priced_from,home_type, andamenitiesside by side. - Populate a retirement relocation tool that filters communities by lifestyle category using slugs from
get_lifestyles. - Display showcase community cards with thumbnail images, HTML descriptions, and starting prices from
get_showcase_communities. - Build a community detail page with full gallery, amenity lists, address, and price range sourced from
get_community_detail. - Track inventory changes per state over time by periodically polling
get_statesforcommunities_countdeltas. - Feed community contact data — phone numbers, ZIP codes, and addresses — into a CRM or lead-routing system for senior living advisors.
| 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 activeadultliving.com have an official developer API?+
What does `get_community_detail` return beyond what the listing endpoints provide?+
get_community_detail adds fields not present in list-level responses: a full address, an amenities array, a home_types array, a multi-image images gallery, priced_to (upper price bound), and an overview object with structured key-value community facts. The six required parameters — zip, city_slug, state_abbr, state_name, community_slug, and lifestyle_slug — all come directly from get_communities_by_state results.Can I filter communities by lifestyle category or price range within a state?+
get_communities_by_state endpoint does not currently accept lifestyle or price filters — it returns all communities for a given state abbreviation and relies on limit/offset pagination. Filtering by lifestyle or price range would require post-processing the results client-side. You can fork this API on Parse and revise it to add server-side filter parameters if needed.Does the API cover Canadian provinces, or only US states?+
get_states includes Canadian provinces alongside US states, and get_communities_by_state accepts Canadian province abbreviations (e.g., ON for Ontario). Coverage depth varies by province since the source site has more US listings than Canadian ones.Is there an endpoint to search communities by city or ZIP code rather than by state?+
get_communities_by_state; there is no city-level or ZIP-level search endpoint. You can fork this API on Parse and revise it to add a city or ZIP search endpoint.