MagicBricks Scraper - India Property Listings avatar

MagicBricks Scraper - India Property Listings

Pricing

from $5.00 / 1,000 results

Go to Apify Store
MagicBricks Scraper - India Property Listings

MagicBricks Scraper - India Property Listings

Scrape public MagicBricks sale and rental listings across India with price, BHK, area, location, project, builder, images, lister and RERA metadata.

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Ben

Ben

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Scrape public MagicBricks property listings across India and export structured sale or rental data. Search by city and property type, then collect the asking price, BHK, bathrooms, balconies, area, price per square foot, locality, address, property description, photos, furnishing, ownership, parking, facing, possession status, agent or owner name, agency, RERA-agent registration, coordinates, and listing URL.

The Actor uses MagicBricks' first-party public web search endpoint instead of rendering every result page in a browser. That makes collection faster and more predictable while preserving the rich fields shown in search. A direct request is attempted first; if MagicBricks blocks the datacenter route, the Actor switches to a sticky India residential session. Results are deduplicated before they are written to the dataset.

What you can collect

Each property row can include:

  • MagicBricks listing ID and direct listing URL;
  • property title and public description;
  • sale or rent transaction type;
  • property type, BHK, bathrooms, and balconies;
  • numeric asking price, formatted Indian price, and currency;
  • price per square foot, covered area in square feet, and converted square metres;
  • city, locality, landmark, and public address;
  • project, builder, furnishing, ownership, facing, parking, and flooring;
  • possession and transaction status;
  • posted date and the visible posted label;
  • latitude and longitude when the listing provides them;
  • one preview photo and the complete public photo array;
  • lister name, lister type, lister ID, and agency;
  • RERA-agent status and public registration value when shown;
  • approval authority and listing quality flags; and
  • a transparent lead score based on contact, agency, registration, location, image, price, URL, and description completeness.

MagicBricks does not expose an email address or phone number in every public search result. The Actor does not invent or infer contact details. It returns the public agent, owner, agency, and RERA fields that the first-party search response actually supplies.

Use cases

Property-market research

Collect comparable asking prices for apartments, houses, villas, plots, or land in major Indian cities. Export the data to a spreadsheet or database and calculate median asking price, price per square foot, inventory mix, or differences between localities. Listing prices are offers, not completed transaction prices, so use them as market signals rather than registered-sale evidence.

Real-estate lead research

Build a list of public agents, owners, agencies, and RERA-registered professionals attached to active listings. Sort by lead_score to prioritize complete records. Before outreach, verify the listing is current and follow applicable Indian privacy, telecom, anti-spam, and platform rules.

Rental and acquisition monitoring

Run separate saved Tasks for sale and rent searches. Schedule them daily or weekly, compare listing IDs, and identify newly observed inventory, changed asking prices, or properties that disappear from search.

Location and investment analysis

Use locality, coordinates, area, price, and price-per-square-foot fields in a BI dashboard or map. Combine the dataset with public infrastructure, commute, RERA, or neighborhood data to support manual investment research. The Actor does not provide investment advice or guarantee listing accuracy.

Broker and agency intelligence

Measure which agencies appear in selected locations, what property types they represent, and how complete their listings are. Agency fields are only returned when MagicBricks publishes them in the result response.

Automation and feeds

Connect the default dataset to Make, Zapier, n8n, Google Sheets, Airtable, a warehouse, or your application through the Apify API. Bounded defaults make it practical to create repeat-use city feeds without unbounded crawling.

Input

FieldTypeDescription
citiesarrayIndian city names such as Bengaluru, Mumbai, Hyderabad, Pune, Chennai, Kolkata, Ahmedabad, or New Delhi.
transactionstringsale or rent.
propertyTypesarrayOne or more of apartment, house, or plot.
maxResultsPerSearchintegerMaximum listings for each city and property-type combination. Default: 10.
maxPagesPerSearchintegerSafety limit for pagination.

Example sale search:

{
"cities": ["Bengaluru", "Hyderabad"],
"transaction": "sale",
"propertyTypes": ["apartment", "house"],
"maxResultsPerSearch": 25,
"maxPagesPerSearch": 2
}

Example rental search:

{
"cities": ["Mumbai"],
"transaction": "rent",
"propertyTypes": ["apartment"],
"maxResultsPerSearch": 20,
"maxPagesPerSearch": 2
}

The result limit applies to each city and property-type combination. Two cities and two property types can therefore return up to four times maxResultsPerSearch, subject to actual availability and deduplication.

Output example

