Trulia: scrapers and the official API, compared

Route map

Each line is one way to get Trulia data; each stop is a field you probably need. Green lines are catalogue Actors, ranked by the published formula.

Field matrix: who returns what

Every tool with a published output schema, against the 7 fields most Trulia jobs need. A dot means the field name appears in the schema; rows can still leave it empty.

Field dictionary: the exact keys

The same core field has a different key in each Actor's output. Map these before you merge datasets; a dash means the published schema has no matching key. Need a field that is not listed here, such as email? Search every Trulia Actor by field.

All 9 tools, scored

Catalogue Actors link to their detail pages; the score (0 to 100) is the published formula, identical for every tool. Other Store tools follow in their own table, for reference. Price is the published primary-result rate per 1,000 (the Free-plan rate where the price is tiered; higher Apify plans pay less); start events and platform usage are excluded.

Other Store tools, for reference

Scored with the same published formula and listed for comparison only; this site does not link or recommend them.

Official API route

Terms and personal data

Trulia is covered by the Zillow Terms of Use; listing data carries broker and MLS rights. This is general information, not legal advice.

Read Trulia's terms. Keep to public data, do not bypass logins or access controls, and check whether personal data is involved before you collect it. The can-I-scrape checklist walks through it.

How to start

1. Open Trulia Listings & Price History Scraper and start from its default input; its Actor page has the full example input and code.
2. Set the Trulia search, profile, listing or URL you need and a result limit.
3. Run it and export the dataset as JSON, CSV or Excel, or call it from the Apify API.

Call Trulia Listings & Price History Scraper from code

The example input uses the Actor's published defaults; set your own Trulia query before you run it. You need an Apify API token.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "mode": "search",
    "location": "Austin, TX",
    "listingType": "for_sale",
    "propertyType": "any",
    "maxItems": 3,
    "fetchDetails": False,
    "urls": []
}

run = client.actor("vexaloom-labs/trulia-listings-and-price-history-scraper").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "mode": "search",
    "location": "Austin, TX",
    "listingType": "for_sale",
    "propertyType": "any",
    "maxItems": 3,
    "fetchDetails": false,
    "urls": []
};

const run = await client.actor("vexaloom-labs/trulia-listings-and-price-history-scraper").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~trulia-listings-and-price-history-scraper/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"mode":"search","location":"Austin, TX","listingType":"for_sale","propertyType":"any","maxItems":3,"fetchDetails":false,"urls":[]}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=vexaloom-labs/trulia-listings-and-price-history-scraper",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Questions people ask

More on Trulia

• Topic groupReal estate data: every website compared
• ToolWhich Trulia route fits your job?
• ToolTrulia cost by Apify plan, rows and runs

Related websites

• Zillow8 Actors
• Realtor.com1 Actor
• Redfin1 Actor

Sources

• Trulia Listings & Price History Scraper on Apify Store
• No official Trulia data API documentation
• Trulia terms