FastPeopleSearch Scraper — Phones, Emails & Addresses

Turn a name, phone number, or street address into full US person records. Search FastPeopleSearch.com by name (with optional city/state), run reverse phone or reverse address lookups, or paste any FastPeopleSearch URL — and get structured rows with phone numbers, email addresses, current + past addresses, relatives, associates, and employment history.

Why Use This Scraper?

• ✅ Batch lists — searches[] runs many names, phones, or addresses in one run
• ✅ Email addresses included and decoded to plain text (most FastPeopleSearch scrapers skip these)
• ✅ Phone numbers with carrier, line type, and first-reported date
• ✅ Charged only for people actually written to the dataset — empty lookups cost nothing extra
• ✅ Flattened CRM columns (Email-1, Phone-1, …) for Sheets / skip-trace exports
• ✅ Resume cursor — continue a large crawl without re-billing people you already have
• ✅ Anti-bot handling built in — no proxy setup, no browser, no login

Overview

The FastPeopleSearch Scraper is built for skip tracers, real-estate investors, lead-generation teams, and researchers who need structured US people data without copying it off the site by hand.

The output is person-shaped rows. Whatever you start from — a name search, a phone number, an address, or a pasted URL — the dataset is a stream of person records, one row per profile. A reverse phone lookup that matches three people produces three person rows.

The site sits behind an aggressive anti-bot wall. This actor routes every request through unblocking infrastructure that clears it automatically, so a run needs zero proxy configuration on your side.

Coming from another skip-trace actor?

Complaint we keep seeing on the category leader	What this actor does
Charged for “Person Not Found” / 404s	Billing is apify-default-dataset-item — a row has to land in the dataset
One name per run, 189 runs for a list	Pass searches — one run, many lookups
No emails	Emails are decoded from Cloudflare obfuscation when the profile lists them
$0.10 actor-start tax	Start event is $0.005
Re-paying for page 1 of a huge name search	Paste resumeCursor from the previous run

Supported Inputs

Search modes

Mode	You provide	Example
Name search	firstName, lastName, optional city + state	John Smith in NY
Reverse phone	phone (any format)	(206) 592-2882
Reverse address	address, city, state, optional zip	123 Main St, Dallas, TX

URL types (advanced)

URL type	Pattern	Example
Name listing	/name/{first}-{last}_{city}-{st}	https://www.fastpeoplesearch.com/name/john-smith_ny
Reverse phone	/{AAA-BBB-CCCC}	https://www.fastpeoplesearch.com/206-592-2882
Reverse address	/address/{street}_{city}-{st}	https://www.fastpeoplesearch.com/address/123-main-st_dallas-tx
Person profile	/{name}_id_G{id}	https://www.fastpeoplesearch.com/amanda-smith_id_G4156490107428859261

Copy-pasteable startUrls

{
  "startUrls": [
    "https://www.fastpeoplesearch.com/name/john-smith_ny",
    "https://www.fastpeoplesearch.com/206-592-2882",
    "https://www.fastpeoplesearch.com/amanda-smith_id_G4156490107428859261"
  ],
  "maxItems": 20
}

Unsupported inputs

• ❌ URLs outside fastpeoplesearch.com
• ❌ Uploaded CSV / Google Sheets files (use searches[] or startUrls instead)
• ❌ Anything behind a login or paywall (the site has none for the data this actor collects)

Use Cases

Audience	Use case
Skip tracers	Locate current addresses and working phone numbers from a name or an old address
Real-estate investors	Reverse-address lookups on distressed properties to reach the owner directly
Lead-gen teams	Turn sparse contact lists into full records with phones and emails
Collections / legal	Verify identity, address history, and known relatives before contact
Researchers	Bulk-export people data for genealogy or demographic analysis

How It Works

1. Input — pick a search mode and fill the matching fields, or paste FastPeopleSearch URLs
2. Clear the wall — every request goes through unblocking infrastructure that passes the site's anti-bot check
3. Walk the results — the actor pages through the listing and opens each person profile concurrently
4. Parse the record — phones, emails (decoded from obfuscation), addresses, relatives, associates, employment
5. Output — one row per person, exportable as JSON, CSV, or Excel

Input Configuration

Input fields

Field	Type	Required	Notes
searchMode	string enum	optional	name (default), phone, or address. Ignored when startUrls is set
firstName	string	for name mode	First name to search
lastName	string	for name mode	Last name to search
city	string	optional / address mode	Narrows name searches; required for address mode
state	string enum	optional / address mode	Two-letter US state (50 states + DC)
phone	string	for phone mode	Any format — digits are extracted
address	string	for address mode	Street part, e.g. 123 Main St
zip	string	optional	Makes address mode more precise
searches	array<object>	optional	Batch: one object per lookup (same fields as a single search). Replaces the top-level search when set
maxItemsPerSearch	integer	optional	Cap per searches entry. Default 5 when more than one search is passed
flattenedOutput	boolean	optional	Add Email-1 / Phone-1 spreadsheet columns. Default false
resumeCursor	string	optional	Continue a previous run without re-billing delivered people
startUrls	array<string>	optional	FastPeopleSearch URLs; overrides the search fields
maxItems	integer	optional	Hard cap on person records. Default 10
maxConcurrency	integer	optional	Parallel profile fetches. Default 5

