Radaris People Search (SkipTrace Lookup) avatar

Radaris People Search (SkipTrace Lookup)

Pricing

from $0.79 / 1,000 people

Go to Apify Store
Radaris People Search (SkipTrace Lookup)

Radaris People Search (SkipTrace Lookup)

Look up US people by name on Radaris. Extract addresses, relatives, aliases, age, and geo-coordinates as structured skip-trace data. Export as JSON, CSV, Excel.

Pricing

from $0.79 / 1,000 people

Rating

0.0

(0)

Developer

ParseBird

ParseBird

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Radaris People Search (SkipTrace Lookup)

Radaris People Search is a lightweight skip-trace tool that looks up US people by name on radaris.com and returns clean, structured public-record data — addresses, relatives, alternate names, age, and geo-coordinates — one row per matched person. It is HTTP-only, needs no login or browser, and pairs with Apify schedules to enrich your lead lists on a recurring basis.

Enter a full name (plus an optional city or US state) and get up to 500 person records — each with known addresses, family members and associates, name aliases, approximate age, and latitude/longitude for the primary home location.

Copy to your AI assistant

Copy this block into ChatGPT, Claude, Cursor, or any LLM to start using this actor.

Actor: parsebird/radaris-people-search (Apify). Purpose: skip-trace / people search on radaris.com by name. Call with ApifyClient: client.actor("parsebird/radaris-people-search").call(run_input={"fullName": "John Smith", "state": "CA", "city": "", "maxItems": 3}). Inputs: fullName (string, REQUIRED — Radaris indexes by name only), city (string, optional, narrows results), state (string, optional, 2-letter abbreviation like CA/TX/NY or full name), phone (string, optional, accepted but UNUSED — no phone reverse-lookup), email (string, optional, accepted but UNUSED — no email reverse-lookup), maxItems (integer, default 3, max 500), proxyConfiguration (object, defaults to Apify residential US proxy). Output: one dataset row per person with type="skip_trace_person", id, url (radaris profile URL), fullName, firstName, lastName, age, addresses [{street?, city, state, zip?, country}], relatives [{name, relation?, url?}], alternateNames [string], latitude, longitude, scrapedAt (ISO-8601 UTC). Only populated fields are included. If fullName is blank the actor returns a single {type:"invalid_input"} row instead of failing. API docs: https://apify.com/parsebird/radaris-people-search/api. Get a token at https://console.apify.com/account/integrations.

What does Radaris People Search do?

Radaris aggregates US public records — property and address history, relatives and associates, aliases, and age — and indexes them by person name. This Radaris scraper automates that lookup:

  • 🔍 Name-based search — pass any fullName (e.g. John Smith); the actor queries Radaris and parses every candidate profile it surfaces.
  • 📍 City and state filters — add a city or state to push matching records to the top of the results.
  • 🏠 Address history — every known location for each person, parsed into street, city, state, zip, and country.
  • 👪 Relatives and associates — family members and known associates, with links to their Radaris pages when available.
  • 🪪 Alternate names — alias and alternate-spelling variants Radaris has on file.
  • 🗺️ Geo-coordinates — latitude and longitude for the primary home location, geocoded from the address.
  • HTTP-only and fast — no browser runtime, no cookies, no login. Runs cheaply and finishes in seconds.
  • 🗓️ Automation-ready — combine with Apify scheduling, the API, and integrations (Make, Zapier, n8n, webhooks) to run recurring skip-trace enrichments against your own lists.

phone and email inputs are accepted so the actor is a drop-in for skip-trace pipelines, but Radaris has no phone or email reverse-lookup, so those values are ignored.

What data can you extract from Radaris?

FieldTypeDescription
typestringAlways skip_trace_person for person rows.
idstringStable Radaris name identifier, e.g. John-Smith.
urlstringCanonical radaris.com profile URL.
fullNamestringMatched person's full name.
firstNamestringGiven name.
lastNamestringFamily name.
ageintegerAge, when Radaris exposes it.
addressesobject[]Known locations: {street?, city, state, zip?, country}.
relativesobject[]Family members and known associates: {name, relation?, url?}.
alternateNamesstring[]Alternate spellings and known aliases.
latitudenumberLatitude of the primary home location.
longitudenumberLongitude of the primary home location.
scrapedAtstringISO-8601 UTC timestamp of the scrape.

Only populated fields are included in each row — there are no null values.

Input parameters

ParameterTypeRequiredDefaultDescription
fullNamestringYesFull name to look up, e.g. John Smith. If blank, the run returns one invalid_input row instead of failing.
citystringNoCity to narrow the search, e.g. Dallas. Matching records are returned first.
statestringNoUS state to narrow the search. Accepts a 2-letter abbreviation (CA, TX, NY) or a full state name.
phonestringNoAccepted for compatibility but unused — Radaris has no phone reverse-lookup.
emailstringNoAccepted for compatibility but unused — Radaris has no email reverse-lookup.
maxItemsintegerNo3Maximum person records to return (max 500). Radaris typically surfaces 20–35 candidates per name.
proxyConfigurationobjectNoApify residential USProxy settings. Radaris rate-limits by IP, so a residential US proxy is used by default.

Example input

{
"fullName": "John Smith",
"state": "CA",
"maxItems": 3
}

Output example

