NoBroker Property Scraper — India Real Estate

Collect property listings from NoBroker.in, India's no-brokerage real-estate portal covering Bangalore, Mumbai, Pune, Delhi NCR and more. Paste one or more NoBroker search-list URLs and get price, size, amenities, owner ID, location and more for every property. Pay per result (see the Pricing tab). The residential proxy is built in.

What data you get

One dataset row per property, with 44 fields (missing optional values are null).

Field group	Fields
Identity	id, propertyCode, propertyTitle, url, detailUrl, imageUrl
Price	price, formattedPrice, negotiable, maintenanceIncluded, maintenanceCostPerSqFt, formattedMaintenanceAmount
Property	type, typeDesc, propertySize (sqft), bathroom, propertyAge, facing, parking, lift, powerBackup, waterSupply, kitchen, ownershipType
Building	buildingName, builderName, builderGrade
Location	locality, city, state, address, lat, lng, transitScore, lifestyleScore
Listing status	underLoan, premium, sponsored, active, ownerId, activationDate
Amenities	amenities (JSON object)
Run info	scrapedAt, searchUrlQuery (the search URL that produced the row)

url is the full listing link; detailUrl is the path as returned by the source.

How to use

1. On nobroker.in, open the search you want (sale or rent, a city and locality) and apply your filters.
2. Copy the address of the search-list page and paste it into Search URLs. You can add several.
3. Set Max items total.
4. Keep the default Proxy configuration (Apify Residential, India). It is already set up; you need no extra account.
5. Click Start, then open the table view or export the dataset as JSON, CSV or Excel.

The actor walks the result pages of each URL until it reaches your item limit or the end of the results.

Input

Field	Type	Default	Description
searchUrls	array of strings (required)	A Whitefield, Bangalore sale search (prefill)	NoBroker search-list URLs. They must contain the city path and the searchParam query parameter
maxItems	integer	100	Maximum property records across all URLs (1 to 5000)
proxyConfiguration	object	Apify Residential, country IN (prefill)	Proxy settings. Keep the prefilled value for reliable access

Example input (the prefilled search):

{
  "searchUrls": [
    "https://www.nobroker.in/property/sale/bangalore/Whitefield_search-list?searchParam=W3sibGF0IjoxMi45NjkxOTE1LCJsb24iOjc3LjcyMDIxNCwicGxhY2VJZCI6IkNoSUpfdkx5bUF3VnJqc1JVUWlwM0wzVTlOWSIsInBsYWNlTmFtZSI6IldoaXRlZmllbGQifV0="
  ],
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}

Output example

Values below are illustrative.

{
  "id": "8a9f00000000000000000000000000aa",
  "propertyCode": "NB-000000",
  "propertyTitle": "3 BHK Flat for sale in Whitefield",
  "url": "https://www.nobroker.in/property/sale/bangalore/Whitefield/example-3-bhk",
  "detailUrl": "/property/sale/bangalore/Whitefield/example-3-bhk",
  "imageUrl": "https://images.nobroker.in/example/thumbnail.jpg",
  "price": 12500000,
  "formattedPrice": "1.25 Crores",
  "type": "BHK3",
  "typeDesc": "3 BHK",
  "propertySize": 1650,
  "bathroom": 3,
  "buildingName": "Example Heights",
  "builderName": null,
  "builderGrade": null,
  "locality": "Whitefield",
  "city": "bangalore",
  "address": "Example Heights, Whitefield, Bengaluru",
  "ownershipType": "Single Owner",
  "propertyAge": 4,
  "facing": "E",
  "parking": "BOTH",
  "lift": true,
  "powerBackup": "FULL",
  "waterSupply": "CORPORATION",
  "kitchen": "MODULAR",
  "maintenanceIncluded": false,
  "maintenanceCostPerSqFt": 3.5,
  "formattedMaintenanceAmount": "5,775",
  "negotiable": true,
  "underLoan": false,
  "premium": false,
  "sponsored": false,
  "active": true,
  "state": "Karnataka",
  "amenities": { "LIFT": true, "GYM": true, "PARK": true },
  "ownerId": "0000000000",
  "activationDate": 1790000000000,
  "lat": 12.9692,
  "lng": 77.7202,
  "transitScore": 7.5,
  "lifestyleScore": 8.1,
  "scrapedAt": "2026-10-02T09:30:00Z",
  "searchUrlQuery": "https://www.nobroker.in/property/sale/bangalore/Whitefield_search-list?searchParam=..."
}

Use cases

• Market and price research: compare asking prices, sizes and maintenance costs by locality.
• Investor screening: filter by ownership type, property age, loan status and amenities.
• Lead generation and listing alerts for agents and service providers.
• Data feeds for property analytics and dashboards.

FAQ

Do I need an API key or my own proxy? No. No key or login is needed, and the residential proxy (India) is built in. Keep the default proxy setting in the input.

How is it priced? Pay per result. See the Pricing tab for the current price per property.

Which URLs work? NoBroker search-list URLs for sale or rent, copied from your browser after applying filters on nobroker.in. The URL must include the searchParam value.

Is there a limit for free-plan runs? Runs on a free Apify plan return a small preview (the first URL, up to 10 properties, first page only). Paid plans have no preview limit.

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.