/acres99/properties/search

POST /api/acres99/properties/search

Price: 10 credits

Search 99acres listings by city for buy or rent. Returns the search feed of individual property listings and new-launch projects: id, name, heading, price and price per sqft, carpet area, configuration, floor, locality, geo coordinates, RERA id and dealer name.

How to use it

Search 99acres residential listings within a city for buy or rent. Requires city (slug, e.g. 'mumbai') and city_id (numeric 99acres id, e.g. 12 for Mumbai) plus listing_type ('buy' or 'rent'). Returns the mixed search feed: each item has result_type ('property' for an individual resale/owner listing, 'project' for a builder new-launch development). For result_type 'property': id (spid), url, name, heading, description, property_type, transaction_type, price/price_text/price_per_sqft/currency (INR), carpet_area_sqft, bedroom_count/bathroom_count, floor/total_floor_count, possession_status, city/locality, latitude/longitude, rera_id, is_verified, dealer_name/dealer_company. For result_type 'project': id, npxid, url, name, heading (configuration summary), builder_name, price/price_text, possession_status. Use acres99/properties with a spid or acres99/projects with an npxid 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 slug to search in, e.g. 'mumbai', 'delhi', 'bangalore' (minLength: 1)
• city_id integer required — Numeric 99acres city id (e.g. 12 for Mumbai, 1 for Delhi) (>: 0)
• listing_type string — Listing type (default: "buy"; one of: "buy", "rent")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "Acres99SearchResult")
• result_type string required
• id string required
• spid string nullable
• npxid string nullable
• url string required
• name string nullable
• heading string nullable
• description string nullable
• property_type string nullable
• transaction_type string nullable
• builder_name string nullable
• price number nullable
• price_text string nullable
• price_per_sqft number nullable
• currency string nullable
• carpet_area_sqft number nullable
• bedroom_count integer nullable
• bathroom_count integer nullable
• floor string nullable
• total_floor_count integer nullable
• possession_status string nullable
• city string nullable
• locality string nullable
• latitude number nullable
• longitude number nullable
• rera_id string nullable
• is_verified boolean 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.