PeopleDB
Pricing | Sign in
Contact Intelligence API

Find the person
behind the profile.

Pass in a LinkedIn ID or GitHub handle. Get back verified emails, phone numbers, and social profiles — aggregated across multiple sources.

Get started → 10 free credits. No card required.

One call. Full picture.

Email addresses
Deduplicated across multiple sources. Automatically classified into personal_email_addresses and work_email_addresses.
Phone numbers
Direct dial numbers sourced and normalized from multiple providers.
Social profiles
GitHub login, LinkedIn ID, Twitter handle — cross-referenced automatically. Lookup by any identifier.
Email verification
Separate SMTP validation endpoint to confirm deliverability before you send.
GET /api/v1/people 
curl "https://peopledb.co/api/v1/people?github_login=dhh" \
  -H "Authorization: Bearer $TOKEN"

// ←
{
  "github_id": 2741,
  "github_login": "dhh",
  "email_addresses": [
    "david@hey.com",
    "david@loudthinking.com",
    "david@basecamp.com"
  ],
  "personal_email_addresses": ["david@hey.com"],
  "work_email_addresses": [
    "david@loudthinking.com",
    "david@basecamp.com"
  ]
}

Comparing options? See how PeopleDB stacks up against Clearbit, Apollo, ContactOut, and Hunter.

How it works

Aggregated across multiple providers.
Merged into one response.

Most enrichment APIs are thin wrappers around a single database. PeopleDB fans out across multiple independent data providers, cross-references results against the same LinkedIn or GitHub identifier, deduplicates email addresses, and classifies them — personal vs. work — before returning a single merged response. When one source carries a stale address, another often has the current one. That redundancy is the coverage guarantee.

The GitHub lookup is a different category of query. Developers leave a trail of real email addresses in their commit history — addresses that never appear on a resume, never get published to a contact directory, but are fully public in the git log. PeopleDB reconstructs these addresses from public GitHub event archives and matches them against commit author names. Pass a github_login or github_id and you get contact data that a conventional LinkedIn enrichment tool will miss entirely.

Before pushing an email address into your CRM or outbound sequence, run it through GET /api/v1/email_verifications. The endpoint connects directly to the recipient mail server, checks MX record configuration, probes mailbox existence, and identifies catch-all domains — without sending a message. Most checks resolve in under two seconds. Filtering undeliverable addresses before you send protects sender reputation and reduces bounce rate at the source.

For technical roles — engineering, product, and design — GitHub commit extraction surfaces contact data in a significant share of lookups that return no results from profile-based sources alone.