/magicbricks/projects

POST /api/magicbricks/projects

Price: 20 credits

Get full Magicbricks new-launch project details by id (psmId) or project URL: name, property and project type, configuration, description, construction status, launch and possession dates, price range and per sqft, project area, tower and unit counts, locality and geo coordinates, RERA id and approval, builder, brochure, amenities, highlights, unit configurations, ratings, and gallery images.

How to use it

Fetch a single Magicbricks new-launch (builder development) project by id (psmId, e.g. 5433263) or a project URL. Returns one item with name, project_type (Residential/Commercial), property_type, configuration (e.g. '3 BHK Multistorey Apartments'), description, construction_status, launch_date, possession_date, price_min/price_max/price_text/price_per_sqft/currency (INR), project_area, tower_count, unit_count, bedrooms, city/locality/address/state/pincode, latitude/longitude, rera_id, is_rera_approved, is_prelaunch, builder_name/builder_description/builder_url, brochure_url, amenities, highlights (why-buy points), configurations (unit bedrooms/type/area_sqft), rating (overall plus category breakdown), image, images (gallery), image_count. Projects are distinct from individual property listings (use magicbricks/properties for those).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Magicbricks project id (psmId) or a project page URL containing it (examples: "5433263", "https://www.magicbricks.com/amogaya-adorit-budigere-cross-bangalore-pdpid-4d4235343333323633"; minLength: 1)

Response

• @type string (default: "MagicbricksProject")
• id string required
• url string required
• name string nullable
• project_type string nullable
• property_type string nullable
• configuration string nullable
• description string nullable
• construction_status string nullable
• launch_date string nullable
• possession_date string nullable
• price_min number nullable
• price_max number nullable
• price_text string nullable
• price_per_sqft number nullable
• currency string nullable
• project_area string nullable
• tower_count integer nullable
• unit_count integer nullable
• bedrooms string nullable
• city string nullable
• locality string nullable
• address string nullable
• state string nullable
• pincode string nullable
• latitude number nullable
• longitude number nullable
• rera_id string nullable
• is_rera_approved boolean nullable
• is_prelaunch boolean nullable
• builder_name string nullable
• builder_description string nullable
• builder_url string nullable
• brochure_url string nullable
• amenities array (default: [])
• highlights array (default: [])
• configurations array (default: [])
  • @type string (default: "MagicbricksProjectConfiguration")
  • bedrooms integer nullable
  • property_type_code string nullable
  • area_sqft number nullable
• rating object nullable
  • @type string (default: "MagicbricksProjectRating")
  • overall number nullable
  • construction_quality number nullable
  • maintenance number nullable
  • amenities number nullable
  • infrastructure number nullable
  • security number nullable
  • rating_count integer nullable
• image string nullable
• images array (default: [])
• 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 — Project not found (well-formed but nonexistent psmId, or page has no project) 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.