# Qatar Living Scraper (`dadhalfdev/qatarliving-scraper`) Actor

Scrape Qatar Living property listings from public pages. Use filters or paste a Qatar Living URL — the URL wins when set. Returns price (QAR), beds, location, and photos.

- **URL**: https://apify.com/dadhalfdev/qatarliving-scraper.md
- **Developed by:** [Marco Rodrigues](https://apify.com/dadhalfdev) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 🇶🇦 Qatar Living Scraper

Want [Qatar Living](https://www.qatarliving.com/en/properties/residential?purpose=For+Rent) property listings in a spreadsheet? This scraper makes it easy.

Use **structured filters** (purpose, residential/commercial, type, location) — structured filters work better for AI agents — **or** paste an **`input_url`** from Qatar Living once you've already filtered in the browser. When `input_url` is set it overrides the filters below.

Qatar Living only publishes about **10 cards on each public page** (the rest of search is client-side). This actor fans out across those public city/area URLs and returns up to 2000 unique rows per run.

### 💡 Perfect for...

- **Agents and relocators:** Export Doha, Lusail, The Pearl, and other Qatar rent or sale ads with QAR asking prices.
- **Dashboards:** Track residential and commercial inventory from public QL pages.
- **Market research:** Slice by apartments, villas, offices, or warehouses.
- **Data analysts:** Export structured listing rows with public Qatar Living URLs.
- **🤖 AI Agents:** Power Claude, Cursor, Codex, the Hermes Agent, and OpenClaw workflows with live Qatar Living results.
- **📚 RAG Systems:** Feed titles, locations, and prices into retrieval pipelines.
- **🔗 AI Workflows:** Plug into LangChain, AutoGPT, CrewAI, and similar stacks.

### ✨ Why you'll love this scraper

- 🔗 **Input URL or Filters:** Paste a Qatar Living properties or listing URL (`input_url`) if you already filtered in the browser, or use structured filters (better for AI agents). `input_url` always wins when set.
- 🎯 **Website-Matched Filters:** Same purpose, residential/commercial, type, and area slugs as qatarliving.com.
- 🌐 **Public pages only:** Reads the JSON-LD already on each search/area page — no login API.

### 📦 What's inside the data?

Every row includes all of these fields:

- **Core:** `id`, `url`, `title`, `purpose`, `kind`, `property_type`, `slug`
- **Price:** `price`, `currency` (QAR)
- **Place / specs:** `location`, `city`, `country`, `street`, `bedrooms`, `bathrooms`
- **Media / agency:** `image_url`, `image_urls`, `agency`, `description`

### 🚀 Quick start

**Option A — Input URL**

1. Open [Residential for rent](https://www.qatarliving.com/en/properties/residential?purpose=For+Rent), apply filters, copy the URL — e.g. `https://www.qatarliving.com/en/properties/residential/rent/doha/apartments-for-rent-doha`.
2. Paste it into `input_url`.
3. Set `max_results` and click **Start**.

**Option B — Structured filters (better for AI agents)**

1. Leave `input_url` empty.
2. Pick Rent/Sale, residential or commercial, optional type and location.
3. Set `max_results` (up to 2000) and click **Start**.

***

#### Tech details for developers 🧑‍💻

**Input Example (filters):**

```json
{
  "purpose": "rent",
  "kind": "residential",
  "property_type": "apartments",
  "location": "doha",
  "max_results": 100
}
```

**Input Example (URL override):**

```json
{
  "input_url": "https://www.qatarliving.com/en/properties/residential?purpose=For+Rent",
  "max_results": 50
}
```

**Output Example:**

```json
{
  "id": "115774",
  "url": "https://www.qatarliving.com/en/properties/rent/residential/apartment/furnished_1bhk_available_in_doha_jadeed_including_bills/115774",
  "title": "FURNISHED 1BHK AVAILABLE IN DOHA JADEED INCLUDING BILLS",
  "purpose": "rent",
  "kind": "residential",
  "property_type": "apartment",
  "price": 3700,
  "currency": "QAR",
  "location": "Al Doha Al Jadeeda",
  "city": "Doha",
  "country": "QA",
  "street": "15, Al Doha Al Jadeeda, Doha",
  "bedrooms": 1,
  "bathrooms": 1,
  "image_url": "https://qlp-media-prod.qatarliving.com//prod/115774/....jpeg",
  "image_urls": ["https://qlp-media-prod.qatarliving.com//prod/115774/....jpeg"],
  "agency": null,
  "description": null,
  "slug": "furnished_1bhk_available_in_doha_jadeed_including_bills"
}
```

**Output fields:**

| Field | Description |
|-------|-------------|
| `id` | Qatar Living numeric listing id. |
| `url` | Public listing page. |
| `title` | Listing headline. |
| `purpose` | `rent` or `sale`. |
| `kind` | `residential` or `commercial`. |
| `property_type` | Type slug or schema type, e.g. `apartment`. |
| `price` | Asking price as a number. |
| `currency` | Usually `QAR`. |
| `location` | Area / region from the card. |
| `city` | City, usually Doha. |
| `country` | Country code, usually `QA`. |
| `street` | Street line when published. |
| `bedrooms` | Bedroom count. |
| `bathrooms` | Bathroom count. |
| `image_url` | First photo. |
| `image_urls` | Photo URLs from the card. |
| `agency` | Agency name when the page publishes it. |
| `description` | Short description when present (detail URLs). |
| `slug` | URL slug for the listing. |

### 📋 Input reference (detailed)

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `input_url` | string | No | — | Paste a properties search, area, or listing URL; overrides filters when set. |
| `purpose` | string enum | No | `rent` | `rent` or `sale`. |
| `kind` | string enum | No | `residential` | `residential`, `commercial`, or `all`. |
| `property_type` | string enum | No | all | `apartments`, `villas`, `offices`, `warehouses`, or all types. |
| `location` | string enum | No | all | `doha`, `lusail`, `al-wakra`, `al-khor`, `al-rayyan`, `umm-salal`, `al-daayen`, `the-pearl`, `west-bay`, `al-sadd`, `old-airport`, or all Qatar. |
| `max_results` | integer | No | `50` | Maximum rows (`1`–`2000`). |

#### Notes on filters

- Prefer exact enum strings from the Apify input dropdowns (same slugs as Qatar Living URLs).
- `input_url` always wins over filters when provided.
- `www.qatarliving.com` and `qatarliving.com` URLs are both accepted.
- Default purpose is **rent** and default group is **residential**.
- Each public page only exposes about 10 listings. The actor follows more area URLs from those pages to fill `max_results`.

# Actor input Schema

## `input_url` (type: `string`):

Paste a Qatar Living properties URL (e.g. https://www.qatarliving.com/en/properties/residential?purpose=For+Rent or an area/listing page). Overrides every filter when set.

## `purpose` (type: `string`):

Same Rent / Sale switch as on qatarliving.com properties. Ignored when input\_url is set.

## `kind` (type: `string`):

Residential, commercial, or both — same groups as the Qatar Living properties home. Ignored when input\_url is set.

## `property_type` (type: `string`):

Same type idea as QL area URLs (apartments, villas, offices, warehouses). Ignored when input\_url is set.

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

Same city / area slugs as qatarliving.com pretty URLs. Ignored when input\_url is set.

## `max_results` (type: `integer`):

How many rows to return (1–2000). QL only publishes about 10 cards per public page, so the actor fans out across area URLs.

## Actor input object example

```json
{
  "purpose": "rent",
  "kind": "residential",
  "property_type": "",
  "location": "",
  "max_results": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

Table view of scraped properties using the dataset 'overview' view.

## `results` (type: `string`):

All scraped listings from the default dataset without view transformation.

# 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("dadhalfdev/qatarliving-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("dadhalfdev/qatarliving-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 dadhalfdev/qatarliving-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dadhalfdev/qatarliving-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/K5OnzrXOr6yl6TGdY/builds/UifjeaGPGhJRDCSqG/openapi.json