Common scenarios

1. Name search narrowed to a state

{
  "searchMode": "name",
  "firstName": "John",
  "lastName": "Smith",
  "state": "NY",
  "maxItems": 25
}

2. Reverse phone lookup

{
  "searchMode": "phone",
  "phone": "(206) 592-2882",
  "maxItems": 5
}

3. Reverse address lookup

{
  "searchMode": "address",
  "address": "6507 Steilacoom Blvd SW",
  "city": "Lakewood",
  "state": "WA",
  "maxItems": 10
}

4. Batch list (many lookups, one run)

{
  "searches": [
    { "searchMode": "name", "firstName": "Jane", "lastName": "Doe", "city": "Dallas", "state": "TX" },
    { "searchMode": "phone", "phone": "(206) 592-2882" },
    { "searchMode": "address", "address": "123 Main St", "city": "Austin", "state": "TX" }
  ],
  "maxItems": 50,
  "maxItemsPerSearch": 5,
  "flattenedOutput": true
}

Output Overview

Each dataset item is one person record containing:

• Identity — fullName, firstName, lastName, age, bornMonthYear, akas[]
• Contact — phones[] (number, line type, carrier, first-reported date, primary flag), emails[], primaryPhone
• Location — currentAddress (street/city/state/zip/county + since-date), coordinates, pastAddresses[] with recorded dates
• Property — currentAddressPropertyDetails (square feet, year built, estimated value, last sale, occupancy type)
• Network — relatives[] and associates[], each with name, age, and profile URL
• Work — currentEmployment[] and workExperience[] (employer, title, location)
• Query echo — query.inputGiven, Search Option, Input Given (so a batch row joins back to the lookup that produced it)
• Meta — personId, profileUrl, maritalStatusText, scrapedAt

Field availability follows the site: a profile without a listed email produces an empty emails array, not a missing run.

Output Samples

Reverse address start, trimmed

{
  "type": "person",
  "personId": "G5374097278778066177",
  "profileUrl": "https://www.fastpeoplesearch.com/mary-huff_id_G5374097278778066177",
  "fullName": "Mary L Huff",
  "firstName": "Mary",
  "lastName": "Huff",
  "age": 71,
  "bornMonthYear": "October 1954",
  "currentAddress": {
    "fullAddress": "6507 Steilacoom Blvd SW, Lakewood, WA, 98499",
    "street": "6507 Steilacoom Blvd SW",
    "city": "Lakewood",
    "state": "WA",
    "zip": "98499",
    "county": "Pierce County",
    "since": "January 2012"
  },
  "coordinates": { "latitude": 47.176693, "longitude": -122.524788 },
  "currentAddressPropertyDetails": {
    "bedrooms": "3",
    "squareFeet": "1,438",
    "yearBuilt": "1928",
    "estimatedValue": "$468,000",
    "occupancyType": "Owner Occupied"
  },
  "phones": [
    {
      "number": "(253) 380-5662",
      "type": "Wireless",
      "carrier": "T-Mobile USA Inc",
      "firstReported": "September 2025",
      "isPrimary": true
    }
  ],
  "primaryPhone": "(253) 380-5662",
  "emails": ["marylhuff@gmail.com", "mary.huff@intel.com"],
  "akas": ["Mary Huff", "Mary L Smith"],
  "pastAddresses": [
    {
      "fullAddress": "120 Walzer Rd Rochester NY 14622",
      "city": "Rochester",
      "state": "NY",
      "county": "Monroe County",
      "recordedDate": "June 2017"
    }
  ],
  "relatives": [
    { "name": "Amanda Smith", "age": "Age 46 (May 1980)", "profileUrl": "https://www.fastpeoplesearch.com/amanda-smith_id_G4156490107428859261" }
  ],
  "currentEmployment": [
    { "employer": "WASHINGTON STATE DEPARTMENT OF ECOLOGY", "title": "FLOODPLAIN MANAGEMENT UNIT SUPERVISOR", "location": "Salt Lake City, UT" }
  ],
  "scrapedAt": "2026-09-02T20:39:30.355Z"
  /* pastAddresses, relatives, associates, workExperience trimmed */
}

Key Output Fields

Identity

• fullName, firstName, lastName, age, bornMonthYear, akas[], personId, profileUrl

Phones

• phones[].number, phones[].type (Wireless / Landline / Voip), phones[].carrier, phones[].firstReported, phones[].isPrimary, primaryPhone

Emails

• emails[] — plain-text addresses, decoded from the site's obfuscation

Addresses

• currentAddress.{street, city, state, zip, county, since}, coordinates.{latitude, longitude}
• pastAddresses[].{fullAddress, street, city, state, zip, county, recordedDate}
• currentAddressPropertyDetails.{squareFeet, yearBuilt, estimatedValue, lastSaleAmount, occupancyType, …}

