Indian Property Listings Finder by City & BHK: MCP config, n8n workflow and API

{
  "mode": "searchForSale",
  "city": "Mumbai",
  "propertyType": "Apartment",
  "bedrooms": "Any",
  "furnishing": "Any",
  "possessionStatus": "Any",
  "postedSince": "Any",
  "tenantType": "Any",
  "sortBy": "Relevance",
  "maxItems": 3,
  "includeDetails": false
}

---
name: indian-property-listings-finder-by-city-and-bhk
description: "MagicBricks property listings with price, area, BHK, project, RERA, seller, amenities, images and listing URLs. Runs the Apify Actor dataspryva/indian-property-listings-finder-by-city-and-bhk. Use when the user needs Indian Property data with fields such as propertyId, title, price, priceInr, area, bedrooms and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/indian-property-listings-finder-by-city-and-bhk"
  store-url: "https://apify.com/dataspryva/indian-property-listings-finder-by-city-and-bhk"
---

# Indian Property Listings Finder by City & BHK

Use this skill to fetch Indian Property data with the Apify Actor `dataspryva/indian-property-listings-finder-by-city-and-bhk` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `searchForSale`, `searchForRent`, `searchProperties`, `bySearchUrl`, `byPropertyUrl`, required | What to collect. Search by city and filters, paste MagicBricks search-result URLs, or paste property-detail URLs. |
| `startUrls` | array | MagicBricks search-result or property-detail links (mode=bySearchUrl or byPropertyUrl). |
| `city` | string | Indian city to search (mode=searchForSale, searchForRent, searchProperties). |
| `propertyType` | string | Type of property to search (mode=searchForSale, searchForRent, searchProperties). |
| `bedrooms` | one of `Any`, `1`, `2`, `3`, `4`, `5+` | Bedroom count. 5+ is sent as 5, the site's maximum (mode=searchForSale, searchForRent, searchProperties). |
| `furnishing` | one of `Any`, `Furnished`, `Semi-Furnished`, `Unfurnished` | Furnishing state filter (mode=searchForSale, searchForRent, searchProperties). |
| `possessionStatus` | one of `Any`, `Ready to Move`, `Under Construction` | Ready-to-move or under-construction filter (mode=searchForSale, searchProperties). |
| `postedSince` | one of `Any`, `1` | Only listings posted in the last 24 hours (mode=searchForSale, searchForRent, searchProperties). MagicBricks does not expose wider server-side posting windows. |
| `tenantType` | one of `Any`, `Bachelors`, `Family` | Who the landlord accepts (mode=searchForRent and rent searches in searchProperties). MagicBricks exposes Bachelors and Family server-side. |
| `sortBy` | one of `Relevance`, `Price - Low to High`, `Price - High to Low`, `Most Recent`, `Rate/sqft - Low to High`, `Rate/sqft - High to Low` | Order of search results (mode=searchForSale, searchForRent, searchProperties). |
| `maxItems` | integer | Hard cap on the number of property records returned. |
| `includeDetails` | boolean | Also open each listing's detail page for project, developer, RERA, full address, GPS, amenities, deposit and maintenance data (search modes). |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "searchForSale",
  "city": "Mumbai",
  "propertyType": "Apartment",
  "bedrooms": "Any",
  "furnishing": "Any",
  "possessionStatus": "Any",
  "postedSince": "Any",
  "tenantType": "Any",
  "sortBy": "Relevance",
  "maxItems": 3,
  "includeDetails": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~indian-property-listings-finder-by-city-and-bhk/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~indian-property-listings-finder-by-city-and-bhk/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `propertyId`, `title`, `price`, `priceInr`, `area`, `bedrooms`, `propertyType`, `transactionType`, `city`, `locality`, `projectName`, `reraIds`, `propertyUrl`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.