/pararius/agents/properties

POST /api/pararius/agents/properties

Price: 10 credits

List the current listings offered by a single Pararius agent (makelaar), by agent URL or city/slug pair and mode (rent or buy). Returns listing cards with address, price, living area, rooms, interior, photo and the listing detail url.

How to use it

List one Pararius agent's listings by agent URL or a city/slug pair (e.g. 'amsterdam/my-home-amsterdam') and mode (rent or buy). Each result has id, url, title, offering_type, postcode, city, district, price (numeric), price_label, living_area_m2, room_count, interior, is_highlighted, image and agent (name, alias, city, url).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• agent string required — Pararius agent (makelaar) URL, or a city/slug pair identifying the agent (examples: "https://www.pararius.com/real-estate-agents/amsterdam/my-home-amsterdam", "amsterdam/my-home-amsterdam"; minLength: 1)
• mode string — List the agent's rentals or properties for sale (default: "for_rent"; one of: "for_rent", "for_sale")
• count integer required — Max number of results to return (min: 1)
• city string (default: "")
• alias string (default: "")

Response

• @type string (default: "ParariusSearchListing")
• id string required
• url string nullable
• offering_type string nullable
• postcode string nullable
• city string nullable
• district string nullable
• price integer nullable
• price_label string nullable
• living_area_m2 integer nullable
• room_count integer nullable
• interior string nullable
• is_highlighted boolean nullable
• image string nullable
• agent object nullable
  • @type string (default: "ParariusSearchAgent")
  • name string nullable
  • alias string nullable
  • city string nullable
  • url 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 city/slug) 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.