/fotocasa/agencies/search

POST /api/fotocasa/agencies/search

Price: 5 credits

Search Fotocasa real estate agencies by province or municipality, optionally filtered by the offer type they publish (sale or rent). Returns agency cards with client id, name, alias, profile url, logo, the number of listings in the zone, the total number of published listings and the lowest published price.

How to use it

List Fotocasa real estate agencies (inmobiliarias) in a province or municipality. province is a province or municipality name ('Madrid', 'Barcelona'); offer_type selects venta (agencies that sell) or alquiler (agencies that rent). Each result has client_id (use it with fotocasa/agencies/listings), name, alias, url, image, listing_in_zone_count, listing_count and lowest_price.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• province string required — Province or municipality to list agencies in (examples: "Madrid", "Barcelona", "Valencia"; minLength: 1)
• offer_type string — Offer type the agency publishes (default: "venta"; one of: "venta", "alquiler")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "FotocasaAgency")
• client_id string required
• name string nullable
• alias string nullable
• url string nullable
• image string nullable
• listing_in_zone_count integer nullable
• listing_count integer nullable
• lowest_price integer 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 — No agencies found for the given province 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.