Try requests in the browser. Loads about 1MB of JavaScript.

PeopleDB API

API for retrieving contact information and validating email addresses.

Base URL: https://peopledb.co/api/v1 · Authentication: Bearer token in the Authorization header · OpenAPI spec · peopledb.co · Pricing

GET /people — Get contact info

Retrieve contact information for a person by their LinkedIn ID, LinkedIn public identifier, GitHub ID, or GitHub login.

Query parameters

Name	Type	Required	Description
`linkedin_id`	integer	no	LinkedIn ID to search by
`linkedin_public_identifier`	string	no	LinkedIn public identifier (username) to search by
`github_id`	integer	no	GitHub ID to search by
`github_login`	string	no	GitHub login (username) to search by

Example

curl "https://peopledb.co/api/v1/people?linkedin_public_identifier=johndoe" \
  --header "Authorization: Bearer YOUR_SECRET_TOKEN"

Responses

200 — Profile found successfully
400 — Bad request - missing required parameters
401 — Unauthorized - invalid or missing bearer token
402 — Insufficient credits
404 — No profile found for the given parameters

Response fields

Field	Type	Description
`linkedin_id`	integer	LinkedIn ID
`linkedin_public_identifier`	string	LinkedIn public identifier (username)
`github_id`	integer	GitHub ID
`github_login`	string	GitHub login (username)
`email_addresses`	array of string	List of known email addresses. Only present when at least one address was found — absence means no email data is available.
`personal_email_addresses`	array of string	The subset of email_addresses on personal mail providers (Gmail, Outlook, and similar). Only present when email_addresses is present.
`work_email_addresses`	array of string	The subset of email_addresses on company domains. Only present when email_addresses is present.
`phone_numbers`	array of string	List of known phone numbers. Only returned when email_addresses is also present.
`github_username`	string	GitHub username
`facebook_username`	string	Facebook username
`twitter_username`	string	Twitter/X username

GET /email_verifications — Validate email address

Validate an email address and return detailed verification results.

Performs comprehensive validation including: Email syntax validation; MX record verification (DNS lookup); SMTP deliverability check; Disposable email detection; Common domain typo suggestions; Detection of servers that accept any email

Query parameters

Name	Type	Required	Description
`email_address`	string	yes	Email address to validate
`smtp_timeout`	integer	no	SMTP check timeout in seconds

Example

curl "https://peopledb.co/api/v1/email_verifications?email_address=user@example.com" \
  --header "Authorization: Bearer YOUR_SECRET_TOKEN"

Responses

200 — Email validation completed successfully
400 — Bad request - missing email_address parameter
401 — Unauthorized - invalid or missing bearer token

Response fields

Field	Type	Description
`email`	string	The email address that was validated
`valid`	boolean	Whether the email is considered valid
`classification`	string	Overall classification of the email: - `valid`: Email passed all checks cleanly - `risky`: Email is valid but has concerns (accepts any email, DNS/SMTP assumptions, disposable email, or warnings) - `invalid`: Email validation failed
`score`	integer	Validation score from 0-100. Higher scores indicate higher confidence. Scoring breakdown: - Syntax valid: +20 points - MX verified: +40 points (or +15 if assumed) - SMTP verified: +35 points (or +15 if accepts any email, +10 if assumed) - No SMTP check: +20 points - Warning penalty: Up to -25 points
`score_details`	object	Detailed breakdown of validation scoring factors
`errors`	array of string	List of validation errors encountered
`warnings`	array of string	List of validation warnings
`checks`	object	Individual validation check results

POST /email_verifications — Validate email address

Validate an email address and return detailed verification results.

This endpoint performs the same validation as GET but accepts parameters via request body or form data.

Query parameters

Name	Type	Required	Description
`email_address`	string	yes	Email address to validate
`smtp_timeout`	integer	no	SMTP check timeout in seconds

Example

curl --request POST \
  "https://peopledb.co/api/v1/email_verifications?email_address=user@example.com" \
  --header "Authorization: Bearer YOUR_SECRET_TOKEN"

Responses

200 — Email validation completed successfully
400 — Bad request - missing email_address parameter
401 — Unauthorized - invalid or missing bearer token

Response fields

Field	Type	Description
`email`	string	The email address that was validated
`valid`	boolean	Whether the email is considered valid
`classification`	string	Overall classification of the email: - `valid`: Email passed all checks cleanly - `risky`: Email is valid but has concerns (accepts any email, DNS/SMTP assumptions, disposable email, or warnings) - `invalid`: Email validation failed
`score`	integer	Validation score from 0-100. Higher scores indicate higher confidence. Scoring breakdown: - Syntax valid: +20 points - MX verified: +40 points (or +15 if assumed) - SMTP verified: +35 points (or +15 if accepts any email, +10 if assumed) - No SMTP check: +20 points - Warning penalty: Up to -25 points
`score_details`	object	Detailed breakdown of validation scoring factors
`errors`	array of string	List of validation errors encountered
`warnings`	array of string	List of validation warnings
`checks`	object	Individual validation check results