Retrieving Identity Exposures

Pull past exposures of user identities

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.

---

Pull historical exposures for a specific identity

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.

POSThttps://api.enzoic.com/v1/identity-exposures

Authorization

enzoic_auth

Body

application/json

firstName*string

Legal first name

Example: "John"

lastName*string

Legal last name

Example: "Doe"

country*string

The ISO 3166-1 alpha 2 country code for the individual

Example: "US"

address1string

Physical street address

Example: "1234 Main St"

address2string

Physical address line 2

Example: "Suite 100"

citystring

Physical address city

Example: "New York"

provincestring

Physical address province/state (2 letter abbreviation for US states)

Example: "NY"

postalCodestring

Physical address postal code (5-digit ZIP code in US)

Example: 12345

governmentIDobject

A national identifier for this individual (e.g. Social Security Number in the US)

emailsarray of string

An array of email addresses associated with this identity

phoneNumbersarray of object

An array of phone numbers associated with this identity

creditCardsarray of string

An array of payment card numbers associated with this identity

cryptocurrencyWalletsarray of string

An array of cryptocurrency wallet addresses

urlsarray of string

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.

ip4Addressesarray of string

An array of IPv4 addresses to monitor

ip6Addressesarray of string

An array of IPv6 addresses to monitor

secondaryMatchItemsarray of object

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.

Response

200

The response body contains the requested results.

Body

application/json

matchesarray of object

An array of past exposures found for the provided identity

Request

JavaScriptCurlPython

const response = await fetch('https://api.enzoic.com/v1/identity-exposures', {
    method: 'POST',
    headers: {
      "Authorization": "basic <token>",
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      "firstName": "John",
      "lastName": "Doe",
      "country": "US"
    }),
});
const data = await response.json();

Response

200

{
  "matches": [
    {
      "exposureID": "text",
      "matchedItems": {
        "foundValue": "4111-1111-1111-1111",
        "queriedValue": 4111111111111111
      },
      "rawMatchSource": "Jimmy Dean\n2121 Cherrybrook Dr, Suite 200 Heisenberg, CO 12345\nSSN 232-44-3432\nMobile: [phone]\[e-mail]\nVisa 4111111111111111 03/28 444\nBTC Wallet 0xb794f5ea0ba39494ce839613fffba74279579268 (1.0233 balance)\nEIN: 12-3123122\nWells Fargo Checking - Account #900000001\n"
    }
  ]
}