REAL ESTATE · INDIA
magicbricks.com Property (India)
Property listings from magicbricks.com (India's #1 property portal by traffic) for a list of cities (Bangalore, Mumbai, Delhi, Pune, Hyderabad, Chennai and more), for sale or rent.
About this data
Property listings from magicbricks.com (India's #1 property portal by traffic) for a list of cities (Bangalore, Mumbai, Delhi, Pune, Hyderabad, Chennai and more), for sale or rent. One normalized record per listing: URL, price INR, bedrooms (BHK), locality, city, listing type, images and source.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/in/magicbricks/listings
Live Magicbricks property listings for one Indian city (Bangalore by default), for sale or rent: price in INR, bedrooms, locality, city, listing type, images and listing URL.
First results page only, no detail pages, up to 20 listings per call; the residential proxy is included in the price.
Input
Send a JSON body to POST https://api.ssh.autos/v1/in/magicbricks/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
city | string | optional | one of Bangalore, Mumbai, Delhi, Pune, Hyderabad, Chennai; default "Bangalore" |
operation | string | optional | one of buy, rent; default "buy" |
maxResults | integer | optional | 1–20; default 10 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 10 fields; a field the source does not publish comes back null.
10 fields per record
| Field | Type | Notes |
|---|---|---|
listing_key | string | Stable record key 'magicbricks.com:{listingId}', or the canonical URL when the id is unknown. |
url | string | Canonical listing URL on www.magicbricks.com (/propertyDetails/{slug}&id={listingId}); the id query param is preserved, tracking parameters removed. |
price_inr | integer | Asking price in integer INR ('₹ 1.20 Cr' → 12000000, '₹ 85 Lakh' → 8500000, '₹ 1,20,00,000' → 12000000). Null when the price is hidden ('Price on Request'). |
bedrooms | integer | Bedrooms from the 'N BHK' configuration. Null when absent. |
locality | string | Locality/neighbourhood from the card, JSON-LD addressLocality, or the listing title. |
city | string | The searched city. |
listing_type | string | Listing type: 'buy' or 'rent'. |
images | array of strings | Listing image URLs (img.staticmb.com). |
source | string | Source slug 'magicbricks.com'. |
scraped_at | string | UTC ISO-8601 collection timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/in/magicbricks/listings -m POST -b '{"city": "Bangalore", "maxResults": 3}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: magicbricks.com Property Scraper (India). Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt