People Lookup

Overview

Find a person’s professional profile when you don’t have their LinkedIn URL but have other identifying information like their name, company domain, title, or location. This endpoint is perfect for lead generation and contact discovery workflows.

Authentication

X-API-KEY

string

required

Your Tuesday API key

Query Parameters

company_domain

string

required

Domain of the company (e.g., technova.com, sempersolaris.com)

first_name

string

required

First name of the person

last_name

string

Last name of the person (optional but recommended for better accuracy)

title

string

Job title or role (e.g., “Energy Consultant”, “Software Engineer”)

location

string

Location (city, state, or country) (e.g., “Florida”, “New York”, “United States”)

include_email

string

default:"exclude"

Include email address in the responseOptions: include | excludeAdditional Cost: +2 credits when set to include

include_phone

string

default:"exclude"

Include phone number in the responseOptions: include | excludeAdditional Cost: +3 credits when set to include

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”)

string

Email address (only when include_email=include)

mobile_number

string

Phone number (only when include_phone=include)

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?company_domain=sempersolaris.com&first_name=David&last_name=Addiss' \
--header 'X-API-KEY: your-api-key-here'

Example Response

{
    "data": {
        "city": "St Petersburg",
        "country": "United States",
        "country_code": "US",
        "country_region": "NORAM",
        "email": "[email protected]",
        "first_name": "David",
        "id": "tu_pacyf3uhs",
        "job_start_date": "2022-04-01",
        "last_name": "Addiss",
        "linkedin_url": "https://www.linkedin.com/in/david-addiss-4725189",
        "mobile_number": "+1 813-407-3977",
        "name": "David Addiss",
        "organization_id": "tu_oac4h5wgp",
        "organizations.founded_year": 2012,
        "organizations.linkedin_url": "https://www.linkedin.com/company/semper-solaris",
        "organizations.name": "Semper Solaris",
        "organizations.primary_domain": "sempersolaris.com",
        "organizations.website_url": "https://www.sempersolaris.com?utm_source=linkedin",
        "seniority": "Staff",
        "state": "Florida",
        "title": "Energy Consultant"
    },
    "statusCode": 200,
    "message": "Success"
}

Best Practices

Improve Match Accuracy

To get the most accurate results:

Always provide both first_name and last_name when possible
Include title to help disambiguate between people with the same name
Add location to further refine results
Ensure the company domain is accurate and current

Handle Multiple Matches

If multiple people match your criteria:

The API returns the best match based on all provided parameters
Add more specific criteria (title, location) to narrow results
Review the returned LinkedIn URL to verify it’s the correct person

Company Domain Tips

For best results with company domains:

Use the primary domain (e.g., google.com not gmail.com)
Check the company’s official website for the correct domain
Some companies may have multiple domains - try the main one first

Credit Usage

Base Lookup

Email Enrichment

Phone Enrichment

Error Responses

400 Bad Request - Missing Required Parameters

{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Missing required parameters: company_domain and first_name are required"
}

404 Not Found - No Match Found

{
    "statusCode": 404,
    "message": "Not Found",
    "error": "No profile found matching the provided criteria"
}

400 Bad Request - Invalid Domain

{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Invalid company domain format"
}

Use Cases

Lead Generation

Find contact information for prospects when you only know their name and company

CRM Data Cleanup

Enrich incomplete contact records with missing information

Sales Prospecting

Research specific individuals at target companies

Contact Discovery

Find the right person to contact at a company for specific roles

People Profile API - Get profile by LinkedIn URL
People Search API - Advanced search with multiple filters
Reverse Email Lookup - Find profile by email address
Reverse Phone Lookup - Find profile by phone number

Authentication

People APIs

Company APIs

Overview

Authentication

Query Parameters

Response

Example Requests

Example Response

Best Practices

Credit Usage

Error Responses

Use Cases

Lead Generation

CRM Data Cleanup

Sales Prospecting

Contact Discovery

Authentication

People APIs

Company APIs

​Overview

​Authentication

​Query Parameters

​Response

​Example Requests

​Example Response

​Best Practices

​Credit Usage

​Error Responses

​Use Cases

Lead Generation

CRM Data Cleanup

Sales Prospecting

Contact Discovery

​Related Endpoints

Overview

Authentication

Query Parameters

Response

Example Requests

Example Response

Best Practices

Credit Usage

Error Responses

Use Cases

Related Endpoints