Reverse Phone Lookup

Overview

Find a person’s professional profile using their phone number. This endpoint is useful for identifying unknown callers, enriching contact databases, and discovering professional information about phone contacts.

Authentication

X-API-KEY

string

required

Your Tuesday API key

Query Parameters

phone

string

required

Phone number to lookup (e.g., +14155552671, +1 713-408-6387)Format: International format with country code is recommended

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/phone?phone=%2B1%20713-408-6387' \
--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"
}

Phone Number Formats

Supported Formats

The API accepts various phone number formats:Recommended (International):

+1 713-408-6387
+14155552671
+44 20 7946 0958

Also Accepted:

(713) 408-6387
713-408-6387
7134086387

Best Practices

For optimal results:

Include country code when possible (e.g., +1 for US)
Use international format for non-US numbers
URL encode special characters in API requests
Ensure numbers are complete and valid

Credit Usage

Credit per lookup

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

Error Responses

400 Bad Request - Missing Phone Number

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

400 Bad Request - Invalid Phone Format

{
    "statusCode": 400,
    "message": "Bad Request",
    "error": "Invalid phone number format"
}

404 Not Found - Phone Not Found

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

Best Practices

Phone Number Quality

Business/mobile numbers typically have higher match rates
Landline numbers may have lower success rates
Recent numbers are more likely to return current information
Professional contact numbers yield better results than personal lines

Privacy Considerations

Only lookup phone numbers you have legitimate business reasons to research
Respect privacy laws and regulations in your jurisdiction
Consider opt-in/opt-out mechanisms for contact enrichment
Use results responsibly for business purposes

Data Validation

Verify phone numbers are properly formatted before lookup
Handle cases where numbers may have changed or been reassigned
Cross-reference results with other data points when possible

Use Cases

Caller Identification

Identify unknown business callers and prepare for conversations

Contact Enrichment

Add professional context to phone contacts in your database

Lead Verification

Verify legitimacy of phone-based leads and prospects

CRM Data Quality

Enhance phone contact records with professional information

Regional Considerations

United States & Canada

10-digit numbers: (555) 123-4567 or +1-555-123-4567
Business numbers typically have higher match rates
Mobile numbers increasingly used for professional contact

International Numbers

Always include country code: +44 20 7946 0958
Format varies by country - use standard international format
Business directories may be less comprehensive in some regions

Mobile vs. Landline

Mobile numbers often have better match rates for professionals
Business landlines may connect to multiple employees
Consider the number type when interpreting results

People Profile API - Get profile by LinkedIn URL
People Lookup API - Find people by name and company
Reverse Email Lookup - Find profile by email address
People Search API - Advanced search with multiple filters

Authentication

People APIs

Company APIs

Overview

Authentication

Query Parameters

Response

Example Requests

Example Response

Phone Number Formats

Credit Usage

Error Responses

Best Practices

Use Cases

Caller Identification

Contact Enrichment

Lead Verification

CRM Data Quality

Regional Considerations

Authentication

People APIs

Company APIs

​Overview

​Authentication

​Query Parameters

​Response

​Example Requests

​Example Response

​Phone Number Formats

​Credit Usage

​Error Responses

​Best Practices

​Use Cases

Caller Identification

Contact Enrichment

Lead Verification

CRM Data Quality

​Regional Considerations

​Related Endpoints

Overview

Authentication

Query Parameters

Response

Example Requests

Example Response

Phone Number Formats

Credit Usage

Error Responses

Best Practices

Use Cases

Regional Considerations

Related Endpoints