Properstar

Properstar at a glance

Properstar is a ready-to-run Apify actor from abotapi for collecting real estate data. Its documented output includes id, change type (incremental mode), url, deal and type, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $3.00 per 1,000 results on the Apify Free plan and from $1.50 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Real Estate, Developer Tools, Automation
Pricing: $3.00 per 1,000 results (Free plan), from $1.50 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 20 options

Extract property listings from Properstar across global domains like .com.co.uk.ch, and .fr. Use search pages, listing URLs, or agency pages. Returns prices, multilingual descriptions, photos, floor plans, GPS coordinates, and agency details via Properstar’s data service.

What Properstar can do

Any Properstar country domain, auto-detected from the URL you paste, no domain allowlist to work around.
Three input shapes in one actor: search-results pages, single listing pages, and agency or agent pages.
Multilingual titles and descriptions captured per language, not just one.
50+ named fields per listing, plus the complete source object so nothing is lost.
Optional full detail mode adds amenities, AI-extracted view types, construction year, and floor to search and agency results (listing-page URLs always include these).
Full measurements: living and land area in both square metres and square feet, alongside rooms, bedrooms, bathrooms, and energy/CO2 ratings.

Choose what to collect

These inputs let you configure Properstar - Global Property Listings, URLs & Agency Data. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`startUrls`array · required	Paste Properstar URLs from any country domain (.com.co.uk.ch.fr...). Supported: search result pages (e.g. /united-kingdom/london/buy/apartment-house), single listing pages (/listing/{id}), and agency or agent pages (/agency/{slug}/{id}). Multiple URLs are processed in order. The filter fields below refine search-page URLs. Leave this field untouched to work through 10 example URLs (one per supported URL shape) in order until Max listings is reached; with the default Max listings only the first search is usually reached. Replace or clear the list to scrape only your own URLs. A page number (?p=2) starts the walk at that page, and price and bedrooms options are applied as filters. A ?sort= option in a pasted URL is ignored.
`transactionType`string	Refine search-page URLs to buy or rent. 'Any' keeps the URL's own setting. Choices: any, buy, rent
`propertyTypes`array	Restrict to these property types. Leave empty to use the URL's own types.
`minPrice`integer	Minimum price. The site compares euro-equivalent prices, so listings priced in another currency can sit slightly outside the range.
`maxPrice`integer	Maximum price. The site compares euro-equivalent prices, so listings priced in another currency can sit slightly outside the range.
`minBedrooms`integer	Minimum number of bedrooms.
`maxBedrooms`integer	Maximum number of bedrooms.

Show 13 more inputs

