POST /api/propertyguru/properties
Price: 10 credits
Get full PropertyGuru property listing details by id or listing URL: title, listing type, price and price per sqft, price type, bedrooms, bathrooms, floor and land area, property type, HDB type, floor level, furnishing, tenure, build year, developer, district / region / estate, street and address, postcode, geo coordinates, green score, project reference, amenities, unit features, nearby places (MRT, schools), description, images and floorplans, and the listing agent (name, CEA license, agency).
Fetch a single PropertyGuru property listing by id (e.g. 500126496) or a listing URL. Set region to 'sg' (Singapore) or 'my' (Malaysia). Returns one item with title, listing_type (For Sale / For Rent), status, description, headline, property_type/property_type_code, hdb_type, price/price_text/price_type/price_per_sqft/currency, maintenance_fee, bedrooms/bathrooms, floor_area_sqft/land_area_sqft, floor_level, furnishing, facing, tenure/tenure_text, build_year, is_new_project, developer, project_id/project_name/project_url, green_score (0-5) and green_score_description, district_code/district_text/region_text, estate, street/address/postcode, latitude/longitude, posted_at/updated_at, is_verified, amenities, unit_features, nearby_places (category MRT/schools, name, distances), image+images, floorplans, and agent (id, name, license, job_title, agency, agency_license, image, profile_url).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)region string — PropertyGuru regional marketplace (sg = Singapore, my = Malaysia). (default: "sg"; one of: "sg", "my")listing string required — PropertyGuru listing id or a listing page URL containing it (examples: "500126496", "https://www.propertyguru.com.sg/listing/hdb-for-sale-10-holland-avenue-500126496"; minLength: 1)@type string (default: "PropertyGuruProperty")id string requiredurl string requiredlisting_type string nullablestatus string nullabledescription string nullableheadline string nullableproperty_type string nullableproperty_type_code string nullablehdb_type string nullableprice number nullableprice_text string nullableprice_type string nullableprice_per_sqft number nullablecurrency string nullablemaintenance_fee number nullablebedrooms integer nullablebathrooms integer nullablefloor_area_sqft number nullableland_area_sqft number nullablefloor_level string nullablefurnishing string nullablefacing string nullabletenure string nullabletenure_text string nullablebuild_year integer nullableis_new_project boolean nullabledeveloper string nullableproject_id string nullableproject_name string nullableproject_url string nullablegreen_score integer nullablegreen_score_description string nullabledistrict_code string nullabledistrict_text string nullableregion_text string nullableestate string nullablestreet string nullableaddress string nullablepostcode string nullablelatitude number nullablelongitude number nullableposted_at string nullableupdated_at string nullableis_verified boolean nullableamenities array (default: [])unit_features array (default: [])nearby_places array (default: [])@type string (default: "PropertyGuruNearbyPlace")category string requiredname string requireddistance_km number nullablewalking_distance_km number nullablewalking_duration_mins integer nullablesubcategory string nullableimage string nullableimages array (default: [])floorplans array (default: [])agent object nullable@type string (default: "PropertyGuruPropertyAgent")id string nullablename string nullablelicense string nullablejob_title string nullableagency string nullableagency_license string nullableimage string nullableprofile_url string 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 — Listing 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.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.