Skip to main content
GET
/
api
/
v1
/
people
/
lookup
/
email
Reverse Email Lookup
curl --request GET \
  --url https://api.tuesday.so/api/v1/people/lookup/email \
  --header 'X-API-KEY: <x-api-key>'
{
    "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"
}

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

email
string
required
Email address to lookup (e.g., john@xyz.com, mlindstrom@waypointsolutions.com)

Response

data
object
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?email=mlindstrom@waypointsolutions.com' \
--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

{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Missing required parameter: email"
}
{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Invalid email address format"
}
{
    "statusCode": 404,
    "message": "Not Found",
    "error": "No profile found for the provided email address"
}

Best Practices

  • 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
  • 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
  • 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

Common business email patterns that work well:
  • firstname.lastname@company.com
  • firstname@company.com
  • f.lastname@company.com
  • firstnamelastname@company.com
  • 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
I