TruePeopleSearch Scraper — People, Phone & Address Lookup

Turn a name, phone number, street address or email into a complete, structured US public-records person profile from TruePeopleSearch. Get the full name, age, current and previous addresses, phone numbers (with type, carrier and last-reported date), emails, aliases, relatives, associates and business connections — as clean JSON, CSV or Excel. No external API key, no ScrapFly, no Bright Data account required.

Built directly on the real TruePeopleSearch site with a stealth browser that clears the site's anti-bot protection on a US residential IP, so you get the full depth of a person's page — not a shallow summary.

---

Who uses this

You are…	You use it to…
Skip tracer / collections / process server	Locate hard-to-find people — current address, live phone numbers, relatives and associates.
Lead-gen agency / real-estate / sales	Enrich a list of names or property addresses with reachable phone numbers and contacts.
Investigator / researcher / fraud & risk	Run reverse-phone and reverse-address lookups; map aliases and associate networks.
PropTech / SaaS developer	Drop a stable people-lookup JSON into your app — no BYO scraping API, no captcha plumbing.

---

What you get — output fields

Each result is one person record:

Field	Type	Description
name	string	Full name
age	integer	Reported age
born	string	Approximate birth month/year
current_location	string	Current city, state
current_address	object	{ street, city_state_zip, url, details[] } — with property details (beds/sqft/value/dates) when shown
previous_addresses	array	Full previous-address history, each with details
primary_phone	string	Best / primary phone number
phones	array	Every phone — { number, type, carrier, last_reported, url }
emails	array	Email addresses (when present)
also_seen_as	array	Known aliases / alternate names
relatives	array	Possible relatives — { name, age, location, person_id, url }
associates	array	Possible associates
business_connections	array	Business connections
person_id / url	string	Stable TruePeopleSearch id and profile URL
search_type / query / enriched	—	Provenance: how the row was found and whether it is a full profile
scraped_at	string	ISO-8601 timestamp

Turn fetchDetails off for a fast, cheaper summary (name, age, city, "used to live in", "related to") straight from the results page.

---

High-value use cases

• Skip tracing — feed a debtor's last-known name or address; get their current address, active phone numbers and relatives to re-establish contact.
• Real-estate lead enrichment — turn a list of property addresses into owner names and phone numbers for direct-mail and cold-call outreach.
• Reverse-phone identification — resolve an unknown inbound number to a name, location and associated people.
• Investigations & due diligence — build an alias/associate graph around a subject from their public record.
• List hygiene / CRM enrichment — append current phone and address data to stale contact records.

---

Input parameters

Field	Type	Default	Description
searchType	enum	name	name, phone, address or email.
queries	string[]	[]	One lookup per entry. For name/address, scope to a location with a pipe: "James Smith | Austin, TX".
personUrls	string[]	[]	Direct /find/person/<id> URLs or ids — always returned with full detail.
fetchDetails	boolean	true	Fetch the full person profile per hit. Off = fast summary only.
maxItems	integer	50	Global cap on person records.
maxResultsPerQuery	integer	20	Per-query cap (paginated).
proxyProvider	enum	apify	apify (your Apify RESIDENTIAL) or massive (shared pool).
proxyCountry	string	US	Residential exit-IP country — keep US.
proxyConfiguration	object	Apify RESIDENTIAL US	Standard Apify proxy input.
headless	boolean	true	Run the stealth browser headless.

A US residential proxy is required. TruePeopleSearch hard-blocks datacenter IPs at the Cloudflare edge. The actor defaults to Apify Proxy Residential (US).

Example input

{
    "searchType": "name",
    "queries": ["James Smith | Austin, TX", "Maria Garcia | Miami, FL"],
    "fetchDetails": true,
    "maxItems": 50,
    "maxResultsPerQuery": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "US"
    }
}

Example output (one row, abridged)

{
    "search_type": "name",
    "query": "James Smith | Austin, TX",
    "enriched": true,
    "person_id": "pxxxxxxxxxxxxxxxxx",
    "url": "https://www.truepeoplesearch.com/find/person/pxxxxxxxxxxxxxxxxx",
    "name": "James Smith",
    "age": 61,
    "current_location": "New Braunfels, TX",
    "current_address": {
        "street": "123 N Sample St",
        "city_state_zip": "New Braunfels, TX 78130",
        "details": ["4 beds | 2,345 sq ft | built 1998", "Single Family"]
    },
    "primary_phone": "(830) 555-0100",
    "phones": [
        {
            "number": "(830) 555-0100",
            "type": "Wireless",
            "carrier": "…",
            "last_reported": "Jun 2026"
        }
    ],
    "relatives": [
        { "name": "John Smith", "age": 63, "location": "Houston, TX" }
    ],
    "associates": [{ "name": "Jane Doe", "age": 43, "location": "Austin, TX" }],
    "scraped_at": "2026-08-04T00:00:00+00:00"
}

---

Scheduling, webhooks & integrations

• Schedule runs (hourly/daily) from the Apify Console to keep a contact list fresh.
• Webhooks fire on run completion — push new records straight into your app.
• Export to JSON, CSV, Excel or feed Google Sheets, Make, Zapier, or S3 via the Apify integrations.
• API — start runs and read the dataset from the Apify API or the JS/Python clients.

Use it from an AI assistant (MCP)

This actor works as a tool for AI agents via the Apify MCP server. Point your MCP-compatible assistant (Claude, ChatGPT, VS Code, etc.) at Apify and it can call truepeoplesearch-scraper to look people up and reason over the structured results — reverse-phone identification, contact enrichment and skip tracing on demand.

---

FAQ

Do I need a TruePeopleSearch account or any API key? No. There's no login and no external service — the actor reads the public site directly. You only need an Apify account and a US residential proxy (Apify Proxy Residential is the default).

Why is a US residential proxy required? TruePeopleSearch blocks datacenter IPs at the Cloudflare edge. A US residential IP is needed to reach the site; the actor clears the DataDome / Cloudflare challenges automatically on that IP.

How fresh is the data? Every record is scraped live from TruePeopleSearch at run time — it reflects whatever the site shows at that moment, timestamped in scraped_at.

How complete are the profiles? With fetchDetails on (default) you get the full page: all phones (with type/carrier), current + previous addresses, relatives, associates, business connections, emails and aliases. Some fields (e.g. emails) are only present when TruePeopleSearch has them.

Can I just get a quick summary to save cost? Yes — set fetchDetails to false for name/age/city and "used to live in" / "related to" hints straight from the results page, without opening each profile.

What if a search returns no matches? The run finishes cleanly with zero rows for that query and moves on — it does not crash. Empty or mistyped queries are skipped.

Is scraping this legal? The actor collects publicly available information. You are responsible for using it lawfully. Do not use the output for FCRA-regulated purposes (credit, employment, insurance, tenant screening) or any use prohibited by TruePeopleSearch or applicable privacy law (e.g. CCPA). Intended for lawful B2B research, skip tracing and lead generation only.

A run failed or got blocked — what do I do? The actor auto-rotates residential IPs on a block. If runs still fail, use a premium US residential proxy pool and/or raise the run timeout. Persistent issues are reported to the maintainer automatically.