{
"id": "82455477",
"url": "https://www.magicbricks.com/propertyDetails-...",
"title": "4BHK Residential House for New Property in Horamavu",
"description": "Beautiful 4 BHK duplex house for sale...",
"transaction": "sale",
"property_type": "Residential House",
"bedrooms": 4,
"bathrooms": 4,
"balconies": 1,
"price": 20300000,
"price_display": "2.03 Cr",
"currency": "INR",
"price_per_sqft": 9227,
"area_sqft": 2200,
"area_sqm": 204.39,
"city": "Bangalore",
"locality": "Horamavu",
"address": "Bangalore, Karnataka",
"furnishing": "Semi-Furnished",
"ownership": "Freehold",
"possession_status": "Ready to Move",
"latitude": 13.03171017,
"longitude": 77.66088781,
"lister_name": "Surya",
"lister_type": "Agent",
"agency": "Nexus Walls Pvt Ltd",
"is_rera_agent": true,
"rera_agent_id": "PRM/KA/RERA/...",
"lead_score": 100,
"search_city": "Bengaluru",
"search_rank": 1,
"scraped_at": "2026-07-11T13:00:00+00:00"
}

Fields can be null when a seller did not publish them. Numeric output remains numeric wherever the source provides a usable value, while formatted Indian prices are preserved separately in price_display.

How it works

  1. The Actor validates the cities, transaction, property types, and limits.
  2. It resolves known city names to MagicBricks search identifiers and can use the public autosuggest endpoint for additional cities.
  3. It calls the first-party property search endpoint with the selected transaction and property type.
  4. Direct access is attempted first to minimize cost.
  5. If the source blocks the datacenter route, the Actor creates one sticky India residential session and reuses it.
  6. It maps the current MagicBricks response fields rather than relying on outdated HTML selectors.
  7. Listings are deduplicated by source ID or URL.
  8. The Actor pushes one clean dataset item per unique listing and fails explicitly if no usable properties are returned.

The Actor runs with limited Apify permissions and only writes to its default dataset. It does not require a MagicBricks login, seller account, or user credentials.

Pricing

This Actor uses pay-per-event pricing: a minimal start event and a flat $0.005 event for each unique property written to the default dataset. Duplicate or unusable records are not pushed and do not create result events. Check the current Store pricing panel before a large run because Store pricing is authoritative.

The per-property rate follows the portfolio's standard for new real-estate Actors. It is positioned for reusable lead and market data rather than a high run-start fee. Residential proxy use is handled inside the Actor when needed.

Reliability notes

Property portals change fields and traffic controls. This Actor validates the first-party JSON response and raises an error on empty output instead of returning a misleading successful run. For recurring feeds, save a Task, keep limits reasonable, and enable Apify failure notifications.

Search results are dynamic. Ranking, inventory, pricing, lister status, and public metadata can change between runs. Always open the listing URL before making a purchase, rental, outreach, or compliance decision. MagicBricks and individual advertisers remain responsible for source content.

API example

curl -X POST "https://api.apify.com/v2/acts/benthepythondev~magicbricks-scraper/runs?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"cities":["Bengaluru"],"transaction":"sale","propertyTypes":["apartment"],"maxResultsPerSearch":10,"maxPagesPerSearch":1}'

Read or export the default dataset after the run succeeds. Keep Apify tokens in secret storage or server-side environment variables and never publish them in client-side code.

Frequently asked questions

Can it scrape properties for rent?

Yes. Set transaction to rent.

Does it support cities outside the hardcoded examples?

The Actor knows common major-city identifiers and can resolve additional Indian cities through MagicBricks' public autosuggest data. If a small locality is not resolved as a city, use its parent city.

Does apartment return only apartment cards?

MagicBricks controls its property-type codes and can include related residential inventory. The Actor returns the exact property_type published for each listing so downstream filtering stays truthful.

Are phone numbers or emails included?

Only when the public search response provides them. The current result feed commonly exposes agent or owner names, agency, lister type, and RERA-agent information but not a direct phone or email for every card.

What does lead_score mean?

It is a transparent completeness score, not a prediction of conversion. Points come from public lister, agency, RERA, coordinates, images, price, URL, and description fields.

Why can a listing have no coordinates?

Some advertisers omit precise map data or publish zero coordinates. The Actor does not geocode or guess an address because that could introduce incorrect location claims.

If this Actor produces useful property data, leave an honest Apify Store review. For support, include the run ID, a sanitized input, and the expected result; never share login credentials or API tokens.

Keywords: MagicBricks scraper, India property API, Bangalore real estate scraper, Mumbai rental scraper, property listing data, Indian real estate leads, RERA agent scraper, MagicBricks property search, house price dataset, Apify real estate scraper.