> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuesday.so/llms.txt
> Use this file to discover all available pages before exploring further.
# Reverse Email Lookup
> Retrieve a person's full profile by providing their email address
## 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
Your Tuesday API key
## Query Parameters
Email address to lookup (e.g., `john@xyz.com`, `mlindstrom@waypointsolutions.com`)
## Response
Unique identifier for the person
Full name of the person
First name
Last name
Current job title
Seniority level (e.g., "Staff", "Manager", "Director")
LinkedIn profile URL
Start date of current position (YYYY-MM-DD format)
Current city
Current state/region
Current country
Two-letter country code
Geographic region (e.g., "NORAM", "EMEA", "APAC")
Unique identifier for the person's current organization
Current organization name
Organization's LinkedIn URL
Organization's primary domain
Organization's website URL
Year the organization was founded
HTTP status code (200 for success)
Response message
## Example Requests
```bash cURL theme={null}
curl --location 'https://api.tuesday.so/api/v1/people/lookup/email?email=mlindstrom@waypointsolutions.com' \
--header 'X-API-KEY: your-api-key-here'
```
```javascript JavaScript theme={null}
const email = 'mlindstrom@waypointsolutions.com';
const params = new URLSearchParams({ email });
const response = await fetch(
`https://api.tuesday.so/api/v1/people/lookup/email?${params}`,
{
headers: {
'X-API-KEY': 'your-api-key-here'
}
}
);
const profile = await response.json();
console.log(profile);
```
```python Python theme={null}
import requests
url = "https://api.tuesday.so/api/v1/people/lookup/email"
params = {
"email": "mlindstrom@waypointsolutions.com"
}
headers = {
"X-API-KEY": "your-api-key-here"
}
response = requests.get(url, params=params, headers=headers)
profile = response.json()
print(profile)
```
```php PHP theme={null}
$email]);
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.tuesday.so/api/v1/people/lookup/email?$params");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-KEY: your-api-key-here'
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>
```
## Example Response
```json Response theme={null}
{
"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
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
```json theme={null}
{
"statusCode": 400,
"message": "Bad Request",
"error": "Missing required parameter: email"
}
```
```json theme={null}
{
"statusCode": 400,
"message": "Bad Request",
"error": "Invalid email address format"
}
```
```json theme={null}
{
"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
Enrich marketing lists with professional profile information
Verify and validate email addresses in your database
Research prospects from email campaigns before outreach
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
## Related Endpoints
* [People Profile API](/api-reference/people/profile) - Get profile by LinkedIn URL
* [People Lookup API](/api-reference/people/lookup) - Find people by name and company
* [Reverse Phone Lookup](/api-reference/people/lookup-phone) - Find profile by phone number
* [People Search API](/api-reference/people/search) - Advanced search with multiple filters