RecruitmentSourcing

Candidate Research

Understand a candidate's current role, experience and employment history from their email alone.

Start with 500 free credits Documentation

Email identity · 1,000 credits per lookup · no monthly fee

How it works

One call, structured answer

Candidate Research runs on the email identity lookup at 1,000 credits per lookup. Same API key, same JSON shape as every other Encrata lookup.

A match on 99.86% of addresses, near-zero dead lookups
Every field is labelled found or not found, so you never guess what to trust
Ask only for the fields you need with the fields parameter
One API call replaces minutes of manual research per contact

Terminal

curl -X POST "https://encrata.com/api/agent/email-identity" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane@example.com"}'

response.json

{
  "email": "jane@example.com",
  "person": {
    "first_name": "Jane",
    "last_name": "Doe",
    "company": "Acme Inc",
    "job_role": "Head of Product",
    "city": "San Francisco",
    "socials": {
      "linkedin": "linkedin.com/in/janedoe"
    }
  },
  "credits": 1000
}

Resolve before the outreach

Run sourced lists through identity resolution before the outreach sequence: current role, employer and history land next to each address, so personalization becomes a merge field instead of a research task. Filter out candidates whose resolved current role matches the one you're pitching, nothing burns a talent brand like offering someone their own job.

Relevance lifts response rates

Response rates move because relevance moves: outreach that references the candidate's actual employer and trajectory reads as recruiting, not spam. The same data protects the pipeline downstream, resolved employment history flags the candidate who's been at their company three months (probably not moving) before a recruiter invests a sequence in them.