Daft.ie Scraper — Irish Property Listings | $1.50/1K | No Login

For Irish property investors, estate agents, and housing analysts who need structured data from Daft.ie — Ireland's largest portal with 4,000+ Dublin listings alone and 95%+ national market share.

$1.50 per 1,000 listings. Agent contact and BER rating available as premium events.

Scrape Irish property listings from daft.ie — Ireland's largest property portal with 4,000+ active listings in Dublin alone.

What it does

Extracts structured listing data from any Daft.ie search URL (for sale or to rent):

• Price (display string + numeric EUR)
• Address (full title, city, county)
• Bedrooms & bathrooms
• Property type (Semi-D, Apartment, Terrace, etc.)
• BER rating (Building Energy Rating A1–G)
• Coordinates (lat/lng for map plotting)
• Agent (name, ID, phone)
• Images (all photo URLs + main image)
• Listing date
• parse_confidence — quality score per listing

How to use

1. Go to daft.ie and run your property search.
2. Copy the full search URL from your browser.
3. Paste it into the searchUrl input field.
4. Set maxItems to control how many listings to fetch.

Example input

{
  "searchUrl": "https://www.daft.ie/property-for-sale/dublin",
  "maxItems": 200
}

Output schema

Field	Type	Description
listing_id	integer	Daft listing ID
title	string	Full address / title
price	string	Display price (e.g. "€975,000")
price_numeric	integer	Numeric price in EUR
currency	string	"EUR"
address	string	Full address
city	string	City/town (derived)
county	string	Irish county (derived)
ber_rating	string	Energy rating (A1–G)
bedrooms	integer	Number of bedrooms
bathrooms	integer	Number of bathrooms
property_type	string	Semi-D, Apartment, etc.
floor_area_m2	float	Floor area in m²
lat	float	Latitude
lng	float	Longitude
agent_name	string	Agent/agency name
agent_id	integer	Daft agent ID
agent_phone	string	Contact phone
url	string	Daft.ie listing URL
image_url	string	Main image URL
images	array	All image URLs
date_listed	string	ISO 8601 listing date
sale_type	string	"For Sale" / "To Let"
listing_type	string	sale / rent
scraped_at	string	ISO 8601 UTC scrape time
parse_confidence	float	Data quality score (0–1)
warnings	array	Quality warning codes

Output sample

{
  "listing_id": 2142857,
  "title": "44 The Stiles Road, Clontarf, Dublin 3",
  "price": "€975,000",
  "price_numeric": 975000,
  "currency": "EUR",
  "city": "Clontarf",
  "county": "Dublin 3",
  "ber_rating": "B2",
  "bedrooms": 4,
  "bathrooms": 2,
  "property_type": "Semi-D",
  "floor_area_m2": 148.0,
  "lat": 53.3682,
  "lng": -6.2019,
  "agent_name": "Sherry FitzGerald",
  "agent_phone": "01 833 6633",
  "url": "https://www.daft.ie/for-sale/semi-detached-house-44-the-stiles-road-clontarf-dublin-3/2142857",
  "parse_confidence": 1.0,
  "warnings": []
}

Pricing example

Run size	Cost
100 listings	~$0.15
1,000 listings	~$1.50
10,000 listings	~$15.00
+ agent phone	+$1.00/1K
+ BER rating data	+$0.50/1K

FAQ

Do I need a Daft.ie account or proxy? No account, no proxy. Agent phone numbers are extracted without authentication.

What output formats are available? JSON, CSV, Excel, XML — all via Apify dataset download or API.

Can I scrape rentals as well as sales? Yes — paste any Daft.ie search URL. Both /property-for-sale/ and /property-for-rent/ URLs work.

What if it returns empty results? Check that your searchUrl is a valid Daft.ie search URL (e.g. https://www.daft.ie/property-for-sale/dublin). The actor logs the issue and exits cleanly with 0 results rather than crashing.

Why this actor vs. competitors

Feature	This actor	epctex/daft-scraper ($3/1K)	Typical Daft.ie scraper
BER rating (A1–G)	Yes	No	Rarely
Agent phone extracted	Yes	No	No
County field (Irish admin)	Yes	No	Rarely
parse_confidence + warnings	Yes	No	No
Source: __NEXT_DATA__ JSON	Yes (stable)	DOM	Usually DOM
No login required	Yes	Yes	Often requires account
Price per 1K listings	$1.50	$3.00	varies

No Login — Daft.ie pushes users toward account creation for agent contacts. This actor extracts agent_phone without any account or authentication.

BER compliance: BER (Building Energy Rating) is a legally required disclosure in all Irish property sales — making this field essential for compliance monitoring and green finance applications.

parse_confidence

Every listing includes a parse_confidence score (0–1). Score < 0.8 means one or more critical fields are missing — check the warnings array before relying on those records.

Use with AI agents (MCP)

Tag: MCP_SERVERS. Returns clean JSON — drop into any n8n / Make / LangChain workflow without post-processing.

{
  "mcpServer": "https://mcp.apify.com/?tools=bovi/daft-listings"
}

Technical notes

• Data source: Daft.ie's __NEXT_DATA__ embedded JSON (reliable SSR data)
• No proxy required from Apify cloud IPs
• Pagination handled automatically (20 listings/page)

Pricing

Pay-Per-Event (PPE):

Event	Price
listing-item (primary)	$1.50 / 1,000 listings
agent-contact (premium)	$1.00 / 1,000 phones extracted
ber-rating-data (premium)	$0.50 / 1,000 BER-rated listings

Agent phone and BER rating each fire their respective premium event only when the data is present. You pay nothing extra for listings where these fields are absent.

Integrations

Built for Irish property investors, estate agents, and housing analysts tracking listings and pricing across Ireland's largest portal — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Disclaimer

This actor is not affiliated with Daft.ie. Use in accordance with Daft.ie's Terms of Service.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.