/magicbricks/projects/search

POST /api/magicbricks/projects/search

Price: 10 credits

Search Magicbricks new-launch projects by city, with filters for bedrooms, budget, possession status and RERA approval. Returns project cards with name, builder, configuration, price range, possession, locality, RERA approval, rating and image.

How to use it

Search Magicbricks new-launch (builder development) projects within a city. Requires city (e.g. 'Bangalore') and count. Optional filters: bedrooms (1-6 BHK), budget_min/budget_max (INR), possession (ready-to-move/under-construction), rera_approved. Each result has id (psmId), url, name, property_type, bedrooms, configurations (unit bedrooms/type/area_sqft), description, builder_name/builder_logo, price_min/price_max/price_text/price_per_sqft/currency (INR), project_area/project_area_unit, tower_count/unit_count, launch_date, possession_date/possession_year, city/locality/pincode, is_rera_approved, rating, review_count, highlights, image, image_count. Use magicbricks/projects with a returned id for full project 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 new-launch projects in, e.g. 'Bangalore', 'Mumbai' (minLength: 1)
• count integer required — Max number of results to return (min: 1)
• 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)
• possession string nullable — Filter by possession status (one of: "ready-to-move", "under-construction")
• rera_approved boolean nullable — Only RERA-approved projects

Response

• @type string (default: "MagicbricksSearchProject")
• id string required
• url string required
• name string nullable
• property_type string nullable
• bedrooms string nullable
• configurations array (default: [])
  • @type string (default: "MagicbricksProjectConfiguration")
  • bedrooms integer nullable
  • property_type_code string nullable
  • area_sqft number nullable
• description string nullable
• builder_name string nullable
• builder_logo string nullable
• price_min number nullable
• price_max number nullable
• price_text string nullable
• price_per_sqft number nullable
• currency string nullable
• project_area number nullable
• project_area_unit string nullable
• tower_count integer nullable
• unit_count integer nullable
• launch_date string nullable
• possession_date string nullable
• possession_year string nullable
• city string nullable
• locality string nullable
• pincode string nullable
• is_rera_approved boolean nullable
• rating number nullable
• review_count integer nullable
• highlights array (default: [])
• image string nullable
• image_count integer 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.