/magicbricks/properties

POST /api/magicbricks/properties

Price: 20 credits

Get full Magicbricks property listing details by id or property URL: title, description, price, price per sqft and EMI, covered area, configuration (bedrooms, bathrooms, balconies), furnishing, transaction type, possession status and date, posted date, city, locality and address, geo coordinates, RERA id, builder and project, amenities, images and dealer details.

How to use it

Fetch a single Magicbricks property listing by id (e.g. 84771039) or a property URL. Returns one item with title, name (society/project), description, property_type, transaction_type (New/Resale), listing_for (For Sale/For Rent), possession_status (a label such as 'Under Construction', 'Immediately' or "Dec '28"), possession_date (ISO year-month, e.g. '2028-12'; empty on ready-to-move and rent listings, which have no future possession date), posted_at, price/price_text/price_per_sqft/emi/currency (INR), area_sqft with area_unit (Sq-ft on built property, Sq-yrd or Acre on some plots - price_per_sqft is per that same unit), bedroom_count/bathroom_count/balcony_count, furnishing, is_corner, is_verified, listing_tier, city/locality/address/state, latitude/longitude, rera_id, builder_name/project_name/project_url/builder_url, amenities, image+images, image_count, and dealer (name, company, type, operating_since, buyers_served_count, verified/sale property counts, years_of_experience, profile_url).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Magicbricks property id or a property page URL containing it (examples: "84771039", "https://www.magicbricks.com/propertyDetails/3-BHK-1803-Sq-ft-Multistorey-Apartment-FOR-Sale-Budigere-Cross-in-Bangalore&id=4d423834373731303339"; minLength: 1)

Response

• @type string (default: "MagicbricksProperty")
• 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
• possession_date string nullable
• posted_at string nullable
• price number nullable
• price_text string nullable
• price_per_sqft number nullable
• emi 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
• is_corner boolean nullable
• is_verified boolean nullable
• listing_tier string nullable
• city string nullable
• locality string nullable
• address string nullable
• state string nullable
• latitude number nullable
• longitude number nullable
• rera_id string nullable
• builder_name string nullable
• project_name string nullable
• project_url string nullable
• builder_url string nullable
• amenities array (default: [])
• image string nullable
• images array (default: [])
• image_count integer nullable
• dealer object nullable
  • @type string (default: "MagicbricksPropertyDealer")
  • name string nullable
  • company string nullable
  • type string nullable
  • operating_since string nullable
  • buyers_served_count integer nullable
  • verified_property_count integer nullable
  • sale_property_count integer nullable
  • years_of_experience integer nullable
  • profile_url 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 — Property not found (well-formed but nonexistent id, or page has no listing) 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.