Property Skip Tracing — Address to People Lookup avatar

Property Skip Tracing — Address to People Lookup

Pricing

from $100.00 / 1,000 skip trace matches

Go to Apify Store
Property Skip Tracing — Address to People Lookup

Property Skip Tracing — Address to People Lookup

Paste a US property address ("123 Main St, Dallas, TX 75201") and get the people on it: phones, emails, mailing address, absentee flag, relatives. One row per person. Pay only when an address matches. Complements name/phone/email skip-trace. Lawful B2B — not for FCRA.

Pricing

from $100.00 / 1,000 skip trace matches

Rating

0.0

(0)

Developer

Muhamed Didovic

Muhamed Didovic

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 hours ago

Last modified

Share

Property Skip Tracing — Address to People Lookup 🏠🔎

Turn a US property address into named leads in seconds. Submit a street address and get back the people connected to it — current and former residents, with age, current city, prior locations, and reported relatives. Built for wholesalers, real-estate investors, title researchers, and B2B due-diligence teams who start from a property list, not a name.

You pay only when an address returns people — blank lookups are never charged.

How it works

How Property Skip Tracing works

✨ Why use this Actor?

  • Address-first by design. Pass street + citystatezip and get everyone associated with that address — no need to know a name first.
  • Pay only on matches. The SkipTraceMatch event fires once per address that returns at least one person. Empty lookups cost nothing beyond the run start.
  • One row per person. Output is flat and denormalized with the input address — drop it straight into a CSV, Google Sheet, or dialer with no joins.
  • Single, bulk, or file input. One address, an array of addresses, or a public CSV/TXT URL — no custom plumbing.
  • Built-in deduplication. The same person appearing more than once is removed automatically.
  • HTML run report. Match rate, per-address breakdown, and the lawful-use reminder, saved to the run's key-value store.
  • Standard Apify exports. JSON, CSV, Excel, plus a webhook to push each record to Zapier / Make / GoHighLevel.

🎯 Use cases

You are a…Use it to…
Wholesaler / real-estate investorTurn a distressed-property list into named leads for cold outreach
Owner-occupancy checkerSee who currently lives at a property — spot likely-absentee owners for direct mail
Title / probate researcherPull current and former occupants for genealogy / probate context
B2B due-diligence / fraud analystCross-check who is associated with a registered business address
Process server / investigatorConfirm the people tied to an address before lawful service

📥 Supported inputs

InputExampleReturns
Addresses (one-line)["3828 Double Oak Ln, Irving, TX 75061"]People connected to each address
Single address (split)street: "3828 Double Oak Ln", citystatezip: "Irving, TX 75061"Same lookup, two boxes
Bulk addresses[{ street, citystatezip }, …]People for each address, one row per person
Addresses from URLhttps://example.com/leads.csvPeople for every row of a two-column CSV/TXT
Direct URL (advanced)https://thatsthem.com/address/3828-Double-Oak-Ln-Irving-TX-75061Scraped verbatim and parsed the same way

Not supported: international addresses (US-only), records behind a login, and any premium "unlock"-gated report pages.

🔄 How it works

  1. Build the lookup URL from each address you submit.
  2. Fetch the result page with a single HTTP request (impit + sliding-window concurrency for bulk lists; automatic anti-bot bypass when needed).
  3. Parse the JSON-LD person graph embedded in the page.
  4. Dedupe people and extract each person's name, age, current + prior cities, and reported relatives.
  5. Charge once per matched address, then push one row per person to the dataset (capped at your maxItems).

⚙️ Input parameters

FieldTypeDescription
addressesarrayFull one-line US addresses (123 Main St, Dallas, TX 75201). Same paste format as other property skip-trace tools.
streetstringUS street address line (optional if addresses is set).
citystatezipstringCity, ST ZIP (optional if addresses is set).
includePhonebooleanDeliver phones. Default true.
includeEmailbooleanDeliver emails. Default true.
bulkAddressesarrayArray of { street, citystatezip } objects.
addressesFromUrlstringPublic CSV/TXT URL with two columns: street, citystatezip.
startUrlsarrayDirect thatsthem.com URLs, scraped as-is (advanced).
webhookUrlstringEach person record is POSTed here as JSON as it's found. Best-effort.
deepSearchbooleanRetry unmatched addresses against a secondary public-records source before giving up. Default true.
includeContactsbooleanDeliver full phone numbers & emails on each row (billed per person that has them). Default true.
demoModebooleanReturn one sample record with no lookup and no charge. Default false.
maxItemsintegerHard cap on person records returned. Default 1000.
maxConcurrencyintegerHow many addresses to fetch in parallel. Default 8.

📊 Output overview

The dataset contains one row per person connected to the input address. Every row is denormalized with the inputStreet and inputCityStateZip you submitted, so the file is ready for CSV / Sheet workflows with no joins. Fields the source doesn't have for a given person come back null rather than guessed.

📦 Output sample