People network

• relatives[].{name, age, profileUrl}, associates[].{name, age, profileUrl}

Employment

• currentEmployment[].{employer, title, location}, workExperience[].{employer, title}

FAQ

Which URLs are supported?

Any fastpeoplesearch.com URL: name listings (/name/john-smith_ny), reverse phone pages (/206-592-2882), reverse address pages (/address/...), and direct person profiles (/{name}_id_G{id}). URLs on other hosts are not.

Do I get person rows or search-result rows?

Person rows, always. Listing pages are only used to find profiles; every dataset item is a full parsed profile.

Are emails always present?

No — they appear when the site lists them for that person. In testing, most adult profiles carried 5–12 addresses, but some have none. Emails that the site obfuscates are decoded to plain text automatically.

How do I search a whole state vs. one city?

Set state alone for a state-wide search, or city + state to narrow it. Leaving both empty searches nationwide, which is broad — cap it with maxItems.

Can I paste multiple searches into one run?

Yes. Put them in searches (one object per name / phone / address). Each entry is walked until maxItemsPerSearch (default 5 in batch) or the global maxItems. startUrls still works if you already have listing links.

How do I continue a run without paying twice?

When maxItems stops the crawl, the actor logs RESUME_CURSOR and writes it to the default key-value store. Paste that string into resumeCursor on the next run. Already-delivered person IDs are skipped and not billed again.

Can I scrape private or paywalled data?

No. The actor reads only the public profile pages; there is no login and no paid-content access.

Why do requests take longer than a normal scraper?

Every request goes through unblocking infrastructure to pass the site's anti-bot wall. A profile typically takes 3–30 seconds. Concurrency (default 5) keeps total run time reasonable.

What happens when the anti-bot check still blocks a request?

The actor retries up to 4 times per page with fresh unblocker sessions. Persistent failures are logged and skipped — a run never hangs on one bad URL.

Support

Found a bug or have a feature request? Open an issue on the actor's Issues tab in the Apify Console, or email muhameddidovic@gmail.com.

Additional Services

Need a custom export shape, monitoring on a schedule, or the same data from another people-search site? I do tailored work — drop me a line at muhameddidovic@gmail.com.

Explore More Scrapers

If you found this useful, you might also like:

• TruePeopleSearch Scraper — same pipeline on TruePeopleSearch.com
• Realtor.com Agents Scraper — all US real-estate agents, no 3k limit
• Zillow Agents Leads Scraper — agent lead lists from Zillow

Full list at apify.com/memo23.

🤖 For AI Agents & LLM Apps

Compact reference for AI agents calling this actor via the Apify MCP server or the Apify API (actor: memo23/fastpeoplesearch-scraper).

Purpose: US people search on FastPeopleSearch.com — name, reverse-phone, reverse-address, or a searches[] batch; returns one row per person including decoded emails, typed phones, address history, relatives, and associates.

Minimal input:

{ "searchMode": "name", "firstName": "John", "lastName": "Smith", "state": "NY", "maxItems": 5 }

Batch input:

{ "searches": [{ "searchMode": "phone", "phone": "2065922882" }, { "searchMode": "name", "firstName": "Jane", "lastName": "Doe", "state": "TX" }], "maxItems": 10, "flattenedOutput": true }

Output: one dataset row per person — fullName, firstName, lastName, age, phones[], emails[], currentAddress, query.inputGiven, plus optional Email-1 / Phone-1 columns when flattenedOutput is true.

Behaviors an agent should know:

• Always set maxItems. In batch mode also set maxItemsPerSearch (defaults to 5).
• searches[] runs many lookups in one run. startUrls overrides both searches and the single search fields.
• Billing is per person record written; empty lookups and resume skips are not billed.
• If a run hits maxItems, read RESUME_CURSOR from the default key-value store and pass it back as resumeCursor.
• Requests route through anti-bot unblocking — expect 3–30 s per page.

---

⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by FastPeopleSearch.com or its operators. All trademarks mentioned are the property of their respective owners.

The scraper accesses only publicly available people-search pages — no authenticated endpoints, paid features, or content behind any login wall. People-search data is sensitive: users are responsible for ensuring their use complies with FastPeopleSearch.com's Terms of Service, the Fair Credit Reporting Act (this actor is not a consumer reporting agency and its output must not be used for FCRA-regulated purposes such as employment, credit, or tenancy screening), applicable data-protection law (GDPR, CCPA, etc.), and any contractual obligations of their own organization.

---

SEO Keywords

fastpeoplesearch scraper, scrape fastpeoplesearch, fastpeoplesearch API, fastpeoplesearch.com scraper, Apify fastpeoplesearch, people search scraper, reverse phone lookup API, reverse address lookup scraper, skip tracing tool, skip tracing data, people finder API, phone number lookup scraper, email finder people search, address history data, relatives and associates data, US public records scraper, contact enrichment data, real estate lead generation, property owner lookup, truepeoplesearch alternative