Pacaso APIpacaso.com ↗
Access Pacaso luxury co-ownership listings via API. Get price per share, bedrooms, bathrooms, amenities, photos, and destinations across all active markets.
What is the Pacaso API?
The Pacaso API exposes 3 endpoints for accessing fractional property ownership listings, destination markets, and individual property details from Pacaso.com. Use get_listings to retrieve full listing records with price per share, square footage, and amenities across all active markets, or filter by a specific destination like Lake Tahoe or Paris. Use get_listing_detail for the complete photo set and highlights for a single property identified by its UUID.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/8773d2aa-0d89-43b2-92d3-3acb06fb7dae/list_destinations' \ -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 pacaso-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.
from parse_apis.pacaso_property_listings_api import Pacaso, Destination, Listing
pacaso = Pacaso()
# List all destinations and find ones with available homes
for dest in pacaso.destinations.list():
if dest.num_discoverable_homes > 0:
print(dest.name, dest.state, dest.num_discoverable_homes, dest.avg_share_price)
# Get listings for a specific destination using constructible navigation
tahoe = pacaso.destination(name="Lake Tahoe")
for listing in tahoe.listings(count=5):
print(listing.name, listing.price_per_share, listing.bedrooms, listing.bathrooms)
print(listing.location.city, listing.location.state_or_province)
for photo in listing.photos:
print(photo.url, photo.type, photo.sort_order)
# Browse all listings across destinations
for listing in pacaso.listings.list(destination="Napa Valley"):
print(listing.pacaso_home_id, listing.name, listing.square_feet, listing.whole_home_value)
List all available Pacaso destinations/markets with summary stats including number of discoverable homes, average share price, and top amenities. Returns all markets regardless of whether they currently have discoverable homes.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer - total number of destinations",
"destinations": "array of Destination objects with market_id, name, destination_slug, state, country_code, country_name, num_discoverable_homes, num_sold_homes, avg_share_price, top_amenities, and active status"
},
"sample": {
"data": {
"total": 62,
"destinations": [
{
"name": "Lake Tahoe",
"state": "California",
"active": true,
"market_id": 2,
"country_code": "USA",
"country_name": "United States",
"top_amenities": [
"Hot tub",
"Kitchen island",
"Fireplace"
],
"num_sold_homes": 5,
"share_interest": "EIGHTH",
"starting_price": null,
"avg_share_price": 500500,
"destination_slug": "lake_tahoe_ca",
"num_discoverable_homes": 24,
"avg_share_price_currency": "USD"
}
]
},
"status": "success"
}
}About the Pacaso API
Endpoints Overview
The API covers three operations. list_destinations returns every active Pacaso market with its market_id, destination_slug, state, country_code, and num_discoverable_homes — useful for enumerating available regions before querying listings. get_listings accepts an optional destination string and an optional count integer, and returns an array of listing objects that include listing_id, pacaso_home_id, name, description, price_per_share, bedrooms, bathrooms, square_feet, location, amenities, and photos. When no destination filter is applied, results span all active markets and a destinations_queried array is included in the response.
Listing Detail
get_listing_detail takes a required home_id (UUID format, obtainable from get_listings) and an optional destination hint to narrow the lookup. The response includes a full photos array with url, type, title, description, width, height, and sort_order fields, a structured location object with street, city, state_or_province, postal_code, lat, and lng, and separate amenities and highlights arrays covering property-specific features and selling points.
Data Scope
All listings represent co-ownership (fractional) properties — price_per_share reflects the cost of one ownership share, not the full property value. Destinations include both US markets (e.g., Napa Valley, Aspen) and international markets (e.g., Paris, Los Cabos). The country_code and country_name fields on destination objects let you segment by geography without parsing freeform strings.
The Pacaso API is a managed, monitored endpoint for pacaso.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when pacaso.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 pacaso.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 co-ownership property search tool filtered by destination, bedroom count, and share price.
- Track average share prices across Pacaso markets over time using
list_destinationsandget_listings. - Populate a real estate investment dashboard with fractional property data including
square_feetandprice_per_share. - Generate destination-specific landing pages using
num_discoverable_homesand top amenities fromlist_destinations. - Compare property highlights and amenities across markets by querying
get_listing_detailfor eachpacaso_home_id. - Feed a travel or second-home planning app with Pacaso listings filtered to international markets using
country_code. - Build an alert system that detects new listings by diffing
listing_idsets returned by repeatedget_listingscalls.
| 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 Pacaso have an official public developer API?+
What does `get_listings` return when no destination filter is applied?+
get_listings without a destination parameter returns deduplicated listings across all active Pacaso markets. The response includes a destinations_queried array listing every market that was searched, and the total field reflects the combined count. You can narrow results by passing a destination string such as 'Aspen' or 'Los Cabos', and optionally cap the result set with the count parameter.Does the API expose historical pricing or sold/closed listings?+
price_per_share values. Historical transaction data and sold listings are not part of the response shape. You can fork this API on Parse and revise it to add an endpoint targeting historical or off-market records if Pacaso surfaces that data.How do I get the full photo set for a property?+
get_listing_detail returns the complete photos array for a property, including each photo's url, type, title, description, width, height, and sort_order. The home_id parameter (UUID format) is required and can be obtained from the pacaso_home_id field in any get_listings response. Passing the optional destination parameter speeds up the lookup.Does the API support filtering by bedrooms, bathrooms, or square footage?+
get_listings supports filtering only by destination and count. The response does include bedrooms, bathrooms, and square_feet fields on each listing object, so client-side filtering is straightforward. You can fork this API on Parse and revise it to add server-side numeric filters as additional input parameters.