🔎 Skip Trace & Reverse Lookup

Skip Trace & Reverse Lookup searches U.S. and Canadian public-record data by name, phone number, or address and returns clean, structured results for research, lead enrichment, and automation.

• 👤 Search people by name + location
• 📞 Reverse lookup phone numbers
• 🏠 Reverse lookup street addresses
• 📦 Process multiple records in one run
• 🧭 Automatically choose the lookup mode
• 📊 Get match confidence and match evidence
• 🆔 Keep every result connected to your original row
• ⚠️ Separate real no-matches from provider failures

This Actor returns possible public-record matches. It does not verify identity and is not intended for FCRA-regulated decisions.

---

🌍 Supported Regions

US ✅

• People search
• Reverse phone
• Reverse address

Canada ✅

• People search
• Reverse phone
• Reverse address

Set country on each record to US or CA. If omitted, it defaults to US. For Canada, province and postalCode are supported aliases for state and zip.

UK, Australia, and other regions are not supported in the current version.

📦 What data can it return?

🆔 Input row ID	🔗 External lead ID
🔍 Lookup mode	🚦 Resolution status
🏆 Candidate rank	📊 Match confidence
🧾 Match evidence	⚠️ Ambiguity reason
👤 Full name	🪪 Aliases
🎂 Age when available	🏠 Current address
🗂 Past addresses	☎️ Phone numbers
📱 Best phone	📞 Phone type when available
📡 Carrier when available	👪 Relatives
👥 Possible associates	🔗 Source URL when available
🕒 Scrape timestamp	✅ Success / error metadata

Missing fields are returned as null or empty arrays. The Actor does not invent missing data.

---

🚀 Features

• 3 lookup modes: people, reverse phone, reverse address
• Automatic lookup detection from the fields in each record
• Bulk input through records[]
• Row traceability with inputRowId and externalLeadId
• Deterministic match scoring
• Explainable evidence through matchEvidence
• Configurable confidence threshold
• Ambiguous-match handling
• Candidate deduplication
• Retryable provider-failure states
• Structured Apify Dataset output
• JSON, CSV, API, and integration friendly

---

⬇️ Input

The main input is:

records[]

Each object in records is one lookup.

👤 People lookup

Provide a name plus location context.

{
    "inputRowId": "lead-001",
    "fullName": "Jane Example",
    "city": "Austin",
    "state": "TX"
}

You can also use firstName and lastName.

---

📞 Reverse phone lookup

Provide a phone number.

{
    "inputRowId": "lead-002",
    "phone": "2025550104"
}

The Actor normalizes phone data before matching.

---

🏠 Reverse address lookup

Provide a street address and location.

{
    "inputRowId": "lead-003",
    "address": "100 Example Ave",
    "city": "Austin",
    "state": "TX",
    "zip": "78701"
}

---

🧭 Automatic lookup selection

lookupMode is optional.

If omitted, the Actor chooses from the available data:

Phone
→ reverse_phone

Address
→ reverse_address

Name + location
→ people

Not enough usable data
→ INVALID_INPUT

You can also explicitly set:

people
reverse_phone
reverse_address

---

⚙️ Main options

Option	Purpose
maxCandidatesPerRecord	Limit candidate rows retained per input record
minimumMatchConfidence	Set the minimum deterministic match score
includeAmbiguous	Keep strong near-tie candidates
deduplicatePeople	Remove duplicate person candidates
maxConcurrency	Control parallel processing
maxRetries	Control retry attempts

---

🧪 Example bulk input

{
    "records": [
        {
            "inputRowId": "lead-001",
            "externalLeadId": "crm-1001",
            "fullName": "Jane Example",
            "city": "Austin",
            "state": "TX"
        },
        {
            "inputRowId": "lead-002",
            "externalLeadId": "crm-1002",
            "phone": "2025550104"
        },
        {
            "inputRowId": "lead-003",
            "externalLeadId": "crm-1003",
            "address": "100 Example Ave",
            "city": "Austin",
            "state": "TX",
            "zip": "78701"
        }
    ],
    "minimumMatchConfidence": 0.6,
    "includeAmbiguous": true,
    "deduplicatePeople": true
}

Each record is processed independently.

---

⬆️ Output

Results are stored in the Actor's default Apify Dataset.

Each output row stays linked to the source record through inputRowId and, when supplied, externalLeadId.

📊 Example result

