/hemnet/properties/search

POST /api/hemnet/properties/search

Price: 1 credit

Search active Hemnet property listings for sale by location and filters (property type, rooms, living and land area, price, monthly fee, price per m², construction year, distance to water/coastline, floor, balcony, elevator, new construction, foreclosure, bidding started, price drops, recently published, free-text keyword) with configurable sorting. Returns listing cards with address, price, fee, area, rooms, coordinates, broker (name and image), agency (name and image) and the listing detail url.

How to use it

Search Hemnet for-sale listings. location_ids are numeric Hemnet location ids (resolve free text like 'Stockholm' via hemnet/locations/search). Filter by radius, housing_form_groups (apartments, houses, townhouses, vacation_homes, plots, farms, other), rooms_min/max, living_area_min/max, land_area_min, price_min/max, fee_max, square_meter_price_min/max, construction_year_min/max, coastline/water_distance_max, floor, balcony, elevator, new_construction, foreclosure, bidding_started, live_stream, price_change, published_since and keyword; sort by newest/oldest/price/area/fee/etc. Each result has id, street_address, location_description, asking_price, fee, square_meter_price, rooms, living_area, land_area, floor, housing_form, is_new_construction, is_upcoming, published_at, broker_name, broker_agency_name, broker_image, broker_agency_image, coordinates, labels, images and url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• location_ids array required — Hemnet numeric location ids to search in (resolve free text via hemnet/locations/search) (examples: ["17744"]; minItems: 1)
• radius string nullable — Expand the search around the given locations by this radius (one of: "1", "2", "5", "10", "15", "30", "50", "100")
• housing_form_groups array nullable — Restrict to these property types (one of: "apartments", "houses", "townhouses", "vacation_homes", "plots", "farms", "other")
• rooms_min number nullable — Minimum number of rooms (>: 0)
• rooms_max number nullable — Maximum number of rooms (>: 0)
• living_area_min integer nullable — Minimum living area in m² (>: 0)
• living_area_max integer nullable — Maximum living area in m² (>: 0)
• land_area_min integer nullable — Minimum land area in m² (>: 0)
• price_min integer nullable — Minimum asking price in SEK (min: 0)
• price_max integer nullable — Maximum asking price in SEK (min: 0)
• fee_max integer nullable — Maximum monthly fee in SEK (min: 0)
• square_meter_price_min integer nullable — Minimum price per m² in SEK (min: 0)
• square_meter_price_max integer nullable — Maximum price per m² in SEK (min: 0)
• construction_year_min integer nullable — Minimum construction year
• construction_year_max integer nullable — Maximum construction year
• coastline_distance_max integer nullable — Maximum distance to coastline in meters (min: 0)
• water_distance_max integer nullable — Maximum distance to water in meters (min: 0)
• floor string nullable — Floor position restriction (one of: "all", "ground_floor_only", "above_ground_floor", "top_floor_only")
• balcony string nullable — Balcony availability filter (one of: "include", "only", "exclude")
• elevator string nullable — Elevator availability filter (one of: "include", "only", "exclude")
• new_construction string nullable — New construction filter (one of: "include", "only", "exclude")
• foreclosure string nullable — Foreclosure (Kronofogden) filter (one of: "include", "only", "exclude")
• bidding_started string nullable — Bidding-started filter (one of: "include", "only", "exclude")
• live_stream string nullable — Live-streamed showing filter (one of: "include", "only", "exclude")
• price_change string nullable — Filter by price change (e.g. only price drops) (one of: "include", "only_changed", "only_decrease", "only_increase")
• published_since string nullable — Only listings published within this period (one of: "1d", "3d", "7d", "14d")
• keyword string nullable — Free-text keyword (e.g. pool, kakelugn) (minLength: 1)
• sort string — Result ordering (default: "newest"; one of: "newest", "oldest", "lowest_price", "highest_price", "lowest_square_meter_price", "highest_square_meter_price", "largest_living_area", "smallest_living_area", "largest_land_area", "smallest_land_area", "lowest_fee", "highest_fee", "next_open_house", "address_asc", "address_desc", "closest_to_water", "closest_to_coastline")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "HemnetForSaleCard")
• id string required
• street_address string nullable
• location_description string nullable
• asking_price string nullable
• fee string nullable
• square_meter_price string nullable
• rooms string nullable
• living_area string nullable
• land_area string nullable
• floor string nullable
• housing_form string nullable
• is_new_construction boolean nullable
• is_upcoming boolean nullable
• published_at string nullable
• broker_name string nullable
• broker_agency_name string nullable
• broker_image string nullable
• broker_agency_image string nullable
• coordinates array (default: [])
• labels array (default: [])
• url string nullable
• images array (default: [])

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.