> ## Documentation Index
> Fetch the complete documentation index at: https://developer.moltsets.com/llms.txt
> Use this file to discover all available pages before exploring further.
# LinkedIn to Mobile Phone
> The LinkedIn to Mobile Phone API looks up the carrier-verified mobile phone number for a LinkedIn profile, along with the date it was last verified.
Only mobile numbers are returned, no landlines or VoIP numbers, so every result is a real device. It supports single lookups (`linkedin_url`) and batch lookups of up to 100 profiles at once (`linkedin_urls`). External tokens are required for mobile phone lookups, at a cost of 10 tokens per returned result.
**Use this endpoint to:**
- Power SMS outreach and cold calling
- Enrich sales sequences with direct-dial mobile numbers
- Batch-append verified phone numbers to a contact list
**Fair Use Policy:**
This API is subject to our Fair Use Policy for Enrichment.
**External Tokens:**
MoltSets resolves most contact data — emails, phone numbers, et al. — from its own database. For some requests, the data you're looking for isn't in that database, and MoltSets will make a call to a third-party data source to try to find it. Those calls cost external tokens. For more information on external tokens, click here.
## OpenAPI
````yaml /openapi.json post /linkedin_to_mobile_phone
openapi: 3.1.0
info:
title: MoltSets API
version: 1.0.0
description: >-
MoltSets is an identity resolution API. Use it to resolve emails, LinkedIn
profiles, and IP addresses into enriched contact and company data, including
business and personal emails, mobile phone numbers, and firmographic
details.
servers:
- url: https://api.moltsets.com/api/v1/tools
description: Production
security:
- bearerAuth: []
tags:
- name: Search
description: >-
Search and filter company and business profiles by name, domain, industry,
size, or revenue.
- name: Get Valid Emails
description: Resolve and enrich valid business and personal email addresses.
- name: Get Carrier-Verified Mobile Phones
description: Enrich carrier-verified mobile phone numbers.
- name: Get Full Business Profile
description: Resolve identifiers to full business profiles and company firmographics.
- name: Get Ad Audience
description: >-
Resolve identifiers to hashed email (HEM) and mobile advertising IDs
(MAIDs) for audience matching.
- name: Get Company
description: Resolve IP addresses to company data.
- name: Account
description: Account management tools. Free — do not consume credits.
paths:
/linkedin_to_mobile_phone:
post:
tags:
- Get Carrier-Verified Mobile Phones
summary: LinkedIn to Mobile Phone
description: >-
The LinkedIn to Mobile Phone API looks up the carrier-verified mobile
phone number for a LinkedIn profile, along with the date it was last
verified.
Only mobile numbers are returned, no landlines or VoIP numbers, so every
result is a real device. It supports single lookups (`linkedin_url`) and
batch lookups of up to 100 profiles at once (`linkedin_urls`). External
tokens are required for mobile phone lookups, at a cost of 10 tokens per
returned result.
**Use this endpoint to:**
- Power SMS outreach and cold calling
- Enrich sales sequences with direct-dial mobile numbers
- Batch-append verified phone numbers to a contact list
**Fair Use Policy:**
This API is subject to our Fair Use Policy for Enrichment.
**External Tokens:**
MoltSets resolves most contact data — emails, phone numbers, et al. —
from its own database. For some requests, the data you're looking for
isn't in that database, and MoltSets will make a call to a third-party
data source to try to find it. Those calls cost external tokens. For
more information on external tokens, click here.
operationId: enrichPhone
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
linkedin_url:
type: string
description: Single LinkedIn profile URL.
linkedin_urls:
type: array
items:
type: string
maxItems: 100
description: Batch of LinkedIn profile URLs, up to 100.
examples:
single:
summary: Single lookup
value:
linkedin_url: https://linkedin.com/in/retentionadam
batch:
summary: Batch lookup
value:
linkedin_urls:
- https://linkedin.com/in/retentionadam
- https://linkedin.com/in/jane-doe
responses:
'200':
description: Success
content:
application/json:
examples:
found:
summary: Data found
value:
results:
mobile_phone: '5555555555'
last_validated_at: '2026-03-04'
status: ok
metadata:
fair_use:
records_remaining_5h: 179999
records_reset_5h: '2026-07-15T18:53:16Z'
records_remaining_1w: 899999
records_reset_1w: '2026-07-22T13:53:16Z'
external_tokens_used: 0
external_tokens_remaining: 5000
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorBadRequest'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorUnauthorized'
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorNotFound'
'422':
description: Invalid Input
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorInvalidInput'
'429':
description: Rate limit exceeded
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorRateLimit'
components:
schemas:
ErrorBadRequest:
type: object
properties:
error:
type: string
example: Bad Request
message:
type: string
example: >-
The server cannot process the request due to a client error (400 Bad
Request).
ErrorUnauthorized:
type: object
properties:
error:
type: string
example: Unauthorized
message:
type: string
example: Invalid API key.
ErrorNotFound:
type: object
properties:
error:
type: string
example: Not Found
message:
type: string
example: No match was found for the data provided.
ErrorInvalidInput:
type: object
properties:
error:
type: string
example: Invalid Input
message:
type: string
example: Message describing the nature of the invalid input.
ErrorRateLimit:
type: object
properties:
error:
type: string
example: Too Many Requests
message:
type: string
example: Rate limit exceeded. Maximum 100 requests per second.
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: >-
Pass your API key as a Bearer token. Keys follow the format
`ms_XXXXXXXXXXX`.
````