FastPeopleSearch APIfastpeoplesearch.com ↗
Search US public records by name, phone, or address. Get person profiles with contact history, relatives, associates, and address history via 4 endpoints.
What is the FastPeopleSearch API?
The FastPeopleSearch API exposes 4 endpoints for querying US public records: search by name, phone number, or street address, then fetch full person profiles via get_person_details. A single name search returns age, location, aliases, relatives, and a person_slug you can pass to the detail endpoint to retrieve phone numbers with carrier info, email addresses, current and previous addresses, and associated individuals.
curl -X GET 'https://api.parse.bot/scraper/47c39b30-45d4-42b7-a33f-179f4bbb242c/search_by_name?name=John+Smith&location=Seattle%2C+WA' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace fastpeoplesearch-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: FastPeopleSearch SDK — bounded, re-runnable; every call capped."""
from parse_apis.fastpeoplesearch_com_api import FastPeopleSearch, PersonNotFound
client = FastPeopleSearch()
# Search for people by name with location filter
for person in client.people.search_by_name(name="John Doe", location="Springfield, IL", limit=3):
print(person.name, person.age, person.location)
# Reverse phone lookup
for person in client.people.search_by_phone(phone="+1 (555) 012-3456", limit=3):
print(person.name, person.location, person.past_addresses)
# Search by address
for person in client.people.search_by_address(street="123 Main St", city_state_zip="Springfield IL 62704", limit=3):
print(person.name, person.age)
# Drill into full person details from a search result
hit = client.people.search_by_name(name="John Doe", location="Springfield, IL", limit=1).first()
try:
full = hit.details()
print(full.full_name, full.age)
print(full.current_address.full_address)
for phone in full.phone_numbers[:3]:
print(phone.number, phone.type, phone.carrier)
except PersonNotFound as e:
print("person gone:", e.person_slug)
print("exercised: people.search_by_name / people.search_by_phone / people.search_by_address / PersonSummary.details")Search people by name across public records. Returns matching person summaries with age, location, past addresses, relatives, and aliases. Each result includes a person_slug for get_person_details.
| Param | Type | Description |
|---|---|---|
| namerequired | string | Full name to search for (e.g. 'John Smith'). |
| location | string | City and state to narrow search (e.g. 'Seattle, WA'). Omitting searches nationwide. |
{
"type": "object",
"fields": {
"total": "integer count of results returned",
"results": "array of person summaries with name, age, location, person_slug, past_addresses, relatives, and aka"
},
"sample": {
"total": 10,
"results": [
{
"age": 88,
"aka": [
"John Wsmith"
],
"name": "John Smith",
"location": "Anchorage, AK",
"relatives": [
"Minnie Smith",
"Chris Smith"
],
"person_slug": "john-smith_id_G-8653115056365742102",
"past_addresses": [
"Anchorage, AK",
"Suquamish, WA"
]
}
]
}
}About the FastPeopleSearch API
Search Endpoints
search_by_name accepts a full name and an optional location string (city and state) to narrow results geographically. Without location, the search covers nationwide records. Each result in the results array includes name, age, location, aka (aliases), past_addresses, relatives, and a person_slug used to fetch the full profile. search_by_phone performs a reverse lookup on any 10-digit US number and returns current and former owners tied to that number, along with a normalized phone_number field in XXX-XXX-XXXX format. search_by_address takes a street and city_state_zip and returns current and past residents at that address.
Person Detail Endpoint
get_person_details accepts a person_slug from any search result and returns the most complete record set. Response fields include full_name, age, aka, current_address (with full_address, address_slug, and since date), previous_addresses, phone_numbers (each with number, type, carrier, and first_reported), email_addresses, relatives (with name, age_info, relationship, and their own person_slug), and associates. Relatives and associates both carry person_slug values, enabling chained lookups.
Coverage and Data Shape
All coverage is limited to US public records. The search endpoints return summary-level data suitable for identifying the right individual before committing a full detail fetch. Phone carrier and first-reported date fields in the detail endpoint are useful for distinguishing active lines from historical records. Email addresses are returned as plain strings in an array; no metadata accompanies them.
The FastPeopleSearch API is a managed, monitored endpoint for fastpeoplesearch.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fastpeoplesearch.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official fastpeoplesearch.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Reverse-lookup a phone number to identify the current and past owners before returning a call
- Verify a person's stated address against their public record history during an onboarding workflow
- Build a relative-graph by chaining get_person_details calls on person_slugs returned in the relatives array
- Cross-reference an address to enumerate known residents for property research or skip tracing
- Identify aliases returned in the aka field to broaden a background check across multiple name variants
- Retrieve phone carrier information to decide whether to route to SMS or voice outreach
- Aggregate previous_addresses to trace geographic movement history for an individual over time
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.