Prospeo logo

Find Mobile Number by LinkedIn URL (Prospeo)

Prospeo → Find Mobile Number by LinkedIn URL (Prospeo)

POST/v1/prospeo-find-phone
texau__prospeo-find-phoneenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/prospeo-find-phone
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample",
    "mobile_number_status": "valid"
  }
}

Finds a mobile phone number from a LinkedIn profile URL via Prospeo.

Install

Add find mobile number by linkedin url (prospeo) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__prospeo-find-phone

When to use this.

The "prospeo-find-phone" action enables users to retrieve a mobile phone number associated with a specific LinkedIn profile URL through the Prospeo platform. By providing the input parameter "linkedin_url," which is the LinkedIn profile URL, users can seamlessly access relevant contact information. The action outputs two key fields: "phone," which delivers the retrieved mobile number, and "phone_status," indicating the validity or status of the phone number. This functionality is particularly useful for sales professionals, recruiters, and marketers seeking to enhance their outreach efforts and connect with potential leads or candidates. As part of the enrichment category, this action streamlines the process of gathering essential contact data, facilitating more effective networking and communication strategies.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Find Mobile Number by LinkedIn URL (Prospeo)

Try it

LinkedIn profile URL

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • mobile_number
    Mobile Number
    text
  • mobile_number_status
    Mobile Number Status
    text

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/prospeo-find-phone. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/prospeo-find-phone
curl -X POST 'https://v3-api.texau.com/api/v1/prospeo-find-phone' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample",
    "mobile_number_status": "valid"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Mobile Number by LinkedIn URL (Prospeo)→Find Mobile Number Using Full Name and Company Website (Prospeo)→Find Email Using Full Name and Company Website (Prospeo)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → find mobile number by linkedin url (prospeo) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Mobile Number by LinkedIn URL (Prospeo)Prospeo action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit300 / min
  • Per-day limit2,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Enterprise

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Prospeo actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__prospeo-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Find Mobile Number by LinkedIn URL (Prospeo) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs