Get Contact by Email (Reply.io)
Reply → Get Contact by Email (Reply.io)
/v1/reply-get-contact-by-email{ "email": "[email protected]" }
{ "ok": true, "data": { "id": "rec_4f3a91", "email": "[email protected]", "first_name": "sample", "last_name": "sample", "company": "sample", "title": "sample", "mobile_number": "sample", "mobile_number_status": "valid", "city": "sample", "state": "sample", "country": 1, "time_zone_id": "rec_4f3a91", "linkedin_url": "https://acme.com", "adding_date": "sample", "company_size": "sample", "industry": "sample", "sales_navigator_url": "https://acme.com", "linkedin_recruiter_url": "https://acme.com", "account_id": 1 } }
Retrieve details for a specific contact using their email address.
Install
Add get contact by email (reply.io) 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__reply-get-contact-by-email
When to use this.
The "Get Contact by Email" action in Reply.io allows users to efficiently retrieve detailed information about a specific contact using their email address. By providing the email as a dynamic input parameter, users can access a wealth of data, including the contact's ID, first and last names, company affiliation, job title, phone number, and geographical location (city, state, country). The output also includes LinkedIn profile links, time zone information, and additional details such as company size and industry. This action is particularly useful for CRM applications, enabling sales and marketing teams to quickly gather essential contact information for lead generation, customer relationship management, and targeted outreach campaigns. With its focus on semantic types like email, name, and company data, this action enhances user efficiency in managing and leveraging contact information.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Get Contact by Email (Reply.io)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
idIdnumberemailEmailstringfirst_nameFirst Namestringlast_nameLast NamestringcompanyCompanystringtitleTitlestringmobile_numberMobile Numberstringmobile_number_statusMobile Number StatusnullablestringcityCitynullablestringstateStatenullablestringcountryCountrynullablestringtime_zone_idTime Zone Idnullablestringlinkedin_urlLinkedin Urlstringadding_dateAdding Datenullablestringcompany_sizeCompany SizenullablestringindustryIndustrynullablestringsales_navigator_urlSales Navigator Urlnullablestringlinkedin_recruiter_urlLinkedin Recruiter Urlnullablestringaccount_idAccount Idnullablenumber
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/reply-get-contact-by-email. Auth: x-api-key.
/v1/reply-get-contact-by-emailcurl -X POST 'https://v3-api.texau.com/api/v1/reply-get-contact-by-email' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"email":"[email protected]"}'
{ "ok": true, "data": { "id": "rec_4f3a91", "email": "[email protected]", "first_name": "sample", "last_name": "sample", "company": "sample", "title": "sample", "mobile_number": "sample", "mobile_number_status": "valid", "city": "sample", "state": "sample", "country": 1, "time_zone_id": "rec_4f3a91", "linkedin_url": "https://acme.com", "adding_date": "sample", "company_size": "sample", "industry": "sample", "sales_navigator_url": "https://acme.com", "linkedin_recruiter_url": "https://acme.com", "account_id": 1 } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
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 → get contact by email (reply.io) → 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 limitNo public cap
- Per-day limitPlan-defined
- 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. |
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__reply-...` 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 Get Contact by Email (Reply.io) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.