Prospeo logo

Find Mobile Number Using Full Name and Company Website (Prospeo)

ProspeoFind Mobile Number Using Full Name and Company Website (Prospeo)

POST/v1/prospeo-find-mobile-number
texau__prospeo-find-mobile-numberenrichment
cURL · api.texau.app
84ms
POST/v1/prospeo-find-mobile-number
{
  "full_name": "Jane Doe",
  "company_website": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "mobile_number": "sample",
    "mobile_number_status": "valid"
  }
}

Finds a mobile phone number using a person's full name and company website via Prospeo.

Install

Add find mobile number using full name and company website (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-mobile-number

When to use this.

The "prospeo-find-mobile-number" action allows users to retrieve mobile phone numbers based on a person's full name and their associated company website through the Prospeo API. This enrichment tool requires two key input parameters: "full_name," which represents the individual's complete name, and "company_website," which specifies the domain of the organization they are linked to. Upon execution, the action outputs the "phone," which is the retrieved mobile number, and "phone_status," indicating the validity of the number. This functionality is particularly useful for sales teams, marketers, and recruiters seeking to enhance their contact databases, streamline outreach efforts, and improve lead generation strategies. By leveraging this API action, users can efficiently connect with potential clients or candidates, ensuring more effective communication and engagement.

Try it

Run a sample request.

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

Find Mobile Number Using Full Name and Company Website (Prospeo)

Try it

Full name

Comapny

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-mobile-number. Auth: x-api-key.

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

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 using full name and company website (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 Using Full Name and Company Website (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.

Heavy tier

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

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 Using Full Name and Company Website (Prospeo) in 60 seconds.

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