Reverse Email Lookup

Overview

Find a person’s professional profile using their email address. This endpoint is perfect for enriching contact lists, validating email addresses, and discovering professional information about email contacts.

Authentication

X-API-KEY

string

required

Your Tuesday API key

Query Parameters

string

required

Email address to lookup (e.g., [email protected], [email protected])

Response

data

object

Show Person Profile Data

string

Unique identifier for the person

name

string

Full name of the person

first_name

string

First name

last_name

string

Last name

title

string

Current job title

seniority

string

Seniority level (e.g., “Staff”, “Manager”, “Director”)

linkedin_url

string

LinkedIn profile URL

job_start_date

string

Start date of current position (YYYY-MM-DD format)

city

string

Current city

state

string

Current state/region

country

string

Current country

country_code

string

Two-letter country code

country_region

string

Geographic region (e.g., “NORAM”, “EMEA”, “APAC”)

organization_id

string

Unique identifier for the person’s current organization

organizations.name

string

Current organization name

organizations.linkedin_url

string

Organization’s LinkedIn URL

organizations.primary_domain

string

Organization’s primary domain

organizations.website_url

string

Organization’s website URL

organizations.founded_year

number

Year the organization was founded

statusCode

number

HTTP status code (200 for success)

message

string

Response message

Example Requests

curl --location 'https://api.tuesday.so/api/v1/people/lookup/[email protected]' \
--header 'X-API-KEY: your-api-key-here'

Example Response

{
    "data": {
        "city": "Houston",
        "country": "United States",
        "country_code": "US",
        "country_region": "NORAM",
        "first_name": "Matthew",
        "id": "tu_pacdp5w2z",
        "job_start_date": "2017-03-01",
        "last_name": "Lindstrom",
        "linkedin_url": "https://www.linkedin.com/in/mrlindstrom1",
        "name": "Matthew Lindstrom",
        "organization_id": "tu_oacidb4kh",
        "organizations.founded_year": 1997,
        "organizations.linkedin_url": "https://www.linkedin.com/company/waypoint-solutions-llc",
        "organizations.name": "Waypoint Business Solutions",
        "organizations.primary_domain": "waypointsolutions.com",
        "organizations.website_url": "https://www.waypointsolutions.com",
        "seniority": "Staff",
        "state": "Texas",
        "title": "Senior Engineer"
    },
    "statusCode": 200,
    "message": "Success"
}

Credit Usage

Credit per lookup

Email reverse lookup uses 1 credit per request. Unlike other people endpoints, this doesn’t have additional enrichment options since the email is already provided.

Error Responses

400 Bad Request - Missing Email

{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Missing required parameter: email"
}

400 Bad Request - Invalid Email Format

{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Invalid email address format"
}

404 Not Found - Email Not Found

{
    "statusCode": 404,
    "message": "Not Found",
    "error": "No profile found for the provided email address"
}

Best Practices

Email Format

Ensure the email address is properly formatted
Use URL encoding for special characters in email addresses
Professional/work emails typically have higher match rates than personal emails

Data Quality

Results are most accurate for business/professional email addresses
Personal email addresses (Gmail, Yahoo, etc.) may have lower match rates
Corporate email addresses typically provide richer professional data

Bulk Processing

For multiple email lookups, respect rate limits (20 requests/minute)
Consider implementing retry logic for failed requests
Cache successful results to avoid duplicate requests

Use Cases

Email List Enrichment

Enrich marketing lists with professional profile information

Contact Verification

Verify and validate email addresses in your database

Lead Qualification

Research prospects from email campaigns before outreach

CRM Enhancement

Add professional context to email contacts in your CRM

Common Email Patterns

Corporate Email Formats

Common business email patterns that work well:

Domain Considerations

Company domains typically yield better results than generic providers
Look for emails using the company’s primary domain
Subsidiary domains may also contain valid professional profiles

People Profile API - Get profile by LinkedIn URL
People Lookup API - Find people by name and company
Reverse Phone Lookup - Find profile by phone number
People Search API - Advanced search with multiple filters

Authentication

People APIs

Company APIs

Overview

Authentication

Query Parameters

Response

Example Requests

Example Response

Credit Usage

Error Responses

Best Practices

Use Cases

Email List Enrichment

Contact Verification

Lead Qualification

CRM Enhancement

Common Email Patterns

Authentication

People APIs

Company APIs

​Overview

​Authentication

​Query Parameters

​Response

​Example Requests

​Example Response

​Credit Usage

​Error Responses

​Best Practices

​Use Cases

Email List Enrichment

Contact Verification

Lead Qualification

CRM Enhancement

​Common Email Patterns

​Related Endpoints

Overview

Authentication

Query Parameters

Response

Example Requests

Example Response

Credit Usage

Error Responses

Best Practices

Use Cases

Common Email Patterns

Related Endpoints