{
    "inputRowId": "lead-001",
    "externalLeadId": "crm-1001",
    "lookupModeUsed": "people",
    "resolutionStatus": "MATCHED",
    "candidateRank": 1,
    "matchConfidence": 0.8,
    "matchEvidence": ["name_match", "city_state_match"],
    "fullName": "Jane Example",
    "currentAddress": "100 Example Ave, Austin, TX 78701",
    "phoneNumbers": ["(202) 555-0104"],
    "bestPhone": "(202) 555-0104",
    "relatives": [],
    "possibleAssociates": [],
    "success": true,
    "errorCode": null,
    "errorMessage": null,
    "retryable": false
}

Example values are fictional and only demonstrate the output structure.

---

🚦 Resolution statuses

Status	Meaning
MATCHED	A candidate met the matching threshold
AMBIGUOUS	Multiple strong candidates are too close to safely choose one
NO_MATCH	The lookup completed, but no candidate met the matching rules
PARTIAL	The lookup could not complete normally, such as an upstream provider failure
INVALID_INPUT	The input row did not contain enough valid lookup data

⚠️ No-match vs provider failure

These are intentionally different:

Lookup completed with no acceptable candidate
→ NO_MATCH

Provider blocked, skipped, or failed
→ PARTIAL + PROVIDER_FAILED

This helps automated workflows decide whether a row should be retried.

---

📊 Match confidence

matchConfidence is a deterministic score based on available evidence.

Matching can use signals such as:

Name
Phone
Address
City
State
ZIP

matchEvidence shows which evidence contributed to the result.

Match confidence is a ranking aid, not proof of identity.

---

🧹 Candidate handling

When multiple public-record candidates are returned, the Actor can:

1. Normalize the input
2. Deduplicate candidates
3. Score candidates against the original row
4. Rank the strongest candidates
5. Apply minimumMatchConfidence
6. Return MATCHED, AMBIGUOUS, or NO_MATCH

The Actor prefers an honest ambiguous or no-match result over promoting weak evidence into a confident match.

---

🔌 API & integrations

Run the Actor through the Apify API or connect its Dataset to workflows such as:

• Google Sheets
• Make
• Zapier
• CRMs
• Internal APIs
• Data warehouses
• Lead-processing pipelines
• AI agents
• MCP workflows

Use the Actor's API tab in Apify Console for ready-made request examples.

---

💡 Example use cases

🎯 Lead enrichment

Start with a name and location and attempt to resolve structured public-record contact data while preserving your lead ID.

📞 Reverse phone research

Search a phone number and review possible public-record matches with structured match evidence.

🏠 Address research

Search an address for supported public-record resident or contact information.

🧹 CRM cleanup

Use inputRowId, externalLeadId, resolutionStatus, and matchConfidence to review results before syncing them downstream.

---

📤 Export results

Apify Dataset results can be exported in formats such as:

JSON
CSV
Excel
XML
HTML

---

⚠️ Current limitations

The current version supports U.S. and Canadian public-record lookups through region-specific providers.

It does not guarantee:

• A result for every person, phone, or address
• That public-record information is current or complete
• Verified identity
• Phone ownership without supporting returned evidence
• Email enrichment
• Consumer-report accuracy
• Continuous availability of every upstream source

Provider coverage can change between runs.

---

⚖️ Responsible use

Use this Actor only for lawful public-record research and data workflows.

Do not use it for:

• Credit eligibility
• Employment screening
• Housing or tenant decisions
• Insurance eligibility or underwriting
• Stalking or harassment
• Fraud
• Discrimination
• Other unlawful purposes

This Actor is not a consumer report and is not designed for FCRA-regulated decisions.

You are responsible for complying with applicable privacy, public-record, telecommunications, and data-protection laws.

---

❓ FAQ

What can I search?

People by name + location
Phone numbers
Street addresses

Can I process multiple records?

Yes. Add multiple objects to records[].

Do I need to select a lookup mode?

No. The Actor can automatically select the mode from the available fields.

What does NO_MATCH mean?

The lookup completed, but no candidate satisfied the Actor's matching rules.

It does not mean that every possible public record was searched.

What does PARTIAL mean?

The lookup could not complete normally. Check:

errorCode
errorMessage
retryable

Is matchConfidence proof of identity?

No. It is a deterministic matching score.

Why are some fields null?

Not every source exposes every field. Missing values are preserved instead of fabricated.

Can I use it through an API?

Yes. Open the Actor's API tab for examples.

---

💬 Feedback & support

Found a bug or unexpected result?

Use the Actor's Issues tab and include:

lookupModeUsed
resolutionStatus
errorCode
errorMessage

Avoid posting sensitive personal data publicly in issue reports.

---

🚀 Structured skip tracing for automation

Submit a name, phone number, or address and get structured public-record results with traceable row IDs, match confidence, clear no-match handling, and retryable provider-failure states.