/funda/agents

POST /api/funda/agents

Price: 5 credits

Get a Funda real estate agent (makelaar) by agent id or agent URL: name, affiliation, slogan and description, contact details (email, phone, website), office address, logo, rating, review count, selectivity, services, specialties, certificates, languages, opening hours, social media links, employees and recent reviews.

How to use it

Fetch a single Funda agent (makelaar/office) by numeric agent id or an agent URL. Returns one item with id, name, association, page_type, slogan, description, short_description, email, phone, website_url, address (street, house_number, postcode, city), image (logo), geo_identifier, has_listings, rating, review_count, selectivity_percentage, services, specialties, certificates (NWWI, VastgoedCert, NRVT, WFT, ...), languages, opening_hours (day, by_appointment, times), facebook_url, instagram_url, linkedin_url, employees (name, function, image) and reviews (posted_at, transaction_type, average_score, text).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• agent string required — Funda agent (makelaar) id or an agent URL containing it (examples: "24607", "https://www.funda.nl/makelaar/24607-krk-makelaars-amsterdam/"; minLength: 1)

Response

• @type string (default: "FundaAgent")
• id string required
• name string nullable
• association string nullable
• page_type string nullable
• slogan string nullable
• description string nullable
• short_description string nullable
• email string nullable
• phone string nullable
• website_url string nullable
• address object nullable
  • @type string (default: "FundaAgentAddress")
  • street string nullable
  • house_number string nullable
  • postcode string nullable
  • city string nullable
• image string nullable
• geo_identifier string nullable
• has_listings boolean nullable
• rating number nullable
• review_count integer nullable
• selectivity_percentage integer nullable
• services array (default: [])
• specialties array (default: [])
• certificates array (default: [])
• languages array (default: [])
• opening_hours array (default: [])
  • @type string (default: "FundaAgentOpeningHours")
  • day string nullable
  • by_appointment boolean nullable
  • times array (default: [])
    • @type string (default: "FundaAgentOpeningTime")
    • begin string nullable
    • end string nullable
• facebook_url string nullable
• instagram_url string nullable
• linkedin_url string nullable
• employees array (default: [])
  • @type string (default: "FundaAgentEmployee")
  • name string nullable
  • function string nullable
  • image string nullable
• reviews array (default: [])
  • @type string (default: "FundaAgentReview")
  • posted_at string nullable
  • transaction_type string nullable
  • average_score number nullable
  • text 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 — Agent not found (well-formed but nonexistent agent 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.