POST /api/acres99/properties
Price: 10 credits
Get full 99acres property listing details by id (spid) or property URL: title, description, price and price per sqft, brokerage, carpet area, configuration (bedrooms, bathrooms, balconies), floor, facing, furnishing, flooring, power backup, parking, transaction type, ownership, availability and possession, posted and updated dates, locality and geo coordinates, RERA id, amenities, highlights, nearby places, gated/corner/pet-friendly flags, images and dealer details.
Fetch a single 99acres property listing by id (spid, e.g. F81765438) or a property URL. Returns one item with title, name (society/building), description, property_type, transaction_type (Resale/New), ownership (Freehold/Leasehold), availability and possession_date, posted_at/updated_at (listing dates), price/price_text/price_per_sqft/currency (INR), is_price_negotiable, is_price_all_inclusive, brokerage/brokerage_type, carpet_area_sqft, bedroom_count/bathroom_count/balcony_count, floor, total_floor_count, facing, furnishing, flooring, power_backup, parking, age, city/locality/address, latitude/longitude, rera_id, is_verified, is_gated/is_corner/is_pet_friendly, amenities, highlights (key selling points), overlooking, additional_rooms, nearby_places (category, text, distance to railway/schools/hospitals/etc), image+images, and dealer (name, company, type, image, member_since, website_url, is_rera_registered, listed/verified property counts).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)property string required — 99acres property id (spid) or a property page URL containing it (examples: "F81765438", "https://www.99acres.com/3-bhk-bedroom-apartment-flat-for-sale-in-bandra-west-western-mumbai-1630-sqft-r4-spid-F81765438"; minLength: 1)@type string (default: "Acres99Property")id string requiredspid string nullableurl string requiredname string nullabledescription string nullableproperty_type string nullabletransaction_type string nullableownership string nullableavailability string nullablepossession_date string nullableposted_at string nullableupdated_at string nullableprice number nullableprice_text string nullableprice_per_sqft number nullablecurrency string nullableis_price_negotiable boolean nullableis_price_all_inclusive boolean nullablebrokerage string nullablebrokerage_type string nullableis_brokerage_negotiable boolean nullablearea_sqft number nullablecarpet_area_sqft number nullablebedroom_count integer nullablebathroom_count integer nullablebalcony_count integer nullablefloor string nullabletotal_floor_count integer nullablefacing string nullablefurnishing string nullableflooring string nullablepower_backup string nullableparking string nullableage string nullableroad_width string nullablecity string nullablelocality string nullableaddress string nullablelatitude number nullablelongitude number nullablerera_id string nullablerera_authority string nullableis_verified boolean nullableis_gated boolean nullableis_corner boolean nullableis_pet_friendly boolean nullableamenities array (default: [])highlights array (default: [])overlooking array (default: [])additional_rooms array (default: [])nearby_places array (default: [])@type string (default: "Acres99NearbyPlace")category string nullabletext string nullabledistance string nullableimage string nullableimages array (default: [])dealer object nullable@type string (default: "Acres99PropertyDealer")name string nullablecompany string nullabletype string nullableimage string nullablemember_since string nullablewebsite_url string nullableis_rera_registered boolean nullablelisted_property_count integer nullableverified_property_count integer nullable422 — 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 spid, 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.