---
title: "LinkedIn to Mobile Phone"
method: POST
path: "/linkedin_to_mobile_phone"
tags: ["Get Carrier-Verified Mobile Phones"]
---

# LinkedIn to Mobile Phone

`POST /linkedin_to_mobile_phone`

## Request

- Base URL: `https://api.moltsets.com/api/v1/tools`
- URL: `https://api.moltsets.com/api/v1/tools/linkedin_to_mobile_phone`
- Auth: HTTP bearer

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`). Mobile lookups spend **phone tokens** at 1 phone token per returned result. Phone tokens are separate from your regular token balance and aren't included in any plan: they come from a monthly phone token subscription, available on paid plans only. Unused phone tokens roll over while the subscription is active.

**Numbers are not screened against Do Not Call registries.** MoltSets does not currently return DNC status, and a returned number carries no indication of whether it is registered. `last_validated_at` tells you the number was active and in service on that date, nothing more. Scrubbing against the applicable DNC registries, and complying with the calling and messaging rules that apply to you, remains your responsibility.

**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 <a href="https://moltsets.com/fair-use-policy-enrichment/" target="_blank" rel="noopener">Fair Use Policy for Enrichment</a>.

**Outcomes:**
A lookup that finds nothing is not an error. It returns HTTP `200` with `status: "not_found"`, empty or null `results`, and the usual `metadata` — and costs no tokens, though it still counts as one request against your Fair Use requests limit. Read `status`, not the HTTP code, to tell a hit from a miss. The API's only `404` is an unknown or retired tool name.

## Headers

- `User-Agent` string, required

## Request body

- object
  - `linkedin_url` string: Single LinkedIn profile URL.
  - `linkedin_urls` string[]: Batch of LinkedIn profile URLs, up to 100.

## Response `200`

Success

## Other responses

- `401`: Unauthorized
- `402`: Payment Required — out of tokens or phone tokens
- `403`: Forbidden — missing `User-Agent` header, tool not on the plan, or account inactive
- `422`: Invalid Input — malformed body, or a parameter is missing, malformed, or outside its allowed values
- `429`: Too Many Requests — rate limit or Fair Use window exhausted
- `500`: Internal Server Error — the call could not complete. Usually the endpoint is temporarily unavailable, but an oversized request can also cause it. Retry with a smaller request first; the MoltSets team is alerted automatically.

---

[API](https://skmtc.dev/moltsets/apis/moltsets-api.md) - [All operations](https://skmtc.dev/moltsets/apis/moltsets-api/llms.txt) - [OpenAPI document](https://skmtc.dev/moltsets/apis/moltsets-api/revisions/b116df68bd90?raw)