/funda/listings

POST /api/funda/listings

Price: 5 credits

Get full Funda real estate listing details by listing id (or listing URL): address, neighbourhood, asking/rental price, living area, volume, number of rooms and bedrooms, energy label, build year, object and offering type, status, full description, photos, coordinates, selling agent, neighbourhood statistics, sale history (for sold/rented listings) and the full grouped characteristics (Kenmerken) sections.

How to use it

Fetch a single Funda listing (woning) by numeric listing id or a listing URL. Returns one item with id, global_id, url, object_type, offering_type, status, is_sold_or_rented, labels, address (street, house_number, postcode, city, neighbourhood, province, country), description, blikvanger (promo headline), price (numeric), price_label (formatted asking/rental price string), living_area_m2, volume_m3, room_count, bedroom_count, energy_label, build_year, coordinates [lat, lng], publication_date, views, saves, images, agent (id, association), neighbourhood (city, name, inhabitants, families_with_children, average_asking_price_per_m2), sale_history (offered_since, sale_date, days_on_market — populated for sold/rented listings) and feature_sections (grouped label/value characteristics: Overdracht, Bouw, Indeling, Energie, Buitenruimte, VvE checklist, etc).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Funda listing id or a listing URL containing it (examples: "44479270", "https://www.funda.nl/detail/koop/amsterdam/appartement-rhijnvis-feithstraat-28-a/44479270/"; minLength: 1)

Response

• @type string (default: "FundaListing")
• id string required
• global_id string nullable
• url string nullable
• object_type string nullable
• offering_type string nullable
• status string nullable
• is_sold_or_rented boolean nullable
• labels array (default: [])
• address object nullable
  • @type string (default: "FundaListingAddress")
  • street string nullable
  • house_number string nullable
  • postcode string nullable
  • city string nullable
  • neighbourhood string nullable
  • province string nullable
  • country string nullable
• description string nullable
• blikvanger string nullable
• price integer nullable
• price_label string nullable
• living_area_m2 integer nullable
• volume_m3 integer nullable
• room_count integer nullable
• bedroom_count integer nullable
• energy_label string nullable
• build_year integer nullable
• coordinates array (default: [])
• publication_date string nullable
• views integer nullable
• saves integer nullable
• images array (default: [])
• agent object nullable
  • @type string (default: "FundaListingAgent")
  • id string nullable
  • association string nullable
• neighbourhood object nullable
  • @type string (default: "FundaNeighbourhood")
  • city string nullable
  • name string nullable
  • inhabitants integer nullable
  • families_with_children number nullable
  • average_asking_price_per_m2 integer nullable
• sale_history object nullable
  • @type string (default: "FundaListingSaleHistory")
  • offered_since string nullable
  • sale_date string nullable
  • days_on_market string nullable
• feature_sections array (default: [])
  • @type string (default: "FundaListingFeatureSection")
  • features array (default: [])
    • @type string (default: "FundaListingFeature")
    • label string nullable
    • value 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 — Listing not found (well-formed but nonexistent listing id) 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.