CyberBackgroundChecks APIcyberbackgroundchecks.com ↗
Search cyberbackgroundchecks.com by name or email. Get addresses, phone numbers, email addresses, relatives, associates, and address history via 4 endpoints.
What is the CyberBackgroundChecks API?
The CyberBackgroundChecks API provides 4 endpoints for querying US people-search records, returning up to 14 distinct data fields per person including current address, phone numbers, email addresses, address history, relatives, and associates. The get_record_details endpoint delivers the most complete profile, while search_by_name accepts optional city and state filters to narrow results across a paginated result set.
curl -X GET 'https://api.parse.bot/scraper/2a832fe1-60e7-4658-9b29-5e5883ba2461/search_by_name?city=Los+Angeles&name=John+Smith&state=ca' \ -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 cyberbackgroundchecks-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.
"""
Search for people using Cyber Background Checks.
Demonstrates name search, detail retrieval, and email search.
"""
from parse_apis.cyber_background_checks_api import CyberBackgroundChecks, Person, PersonDetail, RecordNotFound
client = CyberBackgroundChecks()
# Search for people by name with city/state filters
for person in client.people.search(name="John Doe", state="ca"):
print(person.name, person.age, person.current_address)
# Drill into full details for this person
detail = person.details()
print(detail.name, detail.current_address)
for phone in detail.phone_numbers:
print(phone)
for addr in detail.address_history:
print(addr)
break
# Search by email address
for person in client.people.search_by_email(email="[email protected]"):
print(person.name, person.age)
# Full email search with automatic detail retrieval
for record in client.people.full_search_by_email(email="[email protected]"):
print(record.name, record.current_address)
for relative in record.relatives:
print(relative)Search for people by name with optional city and state filters. Returns a list of matching person summaries including name, age, current address, phone numbers, relatives, and associates. Results are paginated server-side with approximately 10 results per page. The name is used to build a URL slug; partial matches and variants (middle initials, similar names) may appear in results.
| Param | Type | Description |
|---|---|---|
| city | string | City name to filter results (e.g. 'Los Angeles'). |
| namerequired | string | Full name to search for (e.g. 'John Smith'). |
| state | string | Two-letter US state abbreviation to filter results (e.g. 'ca', 'ny'). Lowercase. |
{
"type": "object",
"fields": {
"url": "the URL that was queried",
"query": "the search name query string",
"results": "array of person summaries with name, age, record_id, current_address, phones, relatives, associates"
},
"sample": {
"data": {
"url": "https://www.cyberbackgroundchecks.com/people/John-Doe/ca",
"query": "John Doe",
"results": [
{
"age": "60",
"name": "John Doe",
"phones": [
"+1 (555) 012-3456",
"+1 (555) 012-3456",
"+1 (555) 012-3456"
],
"record_id": "/detail/john-doe/pidngxpxpyzapyylxqalxzb",
"relatives": [
"Jane Doe",
"Jane Doe",
"Jane Doe"
],
"associates": [
"Jane Doe",
"Jane Doe",
"Jane Doe"
],
"current_address": "123 Main St, Springfield, IL 62704"
}
]
},
"status": "success"
}
}About the CyberBackgroundChecks API
What the API Covers
All four endpoints draw from the CyberBackgroundChecks.com database of US public records. A typical person record exposes the person's full name, age, current residential address, known phone numbers, email addresses, other observed names or aliases, a full address history, and arrays of relatives and associates. Coverage is limited to the United States.
Endpoints and Parameters
search_by_name accepts a required name string and optional city and state (two-letter lowercase abbreviation) filters, returning an array of person summaries each with name, age, record_id, current_address, phones, relatives, and associates. Results are paginated server-side at roughly 10 per page. search_by_email takes a single email parameter and returns the same summary shape; many emails return an empty results array if the address is not in the database. get_record_details requires a record_id path obtained from either search endpoint and returns the full record including email_addresses, other_names, and address_history fields not present in search summaries.
Combined Lookup
full_search_by_email merges the two-step flow of search_by_email followed by get_record_details into a single call. It returns an array of fully detailed person objects for every match found for the given email address, saving a round-trip when you need complete records rather than summaries.
Data Freshness and Limitations
The database reflects publicly available records and is not updated in real time. Phone number and email coverage varies by individual; some records will have empty arrays for those fields. The state filter in search_by_name expects lowercase two-letter abbreviations (e.g., ca, ny). There is no built-in support for phone number lookups or address-to-person reverse searches at this time.
The CyberBackgroundChecks API is a managed, monitored endpoint for cyberbackgroundchecks.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when cyberbackgroundchecks.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 cyberbackgroundchecks.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?+
- Verify a contact's current address before sending physical mail using
current_addressfromget_record_details. - Cross-reference a supplied email against known person records to confirm identity using
search_by_email. - Build a people-verification step in onboarding flows by matching name, city, and state via
search_by_name. - Enumerate known aliases for a subject using the
other_namesarray returned byget_record_details. - Map a person's address history for due-diligence workflows using the
address_historyfield. - Identify potential relatives or associates of a known individual using the
relativesandassociatesarrays. - Aggregate contact data across multiple matching records in a single call using
full_search_by_email.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does CyberBackgroundChecks.com offer an official developer API?+
What does `get_record_details` return that the search endpoints do not?+
get_record_details adds email_addresses, other_names (aliases), and a full address_history array to the base fields returned by search results. Search endpoints return summary data only: name, age, current address, phones, relatives, and associates. A record_id from a prior search call is required to call this endpoint.How reliable are email-based lookups?+
search_by_email and full_search_by_email will return an empty results array in those cases. Email coverage is better for addresses that appear in older public data sets.Does the API support reverse phone lookups — finding a person by phone number?+
Is the data limited to the United States?+
state filter in search_by_name accepts US state abbreviations, and address fields reflect US residential addresses. International records are not covered. You can fork this API on Parse and revise it to point at a people-search source with international coverage.