Find leads · Use case

How do I find bank-owned and auction properties in an area?

Use the bank and auction boolean filters. Search the property graph with POST /api/v2/properties/search (bank or auction true plus location_ids) with a Casafari client account (the self-serve Property Sourcing search has no bank or auction filter); Casafari client accounts can also query alerts with POST /api/v1/listing-alerts/search. For price context, the self-serve Area Insights tool area-insights_get_price_distribution accepts the same flags, so you can compare against the whole market.

Products: Property Sourcing, New Market Leads, Area Insights, Comparables & Valuation

#Short answer

bank and auction are boolean filters in three places:

• POST /api/v2/properties/search returns bank properties or auction properties.
• POST /api/v1/listing-alerts/search returns alerts from them.
• Every Area Insights data tool accepts both. There, bank means the property is owned by the bank and auction means it is the subject of an auction.

On the Area Insights tools, auction defaults to false, so state it explicitly.

#Steps

#Search: POST /api/v2/properties/search with bank or auction true and location_ids

1. With a Casafari client account (the self-serve Property Sourcing search has no bank or auction filter): send location_ids for your area, bank: true (or auction: true), types and search_operations. Each result is one property with its price and status history.

#Alerts: POST /api/v1/listing-alerts/search with bank or auction, or a feed

2. Casafari client accounts: send location_ids, bank or auction true, alert_date_from and alert_date_to. You get new bank or auction properties, price cuts and status changes as alerts.
3. Self-serve: create a feed with POST /alerts-api/feeds and a webhook with PUT /alerts-api/webhooks. filters accepts bank and auction booleans, which combine with alert_subtypes, next to the required business_type. Set the webhook before the first feed: without one, creating a feed answers 409 with No webhook configured. See the Create feed page for the other keys.

#Context: area-insights_get_price_distribution twice, with bank true and without, on the same boundary

4. Self-serve over MCP: resolve the area with locations_search (English place names).
5. Call area-insights_get_price_distribution with custom_location_boundary.location_ids, type_group, business_type and bank: true.
6. Call it again with exactly the same inputs but bank left unset.

#Example: bank-owned apartments in Alicante

Ask an assistant connected to Casafari's MCP servers: "How do bank-owned apartment prices in Alicante compare with the market?" It calls:

1. locations_search with location_name "Alicante". Several matches can come back; administrative_level and breadcrumbs tell them apart, so pick the city.
2. area-insights_get_price_distribution with:

{
  "request_data": {
    "type_group": "apartment",
    "business_type": "sale",
    "custom_location_boundary": { "location_ids": [<ALICANTE_LOCATION_ID>] },
    "bank": true,
    "exclude_outliers": false
  }
}

3. The same call without bank.

exclude_outliers is set to false in both runs. Its default (true) drops significantly underpriced properties, which are exactly what you are looking for.

The properties themselves then come from POST /api/v2/properties/search, with a Casafari client account (the self-serve Property Sourcing search has no bank or auction filter):

{
  "search_operations": ["sale"],
  "location_ids": [<ALICANTE_LOCATION_ID>],
  "types": ["apartment"],
  "bank": true
}

The accepted values for search_operations are on the Search properties (v2) page.

#How to read the result

#If both bank and auction are set, the result combines both (as the field notes say)

On POST /api/v2/properties/search, the notes on bank and auction say that if the other filter is also set, the result combines both. To tell bank stock from auction stock, run them separately. The exact wording is on the operation page.

#Compare price bands against the general market

Each band of area-insights_get_price_distribution has lower_bound, upper_bound, properties_count and is_mean, which marks the band holding the mean.

Turn counts into shares of each run's total and compare the two shapes. If the bank run's mean band sits below the market's, bank stock in that area is priced lower.

To check a single property against its neighbours, run comparables_get_comparables and compare its price with fair_market_price.

#Limits

#Flags come from the advertisement data in the graph

bank and auction reflect how properties are advertised in the sources the graph collects. They do not prove legal ownership, auction terms or charges on the property. Check those before you bid.

#Not available over MCP except the Area Insights context

/alerts-api/feeds and the Area Insights tools are self-serve on the Casafari API and MCP Platform and stay available to Casafari clients. The property search (POST /api/v2/properties/search) is available to Casafari clients over REST; the self-serve Property Sourcing search has no bank or auction filter. POST /api/v1/listing-alerts/search is for Casafari client accounts.

The Area Insights tools name no specific market in their descriptions. The property graph is built from sources in 16 countries. No refresh frequency, quotas or prices are published; ask Casafari.

#Questions

All use cases