Skip to main content
POST
https://api.gtmapis.com
/
v1
/
mobile
/
find
Mobile Finder
curl --request POST \
  --url https://api.gtmapis.com/v1/mobile/find \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "email": "<string>",
  "linkedin_url": "<string>",
  "first_name": "<string>",
  "last_name": "<string>",
  "company": "<string>",
  "domain": "<string>"
}
'
{
  "mobile": "<string>",
  "mobile_raw": "<string>",
  "country_code": "<string>",
  "carrier": "<string>",
  "line_type": "<string>",
  "valid": true,
  "found": true,
  "confidence": 123,
  "source_provider": "<string>",
  "credits_charged": 123,
  "cache_hit": true,
  "latency_ms": 123
}

​
Mobile Finder

Discover mobile phone numbers for business contacts using email, LinkedIn URL, or name + company.

​
Endpoint

POST /v1/mobile/find

​
Request

At least one identifier is required: email, linkedin_url, or first_name + last_name.
​
email
string
Work email address
​
linkedin_url
string
LinkedIn profile URL
​
first_name
string
First name (requires last_name)
​
last_name
string
Last name (requires first_name)
​
company
string
Company name (helps narrow results when using name)
​
domain
string
Company domain (alternative to company name)

​
Example Request

curl -X POST https://api.gtmapis.com/v1/mobile/find \
  -H "Content-Type: application/json" \
  -H "X-API-Key: gtm_test_your_key_here" \
  -d '{
    "email": "john.doe@acme.com"
  }'

​
Response

​
mobile
string
Formatted mobile number (E.164 format, e.g., “+14155551234”)
​
mobile_raw
string
Raw mobile number as returned by provider
​
country_code
string
Country code (e.g., “US”, “GB”)
​
carrier
string
Mobile carrier name (when available)
​
line_type
string
Line type: mobile, landline, voip
​
valid
boolean
Whether the number passed validation
​
found
boolean
Whether a mobile number was found
​
confidence
integer
Confidence score (0-100)
​
source_provider
string
Data provider that returned the result
​
credits_charged
integer
Credits charged for this request
​
cache_hit
boolean
Whether result was served from cache
​
latency_ms
integer
Request time in milliseconds

​
Success Response

{
  "email": "john.doe@acme.com",
  "mobile": "+14155551234",
  "mobile_raw": "415-555-1234",
  "country_code": "US",
  "carrier": "Verizon Wireless",
  "line_type": "mobile",
  "valid": true,
  "found": true,
  "confidence": 85,
  "source_provider": "leadmagic",
  "credits_charged": 2,
  "cache_hit": false,
  "latency_ms": 478
}

​
Not Found Response

{
  "email": "john.doe@acme.com",
  "mobile": "",
  "valid": false,
  "found": false,
  "confidence": 0,
  "credits_charged": 0,
  "cache_hit": false,
  "latency_ms": 234
}

​
Credit Pricing

ResultCredits Charged
Mobile found2 credits
Not found0 credits
Error / failure0 credits
Mobile numbers are cached for 7 days. Cache hits are charged at the same rate.

​
Line Types

TypeDescription
mobileStandard cellular phone
landlineFixed-line phone
voipVoice over IP (Google Voice, etc.)

​
Error Responses

​
400 Bad Request

{
  "error": "Bad Request",
  "message": "email, linkedin_url, or first_name+last_name required"
}

​
401 Unauthorized

{
  "error": "Unauthorized",
  "message": "Invalid API key"
}

​
503 Service Unavailable

{
  "error": "Service Unavailable",
  "message": "mobile finder not configured"
}

​
Use Cases

Build call lists with verified mobile numbers for SDR teams.
Find mobile numbers for text-based outreach campaigns.
Reach executives directly when email isn’t getting responses.
Verify that contacts have valid mobile numbers before importing to dialers.

​
Best Practices

Email addresses have the highest match rate for mobile lookups.
Always check numbers against Do-Not-Call registries before calling.
Filter for line_type: mobile if you’re doing SMS campaigns.

Find Email

Find professional email addresses

Profile Enrichment

Get full contact profiles

Person Lookup

Find LinkedIn profiles