# Daft.ie Properties and Details Scraper (`realestateapi/daft-ie-properties-and-details-scraper`) Actor

Permission-gated Daft.ie property listings. Current written authorization for automated retrieval and intended reuse is required; default runs make zero source requests.

- **URL**: https://apify.com/realestateapi/daft-ie-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Daft.ie Properties and Details Scraper

This permission-gated Actor (CSV rank 665; source Actor `igolaizola/daft-ie-scraper`) can parse official Daft.ie search and detail pages only when current written authorization covers automated retrieval and the intended reuse of listing data. Daft.ie’s current Terms of Use prohibit automated retrieval/database population in section 8 and scraping or commercial reuse without permission in section 27. No applicable written permission is recorded for this project, so the default run completes as `SUCCEEDED` / `SKIPPED_POLICY`, makes zero source requests, and writes no dataset rows.

The `authorizationConfirmed` input is an operator attestation only; it does not grant permission or verify an agreement. Leave it `false` unless the required written authorization is documented. Do not set it to `true` on the basis of this Actor’s code or this README.

When authorized, the Actor can return source-supported listing identity and URLs, transaction/category, prices and currency, bedrooms and bathrooms, property type and area, BER, features, publication dates, coordinates, descriptions, public seller details, public media URLs, and nearby schools and transit. Rich records group related data under `address`, `pricingDetails`, `propertyDetails`, `berDetails`, `sellerDetails`, `mediaDetails`, `publicationDetails`, and `nearbyAmenities`. Optional values are omitted when the page does not provide them. Failures are summarized in key-value storage and never written as dataset rows.

The preserved local dataset contains one historical, 68-field listing record. Its run summary is dated 2026-09-23; it is not a fresh current dataset. The 2026-09-27 Chrome comparison found the saved views counter had changed, and the row was preserved rather than overwritten. The saved summary is normalized to `SUCCEEDED` / `COMPLETED` for its one listing. See `BROWSER_REVIEW.md`.

### Run status

An actual request, parse, validation, or storage failure with zero saved listings is `FAILED` / `FAILED`. If at least one real listing is saved before a later failure, the run is `SUCCEEDED` / `PARTIAL`. A clean search, including one with no matches, is `SUCCEEDED` / `COMPLETED`; a clean bounded result set is also completed. A default rights-gated run is `SUCCEEDED` / `SKIPPED_POLICY`. The dataset and its schema contain real property rows only; diagnostics and placeholder rows are omitted.

### Local checks

Run `npm test`, `npm run check`, `npm run validate`, and `apify validate-schema` for offline verification. A default run writes only successful policy-skip summaries to key-value storage and must not contact Daft.ie. These checks do not qualify a current live scrape. Do not run the Actor against Daft.ie until written authorization is documented.

# Actor input Schema

## `authorizationConfirmed` (type: `boolean`):

Set to true only when current written permission explicitly covers automated retrieval and intended reuse of Daft.ie listing data. This operator attestation does not grant permission. Defaults to false and makes zero source requests.

## `mode` (type: `string`):

Search a public Daft.ie results page or fetch explicit listing URLs.

## `searchUrl` (type: `string`):

Optional public Daft.ie search URL. When omitted, location and transaction are used.

## `transaction` (type: `string`):

Public Daft.ie search family.

## `location` (type: `string`):

Daft.ie location path segment, for example ireland or dublin-city.

## `listingUrls` (type: `array`):

Explicit HTTPS Daft.ie listing URLs for listings mode.

## `startUrls` (type: `array`):

Alias for listing/search URLs; only Daft.ie HTTPS URLs are accepted.

## `maxItems` (type: `integer`):

Maximum property rows emitted.

## `maxPages` (type: `integer`):

Bounded page parameter for public results pages.

## `includeDetails` (type: `boolean`):

Fetch each listing page to enrich descriptions, facilities, BER, coordinates, and media.

## `maxDetailRequests` (type: `integer`):

Bound detail-page enrichment requests.

## `includeImages` (type: `boolean`):

Persist public Daft media URLs without downloading image bytes.

## `maxImages` (type: `integer`):

Maximum public image URLs retained per listing.

## `timeoutSecs` (type: `integer`):

Timeout for each public Daft.ie request.

## `userAgent` (type: `string`):

Optional transparent HTTP user-agent string.

## Actor input object example

```json
{
  "authorizationConfirmed": false,
  "mode": "search",
  "searchUrl": "",
  "transaction": "sale",
  "location": "ireland",
  "listingUrls": [],
  "startUrls": [],
  "maxItems": 20,
  "maxPages": 1,
  "includeDetails": true,
  "maxDetailRequests": 20,
  "includeImages": true,
  "maxImages": 12,
  "timeoutSecs": 30,
  "userAgent": ""
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/daft-ie-properties-and-details-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/daft-ie-properties-and-details-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call realestateapi/daft-ie-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/daft-ie-properties-and-details-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KyjXQyNg6xpZCH7TC/builds/7fSBQlRxPkBZYjIYA/openapi.json