Real Estate Skip Trace — No Login, Owner Phones & Emails
Pricing
from $10.00 / 1,000 delivered skip-trace results
Real Estate Skip Trace — No Login, Owner Phones & Emails
Research public property-owner and contact evidence; missing contacts and inferred signals remain explicit. No login. Bulk export: JSON, CSV, Excel and API. PPE: from $10/1K research results; usage extra.
Pricing
from $10.00 / 1,000 delivered skip-trace results
Rating
0.0
(0)
Developer
Apivault Labs
Maintained by CommunityActor stats
0
Bookmarked
51
Total users
7
Monthly active users
23 days ago
Last modified
Categories
Features
Share
Real Estate Skip Tracing — Find Property Owner Phones & Emails

Find the owner behind a US property and get the contact and deal data needed to qualify the lead. Built for real estate wholesalers, investors, agents, acquisition teams, and property researchers.
Give it a US property address (or a whole list) and get back one record per property — owner, contacts, deal signals and a lead score — from public records, with no external API key or third-party subscription required for the standard workflow.
Use this real estate skip tracing Actor for bulk property owner lookup without supplying browser cookies or logging in to third-party sites. Run it manually, through the Apify API, on a schedule, or as part of an automation. Export successful records to JSON, CSV, Excel, or a webhook.
Quick start
- Open Input and paste one or more complete US addresses into Property addresses — recommended.
- Keep Skip trace owner phones & emails enabled.
- Click Start.
- Open the dataset and use Owner & Contact for outreach or Deal Signals for lead qualification. Export either view to CSV, Excel, or JSON.
Example input:
{"addresses": ["123 Main St, Springfield, IL 62704","2551 Pinebluff Dr, Dallas, TX 75228"],"skipTraceContacts": true,"detectAbsentee": true,"estimateEquity": true}
For better matches, always include the city, two-letter state, and ZIP. Leave all other search fields empty unless you intentionally want to combine modes.
What you get per property
- 👤 Owner name — an LLC/trust is pierced to the real person when possible
- 📞 Skip-traced phones — E.164-normalized, each enriched offline with line type (mobile / landline / VoIP / toll-free), carrier, validity and timezone, so you dial the right number at the right time
- ✉️ Skip-traced emails — returned with a concise availability and quality status when enough evidence is available
- 💬 Live WhatsApp check (opt-in) — confirms a number is active now and adds a WhatsApp outreach channel + public profile photo when available
- 🔗 One-tap outreach links — ready
tel:,sms:,mailto:andwa.melinks built from the contacts found - 🏚️ Absentee owner — mailing address ≠ property address (a top wholesale signal)
- 💰 Estimated equity & mortgage, length of ownership, purchase price/date
- ⚠️ Distress signals (opt-in) — tax delinquency, foreclosure, auction,
vacancy and code violations, with a 0–1
distressScore - 🚨 Distressed lead lists — pull fresh motivated-seller leads straight from
public city records: housing code violations, sheriff sales, delinquent
taxes and adjudicated property, each resolved to its owner with a reason to
call (
leadReasons) - 🎯 Lead score —
leadScore(0–100) +leadQuality(hot / warm / cold / dead) so you can sort and work the best leads first - 👪 Relatives, aliases, age, current + previous addresses and match confidence
Popular use cases
- Wholesale lead qualification — find owner contact data and prioritize absentee, high-equity, long-held, or potentially distressed properties.
- Property owner lookup — turn a property address or APN into a structured ownership record.
- Real estate skip tracing — enrich an existing property list with phone, email, mailing-address, and match-confidence fields.
- Portfolio discovery — search a person or company and find other properties associated with the same owner, across available covered sources in one query. Each portfolio includes a free summary row with the property count, states covered, and combined estimated value.
- LLC research — look for public registered-agent and officer information, then continue with a person search when appropriate.
- Market monitoring — schedule an area lead list with monitor mode on and get only what changed since the last run: new properties, new owners, and big assessed-value moves. The first run is a free baseline.
- CRM enrichment — export flat records to a spreadsheet or send structured JSON into an API, webhook, workflow, or lead-management system.
Choose the right search mode
| Input | What it does |
|---|---|
addresses | Property address → owner + contacts + deal signals |
ownerNames | Known owner (aligned to addresses) → straight to contacts |
leadListAreas | A ZIP or "City, ST" → available owners in the covered area as a lead list, flagged absentee + high-equity |
distressLists | Fresh motivated-seller leads from public city records (code violations, sheriff sales, delinquent taxes, adjudicated property) — resolved to owner + reason to call |
ownerSearch | Owner name → available properties associated with that owner (reverse portfolio) |
apnSearch | Parcel/APN number → owner + property |
businessSearch | LLC / company → its registered agent (+ officers where published) |
names / personAddresses / phoneNumbers / emails | Direct people search (name / address / phone / email) |
universalSearch | One box: give any mix of name / email / phone / address — it detects each signal, chains and merges into one profile |
Most real estate users should start with addresses. Use universalSearch
when you do not know which direct people-search field fits your data. Multiple
modes can be combined, but each populated field launches additional searches.
Key options
verifyEmails— email availability and quality status (default on)detectAbsentee,estimateEquity— derived deal signals (default on)distressSignals— tax / foreclosure / vacancy / code signals (opt-in)checkWhatsApp+whatsappMaxPerPerson— live WhatsApp check (opt-in)linkOwnerProperties— also return the owner's whole portfolioonlyAbsentee,minEquity,maxLeadsPerArea— lead-list filtersmaxContactsPerOwner,maxResultsPerQuery,maxConcurrencyflatOutput— flatten nested fields for spreadsheet/CSV export
Output & views
Five ready-made dataset views:
- 🏠 Owner & Contact — property, owner, absentee, best phone/email, equity, ownership years, confidence
- 🎯 Deal Signals — equity, value, mortgage, tax-delinquent, foreclosure, vacant
- People & Contacts — direct people-search matches and best contacts
- Owner Portfolio — properties associated with an owner query
- LLC & Registered Agent — available public business-registration matches
Each record also carries the full detail: phonesDetailed, emailsVerified,
outreachLinks, distressSignals / distressScore, leadScore /
leadQuality, relatives, aliases, age, addresses and source attribution.
Pricing
Pay per result (PPE): one result event is charged for each eligible delivered result. Unbilled failure or summary records may also appear in the Dataset.
Empty, blocked, invalid, and no-match lookups do not trigger the event. There is
no separate Actor-start event. Platform usage is additional under the current
pricing configuration.
| Apify tier | Price per result | Price per 1,000 |
|---|---|---|
| Free | $0.015 | $15 |
| Bronze | $0.012 | $12 |
| Silver | $0.011 | $11 |
| Gold | $0.010 | $10 |
| Platinum | $0.010 | $10 |
| Diamond | $0.010 | $10 |
Always check the live Pricing tab before a run; it is the source of truth.
Use from AI agents, n8n, Make, or any API client
The Actor is a plain HTTP API: one POST starts a run, the dataset returns JSON. It works the same from ChatGPT/Claude agents (Apify MCP), n8n, Make, Zapier, GitHub Actions, or curl.
# 1) Start a run (find owners for a list of addresses)curl -L "https://api.apify.com/v2/acts/apivault_labs~real-estate-skip-trace-go/runs" \-H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \-d '{"addresses": ["1200 Smith St, Houston, TX", "40 Waterside Plaza, New York, NY"]}'# 2) Read results (datasetId from the run object)curl -L "https://api.apify.com/v2/datasets/$DATASET_ID/items?format=json" \-H "Authorization: Bearer $APIFY_TOKEN"
Prompt patterns that work well with AI agents:
- "Find the owner, phone, and email for 123 Main St, Austin, TX"
- "List absentee owners in Tampa, FL and skip-trace their phones"
- "Show me code-violation and tax-delinquent leads in New Orleans"
- "What else does Main Street Holdings LLC own? Give me a portfolio rollup"
- "Monitor this ZIP weekly and alert me only when owners or values change"
Saved presets for the most common jobs (absentee-owner lists, distress lead lists, LLC portfolios, area monitoring) are available under Examples — copy one and just change the city or name.
Coverage and accuracy
Property and business-record coverage varies by US state and county. Contact, equity, mortgage, absentee, and distress fields are best-effort signals compiled from public sources; not every field is available for every property. Review important matches before outreach or investment decisions.
Every result also carries a leadReasons list — human-readable reasons to
prioritize the lead (for example: absentee owner, high equity,
LLC/entity owner, long ownership (15 yrs), high-value property,
phone on file) — alongside the numeric leadScore and leadQuality label.
Assessor/parcel owner records are queried live from these public sources:
| Statewide parcel sources | Records |
|---|---|
| Arkansas Statewide (GeoStor Planning Cadastre) | 2,117,780 |
| Colorado Statewide (OIT Public Parcels) | 2,599,761 |
| Connecticut Statewide (CAMA) | 1,290,196 |
| Florida Statewide (FDOR Cadastral) | 10,831,924 |
| Idaho Statewide (Public Parcels) | 380,988 |
| Iowa Statewide (Iowa Parcels) | 2,450,589 |
| Maryland Statewide (SDAT Property Data) | 2,396,022 |
| Massachusetts Statewide | 2,559,286 |
| Minnesota Statewide (MnGeo Open Parcels) | 2,708,126 |
| Montana Statewide (Cadastral Framework) | 921,006 |
| New Jersey Statewide (MOD-IV Composite) | 3,478,727 |
| New York Statewide (NYS Tax Parcels) | 5,510,061 |
| North Carolina Statewide (NC OneMap) | 5,938,639 |
| North Dakota Statewide | 748,548 |
| Pennsylvania Statewide (PASDA Parcels) | 4,685,585 |
| Tennessee Statewide (Property Boundaries Public Use) | 2,138,531 |
| Texas Statewide (StratMap) | 14,333,926 |
| Vermont Statewide | 343,860 |
| Wisconsin Statewide (V12 Parcel DB) | 3,574,646 |
| Subtotal | 69,008,201 |
| County / metro parcel sources | Records |
|---|---|
| Alameda County, CA (Oakland/Berkeley) | 489,766 |
| Arapahoe, CO (Littleton/Centennial) | 218,065 |
| Bexar County, TX (San Antonio) | 725,727 |
| Broward, FL (Fort Lauderdale) | 554,681 |
| Clark County, NV (Las Vegas) | 839,630 |
| Cobb, GA (Marietta) | 366,264 |
| Cook County, IL (Chicago) | 1,429,213 |
| Cuyahoga, OH (Cleveland) | 520,912 |
| Dallas, TX | 548,830 |
| Denton, TX | 383,031 |
| Detroit, MI (Parcels) | 377,863 |
| Duval County, FL (Jacksonville) | 400,000 |
| El Paso, CO (Colorado Springs) | 207,799 |
| Fairfax, VA (partial - appraised values file) | 31,849 |
| Fort Bend County, TX | 385,654 |
| Franklin County, OH (Columbus) | 492,379 |
| Fulton County, GA (Atlanta) | 373,004 |
| Gwinnett, GA (Lawrenceville) | 305,466 |
| Hamilton, OH (Cincinnati) | 420,246 |
| Harris, TX (Houston) | 1,548,457 |
| Hennepin, MN (Minneapolis) | 448,087 |
| Hillsborough County, FL (Tampa) | 500,000 |
| King, WA (Seattle) | 636,536 |
| Lee County, FL (Cape Coral/Fort Myers) | 564,719 |
| Maricopa, AZ (Phoenix) | 1,759,816 |
| Miami-Dade County, FL | 943,228 |
| Montgomery County, TX | 336,769 |
| Nashville-Davidson, TN | 286,831 |
| New York City, NY (5 boroughs: Manhattan/Kings/Queens/Bronx/Richmond) | 856,670 |
| Orange County, FL (Orlando) | 450,000 |
| Orange, NC (Chapel Hill/Durham edge) | 192,688 |
| Palm Desert, CA | 36,890 |
| Philadelphia, PA | 547,329 |
| Pinellas County, FL (St. Petersburg/Clearwater) | 437,172 |
| Polk, WI | 48,867 |
| Salt Lake, UT (partial - buffer subset) | 39,982 |
| San Bernardino County, CA | 839,913 |
| Suffolk, MA (Boston) | 184,548 |
| Tarrant, TX (Fort Worth) | n/a |
| Travis, TX (Austin) | n/a |
| Utah County, UT (Provo/Orem) | 284,092 |
| Wake, NC | n/a |
| Williamson County, TX (Austin suburb) | 289,628 |
| Subtotal | 20,302,601 |
That is roughly 89,310,802 assessor parcels addressable by property address, owner name, or APN — before counting the people-search, business-registry, and distressed-lead sources.
FAQ
Do I need an account, API key, login, or cookies?
No login, browser cookies, or external API key is required for the standard workflow. Optional bring-your-own services are clearly marked in the Input tab.
Can I run bulk real estate skip tracing?
Yes. Paste multiple property addresses or people-search values, one per line. For large jobs, start with a small sample to confirm coverage and output shape, then increase the batch size.
Which export formats are available?
Use the Apify dataset to download JSON, CSV, Excel, XML, or RSS. You can also read results through the Apify API, send them to a webhook, or connect them to an automation platform.
Why are some fields empty?
Public-record availability varies by jurisdiction and person. An empty contact or deal-signal field means the Actor did not find enough support to return that value; it should not be interpreted as proof that the information does not exist.
⚖️ Legal & Acceptable Use
Please read this section carefully. By running this Actor you accept these terms.
Bottom line: this is a neutral, general-purpose tool that retrieves already-public records. You — the user — decide which address or person to look up and how to use the results, so you alone are responsible and liable for that use. Any unlawful, harmful, harassing, or otherwise prohibited use is solely your responsibility, and you agree to indemnify the operator against any resulting claims.
1. Public data only. The Actor retrieves information from publicly available public-record and business sources. It does not access private, paywalled, or login-protected data.
2. Not a Consumer Reporting Agency. This Actor and its operator are not a consumer reporting agency (CRA) as defined by the U.S. Fair Credit Reporting Act (FCRA), and the output is not a "consumer report." You may NOT use this Actor or its output, in whole or in part, to make decisions about a person's eligibility for:
- credit or loans,
- employment or contracting,
- housing, rental, or tenant screening,
- insurance, or
- any other purpose regulated by the FCRA.
3. You are the responsible party. You act as the data controller for every lookup you run. You are solely responsible for using the data lawfully and for complying with all applicable laws and regulations, including but not limited to the FCRA, the Driver's Privacy Protection Act (DPPA), the Gramm-Leach-Bliley Act (GLBA), the Telephone Consumer Protection Act (TCPA), and state privacy laws such as the CCPA/CPRA and similar statutes. Intended for lawful business uses such as real-estate outreach, due diligence, and skip tracing — never for stalking, harassment, or any unlawful purpose.
4. Removal requests. If a person asks to have their information excluded, stop processing it and honor applicable opt-out / deletion rights.
5. Indemnification. You assume all risk and liability arising from your use of this Actor, and you agree to defend, indemnify and hold the operator harmless from any and all claims, losses, fines, or liabilities — including reasonable legal fees — resulting from your use or misuse of the Actor or its output, or your breach of these terms or of any law.
This is general information, not legal advice. If you are unsure whether your intended use is permitted, consult your own legal counsel before running this Actor.
Build a bounded property owner research workflow
US property owner lookup works best when the address, parcel context and purpose are clear. Start with one complete property address and review the returned owner evidence before adding contact enrichment or area discovery. A public record association does not by itself verify a current resident, decision-maker or an owner's willingness to sell.
| Goal | Starting input | Review required |
|---|---|---|
| Identify a property's recorded owner | addresses | Parcel/address match and evidence date |
| Prepare a small owner research file | addresses with selected enrichment | Contact match quality and missing fields |
| Review an area sample | leadListAreas and a small ceiling | County coverage, filters and partial results |
| Reconcile a CRM export | flatOutput | Record type, input identity and nested-field projection |
Check property evidence before contact enrichment
{"addresses": ["1200 Smith St, Houston, TX 77002"],"skipTraceContacts": false,"detectAbsentee": true,"estimateEquity": true,"maxConcurrency": 1,"maxRetries": 0}
This public commercial-address example requests property context. Contact collection is disabled. Review owner and source evidence; missing ownership or equity data is not a zero-valued fact.
Prepare a small flat property export
{"addresses": ["1200 Smith St, Houston, TX 77002"],"skipTraceContacts": false,"flatOutput": true,"maxConcurrency": 1,"maxRetries": 0}
Flat output is intended for spreadsheet handling. It changes the representation, not the tariff or the quality of an ownership match. Keep inputGiven or the address identity with the export.
Sample a covered area
{"leadListAreas": ["37215"],"maxLeadsPerArea": 2,"skipTraceContacts": false,"onlyAbsentee": false,"maxConcurrency": 1,"maxRetries": 0}
A two-row ceiling does not promise two matches or every owner in that ZIP. Coverage depends on available owner-exposing public parcel sources. Review the actual county and source context.
Add contact enrichment after a property match
{"addresses": ["1200 Smith St, Houston, TX 77002"],"skipTraceContacts": true,"maxContactsPerOwner": 2,"checkWhatsApp": false,"linkOwnerProperties": false,"maxConcurrency": 1,"maxRetries": 0}
Contact matches are best effort and may be missing. The per-owner contact limit is not a global Dataset-row cap. Keep match confidence and independently review any proposed CRM join.
Read records, derived signals and costs correctly
The live result rates per 1,000 records are $15 Free, $12 Bronze, $11 Silver and $10 Gold/Platinum/Diamond. There is no configured startup event. Platform usage is separately paid by the user under the active pricing configuration. Two Free-tier result events cost $0.03 before resources. Use settled result events, not Dataset length alone: the current runtime can also write unbilled failure records and free summary/baseline records.
An absentee flag compares available mailing and property addresses; it does not prove vacancy, landlord status or current occupancy. Equity and mortgage values are estimates or source observations with coverage limits, not a verified payoff statement. Lead scores and distress signals organize research; they do not prove a person's financial condition, urgency or sale intent. Owner-portfolio and area searches cover available sources, not every US parcel or legal interest.
For bulk work, leave unrelated search sections empty: populated sections launch additional searches. Use small per-query and per-area ceilings, modest concurrency and a run timeout while checking a new region. A successful run status can coexist with no-match or failed records. Check success, record type, source attribution and ownership context before counting useful properties.
Preserve the original query and evidence dates when moving results to a CRM. Review entity-versus-person matches and duplicates before combining records from multiple modes. Flat exports are convenient for sheets; JSON retains nested contact quality, source and deal-signal details for inspection. Follow the product's acceptable-use restrictions below when handling public records.
Does a property row guarantee an owner's phone or email? No. Property identification and contact enrichment have separate coverage. A useful ownership record may lack contacts, and a contact candidate still needs match review.
Does a ZIP list include every property owner? No. Source coverage, local availability, filters and output ceilings limit the returned set. Treat it as a covered sample unless completeness is independently established.
n8n and developer integrations
Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.
- n8n community node: n8n-nodes-apivault-real-estate-skip-trace-go. Install package name
n8n-nodes-apivault-real-estate-skip-trace-goin a self-hosted n8n instance that permits community packages. - Python client and examples: GitHub.
- n8n source and usage: GitHub.
These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.