{
"inputStreet": "3828 Double Oak Ln",
"inputCityStateZip": "Irving, TX 75061",
"name": "Matthew B. Webb",
"personId": "Matthew-B-Webb",
"age": 40,
"livesIn": "Keller, TX",
"usedToLiveIn": "Dallas, TX",
"relatedTo": "Jeffery M. Webb, Sherry L. Webb, Haley M. Webb",
"phones": null,
"emails": "webbmb@hotmail.com",
"profileUrl": "https://thatsthem.com/name/Matthew-B-Webb",
"page": 1,
"scrapedAt": "2026-07-22T21:04:18.270Z"
}

🗂 Key output fields

FieldTypeNotes
inputStreetstringStreet address you submitted (denormalized on every row)
inputCityStateZipstringCity/state/ZIP you submitted
namestringFull name of the connected person
personIdstringStable identifier derived from the source profile
ageinteger | nullReported age when available
livesInstring | nullMost recent city/state of residence
usedToLiveInstring | nullPrior cities/states, comma-separated
relatedTostring | nullReported relatives / associates, comma-separated
phonesstring | nullFull phone numbers, comma-separated (with includeContacts)
emailsstring | nullFull email addresses, comma-separated (with includeContacts)
profileUrlstringPublic profile URL on the source
pageintegerResult page index (single-hop, always 1)
scrapedAtstringISO timestamp of the scrape

💰 Pricing

Pay-per-event, match-only:

  • Actor start — a small fixed charge once per run.
  • SkipTraceMatch — charged only when an address returns at least one person. Empty lookups are not charged.
  • ContactInfo — charged only per delivered person who actually has a phone number or email on file (people without contact data are free). Turn includeContacts off to skip both the fields and the charge.

There's also a free demo mode (demoMode: true) that returns a sample record with no lookup and no charge, so you can preview the exact output shape before scaling.

❓ FAQ

Where does the data come from? The Actor reads publicly available people-search content and returns the people the source associates with an address. Profile URLs in each record link back to the source.

What if no people are returned for an address? With deepSearch on (the default), an unmatched address is automatically retried against a secondary public-records source before giving up. If both come up empty, you're not charged the match event for it. The run-start charge still applies once per run.

Why do some addresses return people who don't live there now? Public records list everyone historically associated with an address — current owner, previous tenants, and their relatives. Use livesIn / usedToLiveIn to filter.

Are international addresses supported? No — US addresses only.

Can I bulk-process a list? Yes. Use bulkAddresses for an array, or addressesFromUrl for a two-column CSV/TXT.

Can I use this to deny someone housing, credit, or a job? No. This Actor is not a consumer reporting agency and is not FCRA-regulated — see the Disclaimer.

💬 Support

Found a missing field or an address that didn't parse? Open an issue from the Actor's Issues tab on Apify with the input you used.

🔎 Explore more scrapers

Need name / phone / email lookups too? Try the companion Skip Trace — People, Phone & Address Finder for reverse lookups by any identifier, plus full unmasked phone numbers and address history. Browse the developer's other people-data and lead-generation Actors on the Apify Store.

🤖 For AI Agents & LLM Apps

Compact reference for agents calling this actor via the Apify MCP server or the Apify API (memo23/property-skip-tracing).

Purpose: US address → people on that property (current + former residents). One dataset row per person, stamped with the input address.

Minimal input:

{ "addresses": ["3828 Double Oak Ln, Irving, TX 75061"], "maxItems": 5 }

Output: inputStreet, inputCityStateZip, propertyAddress, name / ownerFullName, age, livesIn, usedToLiveIn, relatedTo / relatives[], phones / phoneNumbers[], emails / emailAddresses[], ownerMailingAddress, isAbsentee, lookupStatus (contact or name_only), profileUrl, sourceUrl, scrapedAt.

Behaviors an agent should know:

  • Prefer addresses (one-line strings). street + citystatezip still work.
  • Always set maxItems. One address can return many people; each row is a person, not an address.
  • Empty addresses are not billed the match event. includePhone / includeEmail default true.
  • US only. Not for FCRA decisions.

⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Zillow Group, ThatsThem, TruePeopleSearch, or any consumer reporting agency. Brand and source names are used solely descriptively to identify the public data the Actor reads. All trademarks are the property of their respective owners.

Lawful B2B use only. This Actor returns information about individuals derived from public records. It is NOT a consumer reporting agency and its output is NOT a "consumer report" under the U.S. Fair Credit Reporting Act (FCRA). You may not use any output — directly or indirectly — as a factor in establishing a person's eligibility for credit or insurance, employment, housing or tenant screening, or any other purpose covered by Section 604 of the FCRA (15 U.S.C. § 1681b). You are also responsible for compliance with all applicable privacy laws (CCPA/CPRA, VCDPA, CPA, GDPR, DPPA, GLBA, and any sector-specific regulations). If you are unsure whether your use is permitted, consult qualified legal counsel.


SEO Keywords

property skip tracing, skip tracing scraper, address to owner lookup, owner lookup by address, real estate skip trace, wholesaler skip tracing, absentee owner finder, address to people lookup, reverse address lookup, people search by address, distressed property leads, real estate lead generation, resident lookup, current and former residents, relatives lookup, probate research, title research, b2b due diligence address, thatsthem scraper, apify skip trace, pay per match skip tracing, us address people finder