/magicbricks/properties/search

POST /api/magicbricks/properties/search

Price: 20 credits

Search Magicbricks property listings by city for sale or rent, with filters for property type, bedrooms, budget, area, recency, gated community and corner property. Returns listing cards with price, configuration, area, locality, builder/project, amenities, nearby landmarks, geo coordinates, RERA id, image and dealer name.

How to use it

Search Magicbricks residential property listings within a city for sale (listing_type 'buy') or rent ('rent'). Requires city (e.g. 'Bangalore') and count. Optional filters: proptype (Apartment/Independent-House/Villa/Plot/Farm-House/Agricultural-Land), bedrooms (1-6 BHK), budget_min/budget_max (INR), area_min/area_max + area_unit (Sq-ft/Sq-m/Sq-yrd), posted_since (days), gated_community, corner_property, sort (Relevance/Price-Low-to-High/Price-High-to-Low/Most-Recent/Rate-per-sqft-Low-to-High/Rate-per-sqft-High-to-Low). Each result has id, url, title, name, property_type, transaction_type, listing_for, possession_status, price/price_text/price_per_sqft/currency (INR), area_sqft/area_unit, bedroom_count/bathroom_count/balcony_count, furnishing, city/locality, latitude/longitude, rera_id, is_verified, posted_by, builder_name/project_name/project_url, amenities, landmarks, image, image_count, dealer_name/dealer_company. Use magicbricks/properties with a returned id for full details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string required — City to search in, e.g. 'Bangalore', 'Mumbai', 'Pune' (minLength: 1)
• listing_type string — Whether to search properties for sale or rent (default: "buy"; one of: "buy", "rent")
• count integer required — Max number of results to return (min: 1)
• proptype array nullable — Filter by property type(s) (one of: "Apartment", "Independent-House", "Villa", "Plot", "Farm-House", "Agricultural-Land")
• bedrooms array nullable — Filter by number of bedrooms (BHK), 1-6
• budget_min integer nullable — Minimum price in INR (min: 0)
• budget_max integer nullable — Maximum price in INR (min: 0)
• area_min integer nullable — Minimum covered area (min: 0)
• area_max integer nullable — Maximum covered area (min: 0)
• area_unit string — Unit for area_min/area_max (default: "Sq-ft"; one of: "Sq-ft", "Sq-m", "Sq-yrd")
• posted_since integer nullable — Only listings posted within this many days (e.g. 1, 7, 15, 30) (min: 1)
• gated_community boolean nullable — Only properties in a gated community
• corner_property boolean nullable — Only corner properties
• sort string — Result ordering (default: "Relevance"; one of: "Relevance", "Price-Low-to-High", "Price-High-to-Low", "Most-Recent", "Rate-per-sqft-Low-to-High", "Rate-per-sqft-High-to-Low")

Response

• @type string (default: "MagicbricksSearchProperty")
• id string required
• url string required
• name string nullable
• description string nullable
• property_type string nullable
• transaction_type string nullable
• listing_for string nullable
• possession_status string nullable
• posted_at string nullable
• price number nullable
• price_text string nullable
• price_per_sqft number nullable
• currency string nullable
• area_sqft number nullable
• area_unit string nullable
• bedroom_count integer nullable
• bathroom_count integer nullable
• balcony_count integer nullable
• furnishing string nullable
• city string nullable
• locality string nullable
• latitude number nullable
• longitude number nullable
• rera_id string nullable
• is_verified boolean nullable
• posted_by string nullable
• builder_name string nullable
• project_name string nullable
• project_url string nullable
• amenities array (default: [])
• landmarks array (default: [])
• image string nullable
• image_count integer nullable
• dealer_name string nullable
• dealer_company string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.