/acres99/projects

POST /api/acres99/projects

Price: 10 credits

Get full 99acres new-launch project details by id (npxid) or project URL: name, project type (residential/commercial), description, builder, construction status and possession date, price range, locality and geo coordinates, RERA status and id, unit configurations (BHK, area, price), gallery images, facilities, key highlights, nearby places with distances, and brochure / payment-plan PDF links.

How to use it

Fetch a single 99acres new-launch project (builder development) by id (npxid, e.g. r463535) or a project URL. Returns one item with name, project_type (Residential/Commercial), description, builder_name/builder_url, construction_status, possession_date, price_min/price_max/price_text/currency (INR), city/locality/address, latitude/longitude, rera_status/rera_id, image, images (photo gallery), configurations (list of unit types with label e.g. '2 BHK', area_sqft, area_type, price), facilities (amenities), highlights, nearby_places (category, text, distance to malls/schools/metro/etc) and brochure_url/payment_plan_url (official builder PDFs, absent on some projects). Projects are distinct from individual property listings (use acres99/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 — 99acres project id (npxid) or a project page URL containing it (examples: "r463535", "https://www.99acres.com/mahindra-rainforest-lbs-marg-central-mumbai-suburbs-npxid-r463535"; minLength: 1)

Response

• @type string (default: "Acres99Project")
• id string required
• npxid string nullable
• url string required
• name string nullable
• project_type string nullable (one of: "Residential", "Commercial")
• description string nullable
• builder_name string nullable
• builder_url string nullable
• construction_status string nullable
• possession_date string nullable
• price_min number nullable
• price_max number nullable
• price_text string nullable
• currency string nullable
• city string nullable
• locality string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• rera_status string nullable
• rera_id string nullable
• brochure_url string nullable
• payment_plan_url string nullable
• image string nullable
• images array (default: [])
• configurations array (default: [])
  • @type string (default: "Acres99ProjectConfiguration")
  • label string nullable
  • sub_label string nullable
  • property_type string nullable
  • area_sqft number nullable
  • area_text string nullable
  • area_type string nullable
  • price number nullable
  • price_text string nullable
• facilities array (default: [])
• highlights array (default: [])
• nearby_places array (default: [])
  • @type string (default: "Acres99ProjectNearbyPlace")
  • category string nullable
  • text string nullable
  • distance 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 — Project not found (well-formed but nonexistent npxid, 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.