More input fields
Input	What it controls
`luxuryOnly`boolean	Return only listings flagged as luxury.
`enrichDetail`boolean	Fetch each listing's detail page for amenities, AI-extracted views, construction year and floor. Slower and adds a per-listing surcharge. Listing-page URLs always include full detail.
`maxItems`integer	Maximum listings to return across all URLs. Set 0 for unlimited.
`maxPagesPerUrl`integer	Maximum result pages to walk per search/agency URL (25 listings per page). Leave empty to walk every result page (the walk still stops at the site's own ~2000-listing retrievable ceiling).
`resumeFromRunId`string	Paste a previous run ID or dataset ID to continue a full-catalogue walk across separate runs. Listings already collected there (matched by listing id) are skipped, so this run only saves the new ones. Leave empty for a normal fresh run. For recurring daily/weekly monitoring of the same URLs, use Incremental mode below instead.
`incrementalMode`boolean	Turn this on for daily or recurring monitoring of the same startUrls/filters. The first run returns every matching listing as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED listings. Turn on "Emit unchanged" or "Emit expired" only when you also want those listings returned (and billed). State is kept separately per distinct startUrls/filters/enrichDetail setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.
`stateKey`string	Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from startUrls, the filter fields, and enrichDetail, different searches then never mix state with each other.
`emitUnchanged`boolean	Off by default. Turn on to also return listings that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want the full snapshot every run.
`emitExpired`boolean	Off by default. Turn on to also return listings that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked startUrls, not when Max listings capped it, when Resume was used, when a start URL carries a page number (?p=N), or when a page/connection was rejected mid-scan. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking.
`ignoreFieldsForChanges`array	Incremental mode only. Field names that must NOT count as a change, so a listing is not reported UPDATED just because one of them moved. Use top-level names (for example "description") or dotted paths into nested objects (for example "agencyStatistics.listingCount"). Matching is exact on the whole name. Ignored fields are still returned in every row; they only stop being compared and stop appearing in changedFields. The full source payload raw is always ignored for change detection.
`mcpConnectors`array	Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON, the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
`notionParentPageUrl`string	URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idID

changeTypeChange type (incremental mode)

urlURL

transactionTypeDeal

typeType

titleTitle

pricePrice

currencyCurrency

bedroomsBeds

bathroomsBaths

roomsRooms

livingAreaSqmLiving m²

Show 17 more fields

cityCity

postcodePostcode

countryISOCountry

latitudeLat

longitudeLng

picturesCountPhotos

energyRatingEnergy

statusStatus

agencyNameAgency

publicationDatePublished

changedFieldsChanged fields (incremental mode)

firstSeenAtFirst seen (incremental mode)

lastSeenAtLast seen (incremental mode)

amenitiesAmenities

floorFloor

constructionYearBuilt

descriptionDescription

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "id": "100000001",
  "url": "https://www.properstar.co.uk/listing/100000001",
  "class": "PropertyListing",
  "transactionType": "Sell",
  "type": "Apartment",
  "subType": "Penthouse",
  "title": "Sample listing title",
  "description": "Full description text appears here.",
  "titleByLanguage": {
    "en": "Sample listing title"
  },
  "descriptionByLanguage": {
    "en": "Full description text appears here."
  },
  "price": 1000000,
  "currency": "GBP",
  "livingAreaSqm": 120,
  "livingAreaSqft": 1291,
  "rooms": 4,
  "bedrooms": 3,
  "bathrooms": 2,
  "floor": "3",
  "constructionYear": 2020,
  "address": "Sample Street 1",
  "city": "London",
  "postcode": "SW1",
  "countryISO": "GB",
  "latitude": 51.5,
  "longitude": -0.12,
  "pictures": [
    "https://images.example.com/0001.jpg"
  ],
  "picturesCount": 12,
  "floorPlans": [
    "https://images.example.com/plan-0001.jpg"
  ],
  "amenities": [
    "Balcony",
    "Parking"
  ],
  "views": [
    "City"
  ],
  "agencyId": 1000000,
  "agencyName": "Sample Agency",
  "agencySlug": "sample-agency",
  "agencyStatistics": {
    "numberOfListings": 0
  },
  "publicationDate": "2026-01-01T00:00:00Z"
}

Ways to use this data

Real estate portals and PropTech tools: aggregate live listings across multiple country domains into one structured feed.
Investors and relocation agencies: compare prices, sizes, and locations across countries and currencies from a single search.
Market researchers and analysts: track price and inventory changes over time with incremental monitoring.
Lead generation and CRM tools: pull agency and agent contact details tied to their current live inventory.
Content and comparison sites: build country or city listing pages from live search results.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Properstar return?

The documented output for Properstar includes id, change type (incremental mode), url, deal, type, title, price and currency. Availability of each field depends on the source page and the selected mode.

How much does Properstar cost?

It costs $3.00 per 1,000 results on the Apify Free plan and from $1.50 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I monitor the same search for new or changed listings?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated, and reappeared listings, and unchanged ones are not billed unless you turn on Emit unchanged.

Why did my run return fewer listings than I expected?

Check Max listings and Max pages per URL, which both cap a run by design. A single search or agency URL is also capped at roughly the site's own 2000-listing retrievable ceiling. If you pass several overlapping URLs in one run, a later URL can also stop early once a whole page of it repeats listings an earlier URL already returned (see "Known limitation: overlapping URLs end early" under Caps and cost controls), and with Emit expired on, listings it skipped this way can come back as EXPIRED even though they are still live. Run overlapping areas or filters as separate runs to avoid both.

Why did my run fail instead of returning an empty dataset?

If every request to Properstar was rejected, the run fails with a clear message so "no listings match" is never confused with "the connection could not be established". Run it again in a few minutes. If only some of your URLs failed, you still get what was found from the others.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear, or Airtable.