Radaris People Scraper | US People Search, Phone Numbers & Public Records Lookup

Search for anyone in the United States by name and extract structured public records from Radaris.com — one of the largest US people search and public records aggregators. This actor returns addresses, phone numbers, relatives, employment history, education, and aliases in clean JSON, ready for your CRM, spreadsheet, or automation pipeline.

No login required. No browser overhead. Just results.

✅ Extracts phone numbers, job titles, and employer — not just name and address

✅ Parses rich JSON-LD structured data directly from Radaris profile pages

✅ Supports state and city filters to narrow results on common names

✅ Graceful error handling for proxy limits, billing issues, and missing profiles

✅ Export to JSON, CSV, Excel, and XML via the Apify dataset interface

✅ Full API access for automation and integrations

---

What Data Can Be Extracted?

Field	Description
id	Stable numeric Radaris profile ID extracted from the profile URL
fullName	Full name as listed on Radaris
firstName	Given name
lastName	Family name
birthDate	Birth year or date (when publicly available)
jobTitle	Current or most recent job title
workCompany	Employer name
education	Educational institution attended
phones	Known phone numbers (deduplicated)
addresses	Known residential addresses (street, city, state, ZIP)
relatives	Family members and known associates
aliases	Alternate name spellings and nicknames

---

Features

• Phone numbers included — most competing actors stop at name and address; this one goes further
• Employment and education data — extract job title, employer, and alumni information
• Full address fields — street address, city, state, and ZIP in a single formatted string
• State and city filters — narrow results when searching common names
• Auto-parses full names — accepts fullName or separate firstName/lastName inputs
• Stable profile IDs — numeric Radaris ID lets you reconstruct canonical profile URLs
• Chrome TLS fingerprinting — uses curl_cffi to impersonate a real browser, no Playwright overhead
• Proxy-aware — full Apify proxy configuration support including US Residential proxies
• Out-of-funds protection — detects HTTP 402 and 407 responses and stops cleanly before wasting compute
• Export to JSON, CSV, Excel, XML — via the Apify dataset interface
• API access — retrieve results programmatically or trigger runs via the Apify API
• Schedule automated runs — keep records fresh with Apify's built-in scheduling
• Integrate with Zapier, Make, n8n — connect to your existing workflows

---

How to Scrape Radaris People Data

1. Open the Actor on Apify and click Try for free
2. Enter the person's name — provide firstName and lastName, or a combined fullName
3. Narrow by location (optional) — add a US state code (CA, TX, IN, etc.) or city name
4. Set a result limit — use maxItems to control how many profiles are scraped (default: 3)
5. Configure proxies — US Residential proxies are strongly recommended to avoid 403 blocks
6. Run the Actor and wait for results (typically a few seconds per profile)
7. Download your data — export as JSON, CSV, Excel, or XML from the dataset tab

---

Input Example

