# Casas y Terrenos Scraper — Mexican rentals & sales (`maingaon/casasyterrenos-scraper`) Actor

Scrape casasyterrenos.com rentals and sales by city: MXN price, rooms, area, colonia, ad ID and URL. Optional detail mode adds street address, exact coordinates and photos. Structured JSON, no login, per-result pricing.

- **URL**: https://apify.com/maingaon/casasyterrenos-scraper.md
- **Developed by:** [Mike Major](https://apify.com/maingaon) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Casas y Terrenos Scraper

Pulls rental and sale listings from [casasyterrenos.com](https://www.casasyterrenos.com), one of
Mexico's longest-running property portals. Runs by state and municipality and walks the result pages
until `maxItems` or the end of the list.

Output is structured records, not page text: price in MXN, rooms, area, neighbourhood, and — with
`fetchDetails` on — street address, exact coordinates and the listing image.

### Why

Mexican rental data is scattered and expensive to collect by hand. `casasyterrenos` alone carries
hundreds of thousands of live ads across 30 years of agency relationships. Agencies price against it,
landlords benchmark it, proptech and valuation teams map it, relocation services filter it.

### Output

One record per listing, about 20 per page.

| Field | Meaning |
|---|---|
| `title` | Listing headline as published |
| `price` | Displayed price, e.g. `$38,000` |
| `currency` | `MXN` |
| `priceMxn` | Numeric price, no formatting |
| `bedrooms` / `bathrooms` | Counts, null when unstated |
| `areaM2` | Floor area in m², null when unstated |
| `colonia` | Neighbourhood — from the detail page when `fetchDetails`, otherwise a title hint |
| `streetAddress` | Street and number — `fetchDetails` only |
| `locality` | Municipality as recorded on the listing — `fetchDetails` only |
| `region` | State code — `fetchDetails` only |
| `lat` / `lng` | Exact coordinates — `fetchDetails` only |
| `imageUrl` | Main listing image — `fetchDetails` only |
| `adId` | Site ad identifier, unique per listing |
| `url` | Listing URL |
| `operation` | `renta` or `venta` |
| `municipality`, `state` | Echo of the input |
| `scrapedAt` | ISO timestamp |

### Input

- `state` and `municipality` — the site's own URL slugs, e.g. `df` / `benito-juarez`, or `jalisco` / `guadalajara`.
- `operation` — `renta` (rent) or `venta` (sale).
- `propertyType` — path segment, `departamentos` by default and the best populated.
- `maxItems` — hard cap, 200 default.
- `fetchDetails` — off by default. Adds one request per listing for address, coordinates and image.
  Roughly doubles runtime; turn it on when you need mapping or drive-time, off when you only need the list.

### Pricing

Pay per result. About $1.10 per 1,000 listings (dataset item plus listing event), with a small
per-run start charge. Platform usage is absorbed here, so your bill is the price and nothing else.

With `fetchDetails` expect a run to take roughly twice as long for the same row count.

### Limits

- Fields mirror what advertisers publish; rooms and area are null when they omit them.
- `colonia` from the title is a hint. Turn on `fetchDetails` if neighbourhood accuracy matters.
- Municipality slugs are the site's own — check the portal before composing an input.
- Detail requests are throttled; very large `maxItems` with `fetchDetails` will run for minutes.

# Actor input Schema

## `state` (type: `string`):

URL slug of the state, e.g. `df`, `jalisco`, `nuevo-leon`.

## `municipality` (type: `string`):

URL slug of the municipality, e.g. `benito-juarez`, `guadalajara`.

## `operation` (type: `string`):

`renta` for rentals, `venta` for sales.

## `propertyType` (type: `string`):

Path segment used by the site. `departamentos` is the default and the best populated.

## `maxItems` (type: `integer`):

Hard cap on records. 20 per page is typical.

## `proxyConfiguration` (type: `object`):

Optional. Datacenter proxies are enough for this site.

## `fetchDetails` (type: `boolean`):

Fetch each listing page and add street address, colonia, region, exact coordinates and image URL. One extra request per listing, roughly doubles runtime.

## Actor input object example

```json
{
  "state": "df",
  "municipality": "benito-juarez",
  "operation": "renta",
  "propertyType": "departamentos",
  "maxItems": 200,
  "fetchDetails": false
}
```

# Actor output Schema

## `listings` (type: `string`):

One record per listing: title, price in MXN, bedrooms, bathrooms, area, colonia, ad ID, URL.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("maingaon/casasyterrenos-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("maingaon/casasyterrenos-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call maingaon/casasyterrenos-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maingaon/casasyterrenos-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/uomdhqIg6aL51Xaeo/builds/TdzaYfskOauemeIpt/openapi.json