Retrieving Identity Exposures
Pull past exposures of user identities
Last updated
Was this helpful?
Pull past exposures of user identities
Last updated
Was this helpful?
The following API endpoint allows you to retrieve historical exposures for a given identity, using your API key. This can be used in complementary fashion with the monitoring APIs to both monitor for new exposures of a given identity, after pulling the past exposures. Note that you will need to have Identity Breach Monitoring added to your subscription before you can call this API.
Allows you to pull historical exposure details for an individual identity. The identity can include elements such as name, physical address, phone numbers, government IDs, email addresses, credit cards, etc.
/identity-exposures
Legal first name
John
Legal last name
Doe
The ISO 3166-1 alpha 2 country code for the individual
US
Physical street address
1234 Main St
Physical address line 2
Suite 100
Physical address city
New York
Physical address province/state (2 letter abbreviation for US states)
NY
Physical address postal code (5-digit ZIP code in US)
12345
An array of email addresses associated with this identity
An array of payment card numbers associated with this identity
An array of cryptocurrency wallet addresses
An array of URLs associated with this identity. The URL scheme must be included and can be http, https, ftp, ftps, smtp or smtps. URLs are partial match from the beginning of the value, so if https://www.enzoic.com/some/page was found in a breach and https://www.enzoic.com was the URL being monitored, this would be considered a match.
An array of IPv4 addresses to monitor
An array of IPv6 addresses to monitor
A national identifier for this individual (e.g. Social Security Number in the US)
An array of phone numbers associated with this identity
An array of secondary items to match. Secondary matches occur after an identity is matched using the core PII provided above (name, government ID, etc.). If an identity is matched using the core PII, Enzoic looks within close proximity to it for secondary matches that should be flagged as well. Secondary match information can include anything relatively unique to the user and not already covered in one of the core PII categories, e.g. financial account numbers, localty card numbers, a US Employer Identification Number (EIN), passport number, etc.