{
  "fullName": "Michael Anderson",
  "state": "IN",
  "city": "Indianapolis",
  "maxItems": 3,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

---

Field	Type	Required	Default	Descriptio
fullName	string	✅*	—	Full name
state	string	❌	—	US state code to narrow results (CA,TX,IN, etc.)
city	string	❌	—	City name to further narrow results
maxItems	integer	❌	10	Max number of profiles to scrape and return
proxyConfiguration	object	❌	—	Apify proxy config (US Residential strongly recommended)

*Either fullName or both firstName and lastName are required.

---

Output Example

{
  "id": "123456789",
  "fullName": "Michael Anderson",
  "firstName": "Michael",
  "lastName": "Anderson",
  "birthDate": "1978",
  "jobTitle": "Software Engineer",
  "workCompany": "Acme Corp",
  "education": "Indiana University",
  "phones": ["+13175550192"],
  "addresses": [
    "1234 Maple St, Indianapolis, IN, 46201"
  ],
  "relatives": [
    "Sandra K Anderson",
    "James T Anderson"
  ],
  "aliases": [
    "Mike Anderson",
    "M Anderson"
  ]
}

---

Use Cases

Real Estate Skip Tracing

Find landlord contact details, property owner phone numbers, and current addresses for due diligence, collections, or outreach. Enrich property records with live contact data.

Lead Enrichment

Append employment, phone, and address data to existing prospect lists. Turn a name into a full contact profile without manual lookup.

Background Research & Due Diligence

Aggregate publicly available records on individuals for business partnerships, vendor screening, or investigative research. Identify known associates and relatives.

CRM Data Hygiene

Verify and update stale contact records in your CRM. Match names to current addresses, employers, and phone numbers to reduce bounce rates and improve deliverability.

Genealogy & Family Research

Identify relatives, known associates, and alternate name spellings across a family tree. Cross-reference addresses and birth years with public records.

Journalism & Investigative Research

Look up public figures, witnesses, or sources by name and location. Retrieve known contact points and associated individuals from public record aggregators.

---

API Access

You can trigger this actor and retrieve results programmatically using the Apify API. This enables full automation without the Apify web interface.

Common API use cases:

• Trigger actor runs from your own application or backend
• Poll for run completion and retrieve results via the dataset endpoint
• Schedule recurring runs to keep records up to date
• Integrate with Zapier, Make (Integromat), or n8n using Apify's native connectors

Retrieve results from a completed run:

GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json

Supported export formats via API: json, csv, xlsx, xml, rss.

---

Pricing

This actor runs on Apify's pay-per-use infrastructure. Costs depend on compute time and proxy usage.

Volume	Estimated Actor Compute	Notes
10 profiles	Very low	Seconds of runtime
100 profiles	Low	Under 1–2 minutes
1,000 profiles	Moderate	Consider scheduling across multiple runs

Proxy costs are separate. US Residential proxies (required for reliable results) are billed per GB of traffic consumed. Radaris profile pages are lightweight, so bandwidth costs are minimal per profile.

To minimize costs: use the state filter to reduce irrelevant results, and set maxItems to limit unnecessary scraping on common names.

---

Why Use This Instead of Manual Lookup or Other Actors?

Feature	This Actor	crawlerbros/radaris-people-search	Manual Lookup
Phone numbers	✅	❌	✅ (one at a time)
Job title	✅	❌	✅ (one at a time)
Employer name	✅	❌	✅ (one at a time)
Education	✅	❌	✅ (one at a time)
Aliases	✅	✅	✅ (one at a time)
Relatives	✅	✅	✅ (one at a time)
Full addresses	✅ Street + city + state + ZIP	✅ Partial	✅ (one at a time)
Numeric profile ID	✅	❌	❌
State + city filter	✅	✅	✅
Proxy support	✅ Full Apify proxy config	⚠️ Basic	❌
Out-of-funds protection	✅ 402/407 detection	❌	❌
Bulk automation	✅	✅	❌
API access	✅	✅	❌
Speed	Fast (no browser)	Varies	Slow

---

Error Handling

The actor handles all failure modes gracefully and logs every event.

Scenario	Behavior
Missing firstName/lastName	Stops immediately with a clear log message
Radaris returns 403	Logs a warning, skips the profile, continues
Proxy authentication failure (407)	Logs a critical error, exits with code 2
Payment / funds exhausted (402)	Logs a critical error, exits with code 2
Profile page has no JSON-LD data	Skips silently, continues to next profile
Unexpected exception	Fails with exit code 3 and a descriptive message

---

FAQ

Is scraping Radaris legal?

This actor extracts publicly available information from Radaris.com that is accessible to anyone without login or account. Users are responsible for ensuring their use complies with applicable laws, including the FCRA. Do not use for FCRA-regulated purposes (employment, credit, housing, insurance decisions).

Do I need proxies?

Proxies are optional but strongly recommended. Radaris blocks many datacenter IP ranges. Using Apify US Residential proxies (RESIDENTIAL group, country US) will significantly improve success rates and avoid 403 errors.

Can I schedule runs automatically?

Yes. Apify's built-in scheduling lets you run this actor on any cron-based schedule — daily, weekly, or custom intervals.

Can I export results to CSV or Excel?

Yes. After a run completes, export the dataset in CSV, Excel, JSON, or XML from the Apify console or via API.

How many results can I scrape?

There is no hard limit. Set maxItems to any number. For very large batches, consider scheduling multiple runs or using the Apify API to trigger sequential runs.

Why am I getting 403 errors?

Radaris blocks some datacenter IPs. Switch to US Residential proxies in your proxyConfiguration to resolve this.

Can I search by phone number or address?

No. This actor only supports name-based search, which is what Radaris's public search interface provides. For reverse phone lookup, see other actors in the Apify Store.

What does the numeric id field represent?

It's the stable numeric identifier from the Radaris profile URL (e.g., .../123456789). You can use it to reconstruct the canonical profile URL: https://radaris.com/p/First/Last/{id}.

What if a profile has no phone number or employer listed?

Those fields will be empty arrays or null. Not all Radaris profiles have complete data — this reflects what Radaris has in its public records, not a scraper limitation.

What happens if Radaris changes its website structure?

The actor parses <script type="application/ld+json"> JSON-LD blocks, which are a stable, structured data format. This is more resilient to layout changes than CSS selector-based scrapers. If Radaris changes its structured data schema, the actor will be updated accordingly.

Do I need a login or cookies?

No. The actor performs plain HTTP GET requests against public Radaris pages. No cookies, sessions, or accounts are required.

Can I filter by city?

Yes. Pass a city value in the input to narrow results to a specific city, in addition to or instead of the state filter.

---

SEO Reference

How to Scrape Radaris Data

Radaris doesn't offer a public API. To extract data programmatically, you need a scraper that can impersonate a real browser, decode the Base64-encoded profile links on search result pages, and parse the JSON-LD structured data on individual profile pages. This actor handles all three steps automatically.

Radaris API Alternative

There is no official Radaris API available to the public. This actor is the closest functional equivalent: it accepts the same inputs (name, state, city) and returns the same structured data you'd find on a Radaris profile, in a machine-readable JSON format.

How Much Does It Cost to Scrape Radaris?

Actor compute costs are minimal — most runs complete in seconds. The main cost variable is proxy usage. Using Apify's US Residential proxy group costs a small amount per GB of traffic; at a few KB per profile page, you can scrape thousands of profiles for a modest amount.

Export Radaris Data to CSV

After any completed run, open the dataset in the Apify console and click Export to download results as CSV, Excel, JSON, or XML. You can also retrieve exports programmatically via the Apify dataset API.

Automate Radaris People Search

Use Apify's scheduling feature to run this actor on a recurring basis, or trigger it via the Apify API from your own application. Results are stored in Apify datasets and can be pushed to downstream tools like Google Sheets, Airtable, or any webhook-compatible service via Zapier or Make.

---

Support

If you encounter issues or have questions, open a ticket via the Issues tab on this actor's Apify Store page. Please include the input you used, the run ID, and any relevant log output. For proxy-related issues, confirm you're using the US Residential proxy group before filing a report.