# Trulia Scraper (`datascrapers/trulia-scraper`) Actor

Scrape Trulia for-sale, for-rent, and sold listings from search URLs or location queries, with optional property-page details.

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

## Pricing

from $2.20 / 1,000 listings

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

**Trulia Scraper** creates a structured dataset of property listings collected from Trulia. Each dataset item is one listing and can include the listing id, address, price, status, property type, beds, baths, living area, city, and URL. Query the source with a place name, ZIP code, or Trulia URL, choose for sale, for rent, or sold, optionally open the property page, limit results with `maxListings`, and retrieve records through the Apify Dataset API or export them as JSON, CSV, Excel, XML, or another supported format.

[![Trulia Scraper — input to structured data](https://raw.githubusercontent.com/faizanalii/apify-actor-assets/main/trulia-scraper/trulia-scraper-value-demo.gif)](https://apify.com/datascrapers/trulia-scraper)

### Dataset at a glance

| Property | Value |
|---|---|
| Source | Trulia |
| Record unit | One listing |
| Input methods | `searchQueries`, `startUrls` |
| Main identifiers | `listingId`, `url` |
| Delivery | Apify Dataset and API |
| Export formats | JSON, CSV, Excel, XML, and other Apify dataset exports |
| Update model | Fresh records per Actor run |
| Pricing | $2.50 per 1,000 listings on the Free plan |

### Coverage and available records

`searchQueries` accepts places such as `Austin, TX` and ZIP codes. `searchType` applies to those queries and is `FOR_SALE`, `FOR_RENT`, or `SOLD`. Start URLs already encode for-sale, for-rent, or sold, so `searchType` does not rewrite them.

`includeListingDetails` adds property-page fields such as description, photo list, features, and price history when the page is fetched. `detailConcurrency` controls how many detail pages are requested at once. `maxListings` caps listings across every query and URL. `0` means no cap.

The Actor collects listings returned for that search. It does not collect off-market history beyond the sold search type, and it does not collect agent reviews.

### Data dictionary

| Field | Type | Nullable | Description | Example |
|---|---|---:|---|---|
| listingId | string | No | Listing key used for deduplication | 455106024_ZPID |
| url | string | No | Trulia listing URL | https://www.trulia.com/builder-community-plan/easton-park-plan-torres-455106024 |
| address | string | Yes | Display address | Plan Torres in Easton Park, Austin, TX 78744 |
| city | string | Yes | City | Austin |
| state | string | Yes | State | TX |
| zipCode | string | Yes | ZIP code | 78744 |
| neighborhood | string | Yes | Neighborhood | Bluff Springs |
| formattedPrice | string | Yes | Display price | $615,990+ |
| price | number | Yes | Numeric price | 615990 |
| status | string | Yes | Listing status | for sale |
| propertyType | string | Yes | Property type | single-family home |
| listingType | string | Yes | Listing type | BUILDER_PLAN |
| bedrooms | number | Yes | Bedroom count | 4.0 |
| bathrooms | number | Yes | Bathroom count | 3.0 |
| livingArea | string | Yes | Living area | 2,551 sqft |
| detailsFetched | boolean | Yes | Whether the property page was opened | true |
| sourceQuery | string | Yes | Query that found the listing | Austin, TX |

### Example dataset record

```json
{
  "listingId": "455106024_ZPID",
  "url": "https://www.trulia.com/builder-community-plan/easton-park-plan-torres-455106024",
  "listingType": "BUILDER_PLAN",
  "status": "for sale",
  "propertyType": "single-family home",
  "address": "Plan Torres in Easton Park, Austin, TX 78744",
  "city": "Austin",
  "state": "TX",
  "zipCode": "78744",
  "neighborhood": "Bluff Springs",
  "formattedPrice": "$615,990+",
  "price": 615990,
  "currency": "USD",
  "bedrooms": 4.0,
  "bathrooms": 3.0,
  "livingArea": "2,551 sqft",
  "yearBuilt": 2026,
  "detailsFetched": true,
  "sourceQuery": "Austin, TX"
}
```

### Query and input reference

| Field | Required | Description |
|---|---|---|
| searchQueries | No | City, neighborhood, or ZIP searches |
| startUrls | No | Trulia search or listing URLs |
| searchType | No | `FOR_SALE`, `FOR_RENT`, or `SOLD`. Default `FOR_SALE`. Applies to search queries |
| maxListings | No | Maximum listings. `0` means no cap |
| includeListingDetails | No | Open property pages and charge `listing-details` when details are fetched |
| detailConcurrency | No | Parallel property-page requests |
| proxyConfiguration | No | Apify proxy settings. Residential is the usual choice |

Provide a search query or a start URL.

### Retrieve the data through the API

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("datascrapers/trulia-scraper").call(run_input={
    "searchQueries": ["Austin, TX"],
    "searchType": "FOR_SALE",
    "maxListings": 5,
    "includeListingDetails": True,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item.get("address"), item.get("formattedPrice"), item.get("listingId"))
```

### Data quality and record handling

Deduplicate on `listingId`. `url` is a second stable identifier. `detailsFetched` is false when the card was saved without a property page, so description, photos, and features are absent on those rows. Each run writes a new dataset.

### Pricing and cost examples

Pay per event. Prices are per 1,000 events. Platinum and Diamond use the Gold rate. Platform usage is billed separately.

| Event | Free | Bronze | Silver | Gold |
|---|---:|---:|---:|---:|
| listing | $2.50 | $2.40 | $2.30 | $2.20 |
| listing-details | $2.50 | $2.40 | $2.30 | $2.20 |

A Free-plan run that saves 1,000 listing cards costs $2.50, plus platform usage. Each property page that is fetched adds one `listing-details` event at the same rate. Leave `includeListingDetails` off when you only need the cards.

### Limitations and responsible data use

Search type applies to `searchQueries`, not to start URLs that already name a market. Builder plans and resale listings can share one search. Collect public listing fields only, and keep `maxListings` small on the first run.

### Dataset questions

#### What is one dataset item?

One Trulia listing.

#### Which field should I use to merge runs?

`listingId`.

#### When is listing-details charged?

Only when `includeListingDetails` is on and the property page is fetched.

### Related datasets from Data Scrapers

- [Daft.ie Scraper](https://apify.com/datascrapers/daft-ie-scraper) for Irish listings
- [Hemnet Scraper](https://apify.com/datascrapers/hemnet-se-scraper) for Swedish listings
- [Finn.no Scraper](https://apify.com/datascrapers/finn-no-scraper) for Norwegian homes
- [DAHLER Scraper](https://apify.com/datascrapers/dahler-scraper) for German listings

### Data Scrapers support

Questions about this dataset: stardustspotlight@gmail.com.

# Actor input Schema

## `startUrls` (type: `array`):

Trulia search or listing URLs. Search URLs keep any filters already in the path (beds, pets, property type, page) — e.g. https://www.trulia.com/for_sale/Austin,TX/ or https://www.trulia.com/for_rent/Austin,TX/4p_beds/cats_pets/. Listing URLs (/home/ or /building/) scrape that property.

## `searchQueries` (type: `array`):

Location queries used when you do not have a URL — e.g. "Austin, TX", "Austin TX", or a 5-digit ZIP. Combined with Search type to build a Trulia search URL.

## `searchType` (type: `string`):

Market applied to searchQueries only. Start URLs already encode for-sale, for-rent, or sold.

## `maxListings` (type: `integer`):

Maximum listings to scrape (0 = unlimited). Enforced across all URLs and queries.

## `includeListingDetails` (type: `boolean`):

When enabled, open each property page for description, photos, agent, price history, and features. Charges the listing-details event in addition to listing. Property pages run in parallel and each uses a rotated residential proxy.

## `detailConcurrency` (type: `integer`):

How many property pages to fetch at the same time when listing details are enabled. Each request uses a new proxy session.

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

Residential proxies are recommended. Trulia may show a press-and-hold check on some IPs; the Actor rotates and retries.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.trulia.com/for_sale/Austin,TX/"
    }
  ],
  "searchQueries": [
    "Austin, TX"
  ],
  "searchType": "FOR_SALE",
  "maxListings": 10,
  "includeListingDetails": false,
  "detailConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset containing scraped Trulia listings

## `runStats` (type: `string`):

Record counts and timestamps for this run

# 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 = {
    "startUrls": [
        {
            "url": "https://www.trulia.com/for_sale/Austin,TX/"
        }
    ],
    "searchQueries": [
        "Austin, TX"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("datascrapers/trulia-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 = {
    "startUrls": [{ "url": "https://www.trulia.com/for_sale/Austin,TX/" }],
    "searchQueries": ["Austin, TX"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("datascrapers/trulia-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 '{
  "startUrls": [
    {
      "url": "https://www.trulia.com/for_sale/Austin,TX/"
    }
  ],
  "searchQueries": [
    "Austin, TX"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call datascrapers/trulia-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datascrapers/trulia-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/K2uO1iOBzJbWbdfKQ/builds/IaFhQyxiUqNNmVBfb/openapi.json