High Potential Seller Leads: frequently asked questions

Call GET /v1/seller-leads with the address's lat and lon, a radius_m between 50 and 300 metres and min_price_cuts=2 to list the homes in that circle whose asking price was cut at least twice.

Each lead has price_cuts.count, price_cuts.percentage, price_cuts_since and a property_id readable with Property Sourcing. By default a lead needs at least one cut adding up to at least 5 percent over the home's whole time on the market; raise min_price_cuts and min_price_cut_pct to tighten the list. Multiple price reductions are a stronger motivated-seller signal than a single one, according to Greg Powell Homes. A page of leads costs 100 units. See List seller leads.

Call GET /v1/seller-leads with your office's lat and lon, radius_m=300 and min_price_cut_pct=10 to list homes within 300 metres whose price cuts add up to at least 10 percent.

The radius runs from 50 to 300 metres (default 300) and the search is always around a point, so geocode your office or a street corner; for a larger territory, run several points. Add types, price_min and price_max to stay in your niche and since to count only recent cuts. See List seller leads and the use case Street-level mandate prospecting list.

Add since=YYYY-MM-DD, set to the first day of the year, to GET /v1/seller-leads, and only price cuts made since that date count towards min_price_cuts and min_price_cut_pct.

Without since, cuts are counted over the home's whole time on the market, so a home reduced long ago but not recently can still appear. Each lead reports price_cuts_since, showing which window produced its numbers. Re-running the query with a rolling date catches newly reduced homes; see Weekly newly-motivated homes alert for an office and List seller leads.

Yes: GET /v1/seller-leads/{lead_id} returns the lead's property, with the same fields as a Property Sourcing property read, together with its dated price and status history, for 10 units.

The history belongs to one deduplicated property record, however many agencies advertise the home. You can also read the property through its property_id with GET /v1/property-sourcing/properties/{property_id}?expand=listings,history to see every place it is advertised as well. See Get a seller lead and Get a property.

No: High Potential Seller Leads returns no owner names, phone numbers or emails; it identifies properties and their price behaviour, and contacting owners is up to you and your local law.

In the EU, prospecting calls need a lawful basis under GDPR and must also comply with the ePrivacy Directive and national telemarketing law, and a privacy notice is owed within one month when data was not obtained from the person, according to Tomba. In Spain, commercial calls need prior consent or another GDPR Article 6.1 basis since 29 June 2023, according to Maldita.es; in Germany, telephone advertising to consumers needs express consent under section 7(2) no. 1 UWG, according to marken.legal; in France, estate agents need prior opt-in consent before a prospecting call from 11 August 2026, according to MaFormationImmo. See the Seller Leads hub.

High Potential Seller Leads covers Spain, France, Italy, Germany, Greece and Andorra.

Portugal and the other countries available in Property Sourcing are not covered by Seller Leads. For an area there, search Property Sourcing with sort: recently_updated and read each candidate with expand=history to see its dated price changes. See List seller leads.

Yes: types limits leads to the property types you name, and price_min and price_max keep them inside a price band, alongside operation (sale or rent) and the price-cut filters min_price_cuts, min_price_cut_pct and since.

This keeps a prospect list inside an agent's or investor's niche, for example apartments within a price band that were cut at least twice. Each page of leads costs 100 units. See List seller leads.

Yes: pass operation=rent to GET /v1/seller-leads and the same price-cut rules apply to asking rents within 50 to 300 metres of a point: at least min_price_cuts reductions adding up to at least min_price_cut_pct percent, optionally since a date.

Letting agents can use this to spot rentals with repeated reductions, and landlords to see which nearby rentals keep lowering their rent before setting their own. See the use case Rent-cut radar for letting agents and landlords and List seller leads.

Every lead carries a property_id (prop_…), the id of the same property record that Property Sourcing returns, so you can read it with GET /v1/property-sourcing/properties/{property_id}.

That read gives areas, energy rating, condition and address, and with expand=listings,history every place the home is advertised and its dated changes. The lead itself (lead_…) has coordinates, price_cuts {count, percentage} and price_cuts_since; GET /v1/seller-leads/{lead_id} returns the property and its history in one call for 10 units. See Get a seller lead, Get a property and how the property graph is built.

The documentation does not set a refresh frequency, so re-run as often as your territory and credits justify; a weekly run with since set to the previous run's date catches the cuts made in between.

Each page of leads costs 100 units; Free includes 1,000 units for 30 days and allows 10 distinct places a day, while pay as you go and Agent allow 50. Compare the lead_… ids with your last run to find new leads. For alert feeds of price cuts, reservations, withdrawals and sales, see Alerts. Reference: List seller leads.

Yes: High Potential Seller Leads is self-serve on Free, pay as you go and Agent, with the same guards as Property Sourcing.

Free gives 1,000 units for 30 days, 10 distinct places a day, 10 requests a minute and 2 concurrent requests. Pay as you go and Agent (EUR 70 a month) allow 50 distinct places a day, 20 requests a minute and 3 concurrent requests; a new pay-as-you-go account keeps Free's guards until its business is verified or its first credit purchase is 7 days old. Credits are bought from EUR 20, at EUR 0.04 a unit; a page of leads is 100 units and a lead detail 10. See the REST overview.

Authenticate with a platform API key (cf_sk_…) or an OAuth access token, sent as Authorization: Bearer $CASAFARI_API_KEY or X-API-Key; limits depend on the plan, from 10 requests a minute and 2 concurrent on Free to 20 a minute and 3 concurrent on pay as you go and Agent.

Create keys in the console at https://platform.casafari.com/console. A daily guard also limits distinct places queried: 10 on Free, 50 on pay as you go and Agent. The same key works for Seller Leads and Property Sourcing. See Platform API keys.

You get an RFC 9457 problem+json error: 402 payment_required with an upgrade_url when credits run out, or 429 request_limit_reached naming the window when you exceed a guard.

Design clients and agents to wait for the named window on 429 and to show the upgrade_url to a human on 402. On Free, the 1,000 units are valid for 30 days. See the REST overview.

Yes: every hub page is available as Markdown (.md), /llms.txt is provided for language models, and /openapi.json describes the REST operations, including seller leads and property sourcing.

Point a coding agent at /openapi.json for request and response schemas and at /llms.txt for the documentation; the reference pages List seller leads and Get a seller lead are available as .md too. Both products are REST only, with no MCP tools.