Encuentra24 Scraper — Central America Property & Cars

Scrape Encuentra24 across Panama, Costa Rica, Nicaragua, El Salvador, Guatemala and Honduras: price and price per m², area, rooms, bathrooms, coordinates, advertiser name, licence and phone. Property, cars and jobs. Keyless. JSON, CSV or Excel.

---

What does the Encuentra24 Scraper do?

This Actor turns Encuentra24 into a structured dataset you can actually work with. You give it a search, it walks the result pages, and it writes one clean row per record into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

It runs on plain HTTP with no browser and no login, which keeps it fast and cheap, and it works the same on a free account as on a paid one. Every field documented below came from a real verification run of this Actor, so what you read here is what you get.

The current build returns 39 populated fields per record, of which 32 are present on virtually every row.

Who is it for?

• Analysts who need Encuentra24 data as a spreadsheet instead of a browser tab.
• Operations and research teams tracking how Encuentra24 listings change over time.
• Developers wiring a live data feed into an internal tool or database.
• Growth and sales teams building prospect and market lists from public data.
• AI teams assembling structured training or grounding data.

Use cases

• Export a full Encuentra24 search into a spreadsheet for analysis.
• Track how prices, volumes or availability move week over week by scheduling the run.
• Feed a dashboard or internal database with a repeatable, structured source.
• Build a market map by running several searches in one job.
• Enrich an existing list by matching on the identifiers in the output.

Why use this Encuentra24 Scraper?

• 🔑 No API key and no login — nothing to authenticate, nothing to expire.
• 📦 39 verified fields — every column below was confirmed against live output.
• 📄 Real pagination — it walks the result set instead of returning the first screen.
• 🎯 Bounded runs — caps in the input stop the job exactly where you want, so the bill is predictable.
• 💸 Tiered pay-per-result — you pay per row, and higher Apify plans pay less per row.
• 📊 Export anywhere — JSON, CSV, Excel, HTML, the API, or any Apify integration.

What data can you extract?

One row per record. These columns come from a live run, with the share of rows that carried a value:

Field	Type	Typically filled	Description
address	string	100%	Address
advertiserId	string	100%	Advertiser id
advertiserName	string	100%	Advertiser name
advertiserType	string	100%	Advertiser type
areaSqm	number	100%	Area sqm
bathrooms	number	100%	Bathrooms
contactPhone	string	100%	Contact phone
contactWhatsapp	string	100%	Contact whatsapp
currency	string	100%	Currency
dateCreated	string	100%	Date created
dateUpdated	string	100%	Date updated
description	string	100%	Description
featuredLevel	string	100%	Featured level
imageCount	number	100%	Image count
imageUrl	string	100%	Image url
isActive	boolean	100%	Is active
isVerifiedAdvertiser	boolean	100%	Is verified advertiser
latitude	number	100%	Latitude
listingId	string	100%	Listing id
listingUrl	string	100%	Listing url
locality	string	100%	Locality
longitude	number	100%	Longitude
mainCategory	string	100%	Main category
parking	string	100%	Parking
priceAmount	number	100%	Price amount
pricePerSqm	number	100%	Price per sqm
rooms	number	100%	Rooms
scrapedAt	string	100%	Scraped at
source	string	100%	Source
subCategory	string	100%	Sub category
title	string	100%	Title
vertical	string	100%	Vertical
advertiserCompany	string	72%	Advertiser company
advertiserLicense	string	65%	Advertiser license
ageLabel	string	65%	Age label
floor	string	25%	Floor
lotSizeSqm	number	72%	Lot size sqm
petFriendly	string	15%	Pet friendly
swimmingPool	string	75%	Swimming pool

Fields below 90% are genuinely optional at the source — Encuentra24 does not publish them for every record. An empty value means the source did not show it, not that extraction failed.

How to use

1. Open the Actor and fill in the search fields — the defaults below are a working example.
2. Set the result cap so the run stops where you want it.
3. Click Start, then export from the Output tab or pull the dataset through the API.

