> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encrata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Response Fields

> Complete guide to every field returned by the Encrata Lookup API — what it means, where it comes from, and what to expect.

The Lookup API returns a rich profile object with **48 selectable fields** across 7 categories. You can request specific fields using the `fields` parameter, or omit it to get everything.

<Tip>
  In the [Sandbox](https://encrata.com/sandbox), hover over any field name to see a short description. This page provides the full reference.
</Tip>

***

## How field selection works

Pass a `fields` array in your request body to receive only the data you need. This reduces response size and speeds up processing.

```json theme={"dark"}
{
  "email": "satya@microsoft.com",
  "fields": ["first_name", "last_name", "company", "job_role", "breach_info"]
}
```

If `fields` is omitted or empty, **all fields** are returned.

***

## Data sources

Encrata aggregates data from multiple sources in a single API call:

| Source                    | Fields powered                                                                                                                                                         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Web Intelligence**      | Name, bio, company, job role, education, news, scholar, patents, videos, people\_also\_ask, related\_topics, company\_info                                             | Structured extraction from web search results, knowledge graphs, and Google Places                                                                                                                                                                                                                                                                                                                                                         |
| **Professional Networks** | Name, job role, company, industry, socials, education                                                                                                                  | Professional profile enrichment via ContactOut                                                                                                                                                                                                                                                                                                                                                                                             |
| **Email Validation**      | validity                                                                                                                                                               | Real-time mailbox verification via MillionVerifier                                                                                                                                                                                                                                                                                                                                                                                         |
| **Breach Database**       | breach\_info, breach\_exposed\_data                                                                                                                                    | Breach history from Have I Been Pwned (HIBP)                                                                                                                                                                                                                                                                                                                                                                                               |
| **Account Detection**     | registered\_services                                                                                                                                                   | Probes 219+ platforms to detect where the email is registered                                                                                                                                                                                                                                                                                                                                                                              |
| **IP Intelligence**       | location, security, ASN, company, domains, timezone, threat, malware, reverse\_dns, network, ports, blocklist, cloud, bgp, certificates, peering, fraud, threat\_feeds | Geolocation, threat detection, abuse reports, malware analysis, scanner classification, reverse DNS, WHOIS/RDAP allocation, open ports & CVEs (Shodan InternetDB + Censys), spam blocklists, cloud provider, BGP routing, crt.sh certificate transparency, PeeringDB operator/IXP context, proxy/fraud second opinions (proxycheck.io, IPQualityScore, Spur, Scamalytics, IPHub), and extra threat-intel feeds (AlienVault OTX, Pulsedive) |

***

## Person fields

Core identity and demographic data about the person.

| Field              | Type   | Description                                           | Example                              |
| ------------------ | ------ | ----------------------------------------------------- | ------------------------------------ |
| `first_name`       | string | Person's first/given name                             | `"Satya"`                            |
| `middle_name`      | string | Middle name, if available                             | `"Narayana"`                         |
| `last_name`        | string | Last/family name                                      | `"Nadella"`                          |
| `age`              | string | Estimated age (derived from public records)           | `"57"`                               |
| `gender`           | string | Gender — `Male`, `Female`, or empty if unknown        | `"Male"`                             |
| `ethnicity`        | string | Predicted ethnic background                           | `"South Asian"`                      |
| `nationality`      | string | Country of citizenship                                | `"American"`                         |
| `country`          | string | Country where the person is currently based           | `"United States"`                    |
| `city`             | string | City where the person is currently based              | `"Redmond"`                          |
| `birthplace`       | string | City/country where the person was born                | `"Hyderabad, India"`                 |
| `current_location` | string | Full current location string                          | `"Redmond, WA, US"`                  |
| `bio`              | string | Short biography or description                        | `"Chairman and CEO of Microsoft..."` |
| `photo_url`        | string | URL to the person's profile photo                     | `"https://..."`                      |
| `interests`        | string | Known hobbies, interests, or topics (comma-separated) | `"Cloud Computing, AI, Cricket"`     |

***

## Work fields

Professional and career information.

| Field      | Type   | Description                       | Example                           |
| ---------- | ------ | --------------------------------- | --------------------------------- |
| `company`  | string | Current employer or company name  | `"Microsoft"`                     |
| `job_role` | string | Current job title or position     | `"Chairman and CEO of Microsoft"` |
| `industry` | string | Industry sector                   | `"Technology"`                    |
| `website`  | string | Personal website or portfolio URL | `"https://microsoft.com"`         |

***

## Education fields

Academic background.

| Field             | Type   | Description                                   | Example                                                                |
| ----------------- | ------ | --------------------------------------------- | ---------------------------------------------------------------------- |
| `education`       | string | Comma-separated list of institutions attended | `"University of Wisconsin-Milwaukee, Manipal Institute of Technology"` |
| `education_level` | string | Highest education level achieved              | `"Master's"`                                                           |
| `university`      | string | Primary university or college                 | `"University of Wisconsin-Milwaukee"`                                  |
| `field_of_study`  | string | Major or area of study                        | `"Computer Science"`                                                   |

***

## Social fields

Links to social media profiles. Empty string if not found.

| Field       | Type   | Description           | Example                                  |
| ----------- | ------ | --------------------- | ---------------------------------------- |
| `linkedin`  | string | LinkedIn profile URL  | `"https://linkedin.com/in/satyanadella"` |
| `twitter`   | string | Twitter/X profile URL | `"https://twitter.com/satyanadella"`     |
| `instagram` | string | Instagram profile URL | `""`                                     |
| `facebook`  | string | Facebook profile URL  | `""`                                     |
| `github`    | string | GitHub profile URL    | `""`                                     |

***

## Company fields

Structured data about the person's employer, sourced from Google Places and Knowledge Graph.

| Field                  | Type    | Description                       | Example                                       |
| ---------------------- | ------- | --------------------------------- | --------------------------------------------- |
| `company_name`         | string  | Official registered company name  | `"Microsoft Corporation"`                     |
| `company_phone`        | string  | Company phone number              | `"+1-425-882-8080"`                           |
| `company_address`      | string  | Company physical address          | `"One Microsoft Way, Redmond, WA 98052"`      |
| `company_website`      | string  | Company website URL               | `"https://microsoft.com"`                     |
| `company_category`     | string  | Business category classification  | `"Technology company"`                        |
| `company_rating`       | number  | Google Maps star rating (1.0–5.0) | `4.1`                                         |
| `company_rating_count` | integer | Total number of Google reviews    | `25000`                                       |
| `company_price_level`  | string  | Price level indicator             | `"$$"`                                        |
| `company_latitude`     | number  | Company HQ latitude coordinate    | `47.6396`                                     |
| `company_longitude`    | number  | Company HQ longitude coordinate   | `-122.1283`                                   |
| `company_attributes`   | object  | Key-value pairs with extra info   | `{"Founded": "1975", "CEO": "Satya Nadella"}` |

<Note>
  Company fields are nested under `company_info` in the API response. In the Sandbox field selector, they appear as flat `company_*` fields for convenience.
</Note>

***

## Content fields

Media, publications, and web content related to the person.

### news

Recent news articles mentioning the person. Returns an array of objects.

| Sub-field | Type   | Description                                    |
| --------- | ------ | ---------------------------------------------- |
| `title`   | string | Article headline                               |
| `link`    | string | Article URL                                    |
| `date`    | string | Publication date                               |
| `source`  | string | Publisher name (e.g., "TechCrunch", "Reuters") |

### scholar

Academic papers and publications. Returns an array of objects.

| Sub-field   | Type    | Description               |
| ----------- | ------- | ------------------------- |
| `title`     | string  | Publication title         |
| `link`      | string  | URL to the paper          |
| `year`      | integer | Year published            |
| `cited_by`  | integer | Number of citations       |
| `published` | string  | Publisher or journal info |

### videos

Video appearances — talks, interviews, presentations. Returns an array of objects.

| Sub-field  | Type   | Description                     |
| ---------- | ------ | ------------------------------- |
| `title`    | string | Video title                     |
| `link`     | string | Video URL                       |
| `date`     | string | Upload or publish date          |
| `source`   | string | Platform (YouTube, Vimeo, etc.) |
| `channel`  | string | Channel name                    |
| `duration` | string | Video length                    |

### patents

Patents and inventions filed. Returns an array of objects.

| Sub-field   | Type   | Description          |
| ----------- | ------ | -------------------- |
| `title`     | string | Patent title         |
| `link`      | string | Patent URL           |
| `patent_id` | string | Patent ID or number  |
| `date`      | string | Filing or grant date |
| `inventor`  | string | Inventor name        |
| `assignee`  | string | Assignee company     |

### people\_also\_ask

Related questions from Google search results. Returns an array of objects.

| Sub-field  | Type   | Description         |
| ---------- | ------ | ------------------- |
| `question` | string | The question text   |
| `answer`   | string | Answer snippet      |
| `source`   | string | Source website name |
| `link`     | string | Source URL          |

### related\_topics

Related search queries. Returns a simple array of strings.

```json theme={"dark"}
["satya nadella net worth", "satya nadella wife", "satya nadella salary"]
```

***

## Security fields

Email security, breach exposure, and account detection.

### validity

Email deliverability status. Returns a single string value.

| Value        | Meaning                                    |
| ------------ | ------------------------------------------ |
| `valid`      | Mailbox exists and accepts email           |
| `invalid`    | Mailbox does not exist or rejects email    |
| `risky`      | Catch-all domain or temporary address      |
| `unknown`    | Could not determine (timeout, greylisting) |
| `disposable` | Disposable/throwaway email provider        |

### breach\_info

Data breach history powered by [Have I Been Pwned](https://haveibeenpwned.com/). Returns an object.

| Sub-field      | Type    | Description                                                                                                       |
| -------------- | ------- | ----------------------------------------------------------------------------------------------------------------- |
| `breach_count` | integer | Total number of breaches the email appears in                                                                     |
| `services`     | array   | List of breached services (name, domain, breach\_date, data\_types)                                               |
| `interests`    | array   | Inferred interest categories based on breach sources (e.g., Gaming sites → `{"category": "Gaming", "signal": 3}`) |
| `exposed_data` | array   | All unique data types leaked across all breaches (e.g., `["Passwords", "Email addresses", "IP addresses"]`)       |

Each item in `services`:

| Sub-field     | Type   | Description                                   |
| ------------- | ------ | --------------------------------------------- |
| `name`        | string | Breach name (e.g., "LinkedIn", "Adobe")       |
| `domain`      | string | Domain of the breached service                |
| `breach_date` | string | Date the breach occurred                      |
| `data_types`  | array  | Types of data exposed in this specific breach |

### breach\_exposed\_data

Shortcut to the `exposed_data` array inside `breach_info` — a flat list of all data types that were leaked across every breach (passwords, phone numbers, physical addresses, etc.).

### registered\_services

Detects which online services the email is registered on by probing login, registration, and password-reset flows across **219+ platforms** (GitHub, Spotify, Netflix, Adobe, etc.).

| Sub-field          | Type    | Description                                              |
| ------------------ | ------- | -------------------------------------------------------- |
| `total_checked`    | integer | Number of platforms probed                               |
| `registered_count` | integer | Number of platforms where the email is registered        |
| `services`         | array   | List of registered service names                         |
| `recovery_emails`  | array   | Partial recovery emails discovered during probing        |
| `recovery_phones`  | array   | Partial recovery phone numbers discovered during probing |

<Warning>
  **Recovery data** (partial emails/phones like `s***a@outlook.com` or `+1***456`) may be exposed by platforms during password reset flows. This is public information but should be handled carefully.
</Warning>

***

## Response structure

The full API response wraps fields inside the `person` object:

```json theme={"dark"}
{
  "email": "satya@microsoft.com",
  "person": {
    "first_name": "Satya",
    "last_name": "Nadella",
    "validity": "valid",
    "company": "Microsoft",
    "job_role": "Chairman and CEO of Microsoft",
    "socials": {
      "linkedin": "https://linkedin.com/in/satyanadella",
      "twitter": "https://twitter.com/satyanadella"
    },
    "company_info": {
      "name": "Microsoft Corporation",
      "rating": 4.1,
      "category": "Technology company"
    },
    "breach_info": {
      "breach_count": 2,
      "services": [{"name": "LinkedIn", "domain": "linkedin.com", "breach_date": "2012-05-05"}],
      "exposed_data": ["Email addresses", "Passwords"]
    },
    "registered_services": {
      "total_checked": 219,
      "registered_count": 8,
      "services": [{"name": "GitHub"}, {"name": "Spotify"}]
    },
    "news": [...],
    "scholar": [],
    "videos": [],
    "patents": []
  },
  "files": {
    "json": "/api/files/satya_at_microsoft_com.json",
    "csv": "/api/files/satya_at_microsoft_com.csv"
  }
}
```

<Info>
  Empty arrays (`[]`) and empty strings (`""`) indicate no data was found for that field. Objects like `company_info` and `breach_info` are omitted entirely if no data is available.
</Info>
