Find Mobile Number Using Full Name and Company Website (Prospeo)
Prospeo → Find Mobile Number Using Full Name and Company Website (Prospeo)
/v1/prospeo-find-mobile-number{ "full_name": "Jane Doe", "company_website": "https://acme.com" }
{ "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.
{ "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)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
mobile_numberMobile Numbertextmobile_number_statusMobile Number Statustext
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/prospeo-find-mobile-number. Auth: x-api-key.
/v1/prospeo-find-mobile-numbercurl -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"}'
{ "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.
enrichment
Find Email Using Full Name and Company Website (Prospeo)
Finds a professional email address using a person's full name and company website via Prospeo.
enrichment
Find Mobile Number by LinkedIn URL (Prospeo)
Finds a mobile phone number from a LinkedIn profile URL via Prospeo.
enrichment
Find Email by LinkedIn URL (Prospeo)
Finds a professional email address from a LinkedIn profile URL via Prospeo.
Output
Results land in a TexAu table.
Sample rows below.
Real result preview coming soon.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
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.
Built for
Who runs this.
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.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
Related
More Prospeo actions.
enrichment
Find Email Using Full Name and Company Website (Prospeo)
Finds a professional email address using a person's full name and company website via Prospeo.
enrichment
Find Mobile Number by LinkedIn URL (Prospeo)
Finds a mobile phone number from a LinkedIn profile URL via Prospeo.
enrichment
Find Email by LinkedIn URL (Prospeo)
Finds a professional email address from a LinkedIn profile URL via Prospeo.
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.