{
  "market": "panama-es",
  "category": "bienes-raices-venta-de-propiedades-apartamentos",
  "maxResults": 500,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Input parameters

Parameter	Type	Default	Description
market	string	panama-es	Which Encuentra24 country site to scrape.
category	string	bienes-raices-venta-de-pro	Which Encuentra24 category to list.
categoryPathOverride	string	–	Optional.
maxResults	integer	500	Stop after this many listings.
proxyConfiguration	object	–	Encuentra24 streams its listings into the page; the default datacenter proxy is enough.

Tips for best results

• Broad searches return the deepest result sets; very narrow ones run out after a page or two.
• Use the result cap rather than the page cap when you want a predictable bill.
• Schedule the same input daily or weekly to build a history instead of a one-off snapshot.
• Lower the concurrency if you see retries — the source rate-limits aggressive crawling.
• Run several searches in one job instead of one search with a huge page count.
• Empty optional fields are normal; filter on the columns that matter to you after export.
• Deduplicate on the identifier column if you merge several runs together.
• Keep the proxy setting on the default unless the source blocks your region.

Integrations

Push results straight into Google Sheets, Slack, Zapier, Make, Airtable or any Webhook. You can also schedule the Actor and have each run append to the same dataset, which is how you turn a single export into a time series.

API usage

Replace <YOUR_TOKEN> with your Apify API token.

cURL

curl -X POST "https://api.apify.com/v2/acts/logiover~encuentra24-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"market": "panama-es", "category": "bienes-raices-venta-de-propiedades-apartamentos", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true}}'

Python

from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/encuentra24-scraper').call(run_input={"market": "panama-es", "category": "bienes-raices-venta-de-propiedades-apartamentos", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true}})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/encuentra24-scraper').call({"market": "panama-es", "category": "bienes-raices-venta-de-propiedades-apartamentos", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true}});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Use with AI agents (MCP)

This Actor is reachable through the Apify MCP server, so an AI agent can call it as a tool. Point the agent at https://mcp.apify.com and ask it something like "pull the first 200 jobs from Encuentra24 and summarise them" — it receives the same structured rows you would get from the UI.

FAQ

Do I need a Encuentra24 account or API key?

No. The Actor reads publicly available pages only. There is nothing to authenticate and no credentials to rotate.

Does it work on the free plan?

Yes. Every feature is available on a free Apify account — nothing is gated behind a paid tier. Pricing is per result, and higher plans simply pay less per row.

How many jobs can I get in one run?

As many as the search exposes. Raise the page and result caps together; the run stops at whichever limit it reaches first.

Why did I get fewer rows than I asked for?

The search ran out of records. That is normal for narrow queries — broaden the search or add more searches to one run.

Why are some fields empty?

Encuentra24 does not publish every attribute for every record. The table above shows how often each field is filled in practice.

What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two.

Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset.

Does it use a proxy?

It routes through Apify Proxy by default. You can switch groups or supply your own proxies in the input.

Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

How often is the data refreshed?

Every run reads the live source. There is no cache, so the data is as current as the website itself.

What if the site changes its layout?

Open an issue on the Issues tab and it gets fixed — the Actor is actively maintained.

Is it legal?

This Actor reads only publicly available pages on Encuentra24 — the same content any visitor sees without logging in. It does not bypass authentication and does not collect private data. You remain responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved.

This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Encuentra24; Encuentra24 and all other trademarks mentioned here are the property of their respective owners.

Related scrapers

Other Actors from the same collection:

• Dubizzle
• Gumtree
• Finn.no
• Immoweb

How much Encuentra24 data can you extract in one run?

A single run returned 920 listings in 244 seconds on the example input. That is roughly 226 listings a minute. Widen the search — more queries, more pages, a broader location — and the same run goes deeper.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Encuentra24 itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

📝 Changelog

2026-11-01

• Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
• README refreshed: independence disclaimer added.
• README refreshed: duplicate "Related scrapers" sections merged.

2026-10-15

• The prefilled example for maxResults is now 65 (was 200), so a first run finishes in about a minute and a half.
• Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
• A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
• A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
• Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
• Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.

2026-09-24

• Fixed runs that finished successfully with an empty dataset. A crawl that is blocked and a search that genuinely has no results both produce an empty file; the Actor now fails with an explicit NO_ROWS error and writes a SUMMARY record instead of reporting success.
• Diagnosis: Encuentra24 refuses datacenter IPs with HTTP 403.
• Proxy configuration now defaults to the UNBLOCKER group, which was measured fetching this source reliably where datacenter and residential IPs were refused.

2026-09-23

• Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
• Run reliability reviewed: 96.8% of public runs succeeded in the last 30 days.
• Input schema, output schema and pricing configuration reviewed.

2026-09-01

• Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
• Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
• No change to input, output fields or scraping logic.

2026-08-11

• Maintenance release: refreshed the build and dependencies.
• Re-verified live execution, non-empty structured output and dataset field/type integrity.
• Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.