{
"type": "skip_trace_person",
"id": "John-Smith",
"url": "https://radaris.com/p/John/Smith/",
"fullName": "John Smith",
"firstName": "John",
"lastName": "Smith",
"age": 46,
"addresses": [
{"city": "Nevada City", "state": "CA", "country": "USA"},
{"city": "Grass Valley", "state": "CA", "country": "USA"}
],
"alternateNames": ["John B Smith"],
"relatives": [
{"name": "Andrea Mason", "url": "https://radaris.com/p/Andrea/Mason-US/"},
{"name": "David Smith", "url": "https://radaris.com/p/David/Smith/"}
],
"latitude": 39.2625993,
"longitude": -121.0187304,
"scrapedAt": "2026-08-29T00:05:02Z"
}

Download the dataset in JSON, CSV, Excel, HTML, RSS, or XML from the Storage tab or via the API.

How to look up people on Radaris

  1. Open the Input tab of Radaris People Search on Apify.
  2. Enter a Full name — for example John Smith.
  3. Optionally add a City and/or US state to narrow the results.
  4. Set Max person records (start with the default 3 to keep the first run cheap).
  5. Click Start and wait a few seconds.
  6. Open the Storage / Dataset tab to view results, or export as JSON, CSV, or Excel.
  7. To automate, open the Schedules tab and add a recurring run, or call the actor from the API.

Run it from the API

Python:

from apify_client import ApifyClient
client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("parsebird/radaris-people-search").call(run_input={
"fullName": "John Smith",
"state": "CA",
"maxItems": 3,
})
for person in client.dataset(run["defaultDatasetId"]).iterate_items():
print(person["fullName"], person.get("addresses"))

JavaScript:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('parsebird/radaris-people-search').call({
fullName: 'John Smith',
state: 'CA',
maxItems: 3,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

How much does it cost to scrape Radaris?

This actor uses pay-per-result pricing. You are charged once per person record pushed to the dataset (the invalid_input sentinel row is free), plus Apify platform usage, which is minimal because the actor is HTTP-only.

Plan tierPrice per 1,000 person records
Free$0.99
Bronze$0.89
Silver$0.89
Gold$0.79

A typical lookup returning 3 records costs well under one cent in result fees. Enriching a list of 1,000 names at 3 records each costs roughly $3 on the Free tier.

Use cases

  • Skip tracing — locate current and past addresses for debt collection, process serving, or asset recovery.
  • Real-estate lead enrichment — append owner addresses, relatives, and aliases to distressed-property or absentee-owner lists.
  • People and background research — build a profile of known locations, associates, and name variants for a person of interest.
  • Identity verification — cross-check a claimed name against public-record address history.
  • Genealogy and family research — trace relatives and associates across locations.
  • List hygiene — validate and de-duplicate contact lists against public records.

How it works

  1. The actor splits fullName into a first and last name and builds a Radaris search request, adding your city / state filters.
  2. It fetches the Radaris results page over an Apify residential US proxy, rotating the proxy session automatically on rate limits.
  3. It parses each candidate profile card — name, age, address history, relatives, and aliases.
  4. Records matching your city / state filter are moved to the top; the rest are kept as fallback.
  5. For each returned person, the primary address is geocoded to latitude/longitude.
  6. Each person is pushed as one dataset row with only its populated fields.

FAQ

Does Radaris support phone or email reverse-lookup? No. Radaris indexes people by name only. The phone and email inputs exist so the actor is a drop-in for skip-trace pipelines, but they are not used for the lookup.

Why do all rows share the same id and url? Radaris groups every person for a given name under one name page (e.g. radaris.com/p/John/Smith/). Each dataset row is a distinct candidate under that name, differentiated by age, addresses, relatives, and aliases.

How many records will I get per name? Radaris typically surfaces 20–35 candidates per name on a single page. maxItems caps how many are returned and billed; there is no deep pagination beyond what Radaris shows.

What happens if the name has no matches? The run finishes successfully with an empty dataset and a warning in the log. Try a different spelling or drop the city/state filter.

Why is a residential proxy required? Radaris rate-limits aggressively by IP. The actor defaults to Apify's residential US proxy and rotates the session on blocks. You can override proxyConfiguration, but non-residential proxies are likely to be throttled.

Are latitude and longitude always present? They are best-effort. Coordinates come from geocoding the primary address; if geocoding fails or the person has no usable address, the fields are omitted.

Can I schedule recurring runs? Yes. Use the Schedules tab to run daily, weekly, or at any interval, or trigger runs from the API, webhooks, or integrations like Make and Zapier.

Something looks wrong or broke. Open an issue on the Issues tab with your input and the run ID — feedback is welcome and helps keep the actor reliable.

This actor collects data that Radaris publishes publicly, without logging in. Public records and people-search data are subject to laws that vary by jurisdiction and use case. In the United States, using this data for employment screening, tenant screening, credit decisions, or insurance eligibility is regulated by the Fair Credit Reporting Act (FCRA) and is not a permitted use of this actor's output. You are responsible for ensuring your use complies with the FCRA, state privacy laws, the Radaris Terms of Service, and any other applicable regulations. Read Apify's guide on the legality of web scraping for background. If you are the subject of a record and want it removed, use the Radaris opt-out / privacy control page.