cyberbackgroundchecks.com APIcyberbackgroundchecks.com ↗
Search cyberbackgroundchecks.com by name or email. Retrieve addresses, phone numbers, email addresses, relatives, associates, and address history via 4 endpoints.
// select an endpoint above
About the cyberbackgroundchecks.com API
The CyberBackgroundChecks API provides 4 endpoints for querying public people-search records, returning up to 9 fields per record including current address, phone numbers, email addresses, relatives, and address history. The search_by_name endpoint accepts a full name plus optional city and state filters and returns paginated summaries, while get_record_details retrieves the complete record for a specific person using a record_id from search results.
What the API Returns
The API surfaces public people-search records from CyberBackgroundChecks.com across four endpoints. Searches return structured person summaries containing name, age, current_address, phones, relatives, and associates. Full records fetched via get_record_details extend this with email_addresses, other_names (aliases), and address_history — a historical list of prior residential addresses.
Searching by Name
search_by_name requires a name parameter (e.g., 'Jane Doe') and optionally accepts city and state (two-letter abbreviation such as 'ca' or 'ny') to narrow results geographically. Results are paginated at 10 records per page. Each result includes a record_id — a URL path segment — that you pass to get_record_details to retrieve the full record for that individual.
Email-Based Lookup
Two email-oriented endpoints are available: search_by_email returns matching person summaries for a given email address, and full_search_by_email combines the search and detail-retrieval steps to return complete records for all matches in one call. These complement the name-search workflow when an email address is the known identifier rather than a name.
Coverage and Scope
All records are US-based public data. The state filter accepts standard two-letter US state abbreviations. The record_id values are specific to CyberBackgroundChecks.com and must be obtained from a prior search_by_name or search_by_email call — they cannot be constructed independently.
- Verify a contact's current address and phone number before sending physical or phone outreach
- Identify aliases or other observed names for an individual using the
other_namesfield - Build a people-search tool that filters results by US city and state using
search_by_nameparameters - Trace address history for a person across multiple prior residences using the
address_historyfield - Cross-reference an email address against public records to surface associated name and location data
- Enumerate relatives and associates linked to a specific record for relationship mapping
- Batch-resolve full details for multiple email search matches 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 | 250 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 have an official developer API?+
What does `get_record_details` return that `search_by_name` does not?+
search_by_name returns a summary per person: name, age, current_address, phones, relatives, and associates. get_record_details adds email_addresses, other_names (aliases the person has appeared under), and address_history (a list of prior addresses). You need a record_id from a search result to call this endpoint.Are results limited to the United States?+
state filter accepts US two-letter abbreviations. Non-US records are not covered by this source.Does the API return criminal records or court filings?+
How does pagination work for `search_by_name`?+
url field reflecting the queried page and a query field with the search string. To retrieve subsequent pages you adjust the page parameter in your request. Each result in the results array contains a record_id needed to fetch full details.