Get All Contacts (Reply.io)
Reply → Get All Contacts (Reply.io)
/v1/reply-get-all-people{}{ "ok": true, "data": { "total": 1, "page": 1, "pages_count": 1, "id": "rec_4f3a91", "email": "[email protected]", "first_name": "sample", "last_name": "sample", "company": "sample", "title": "sample", "mobile_number": "sample", "city": "sample", "state": "sample", "country": 1, "linkedin_url": "https://acme.com", "mobile_number_status": "valid", "adding_date": "sample", "previous_page_url": "https://acme.com" } }
Retrieves a paginated list of all contacts from Reply.io with metadata and contact details.
Install
Add get all contacts (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-all-people
When to use this.
The "Get All Contacts" action from Reply.io allows users to retrieve a comprehensive, paginated list of all contacts stored within the platform, complete with essential metadata and detailed contact information. This action does not require any input parameters, making it straightforward to use. The output includes critical fields such as total contacts, pagination details, and individual contact attributes like email, first name, last name, job title, company name, phone number, city, country, and LinkedIn profile URL. This functionality is particularly useful for CRM applications, enabling businesses to efficiently manage and analyze their contact database, streamline communication efforts, and enhance customer relationship management strategies. With its robust output structure, users can easily integrate this data into their workflows for improved engagement and outreach.
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
totalTotalnullablenumberpagePagenullablenumberpages_countPages CountnullablenumberidIdnumberemailEmailstringfirst_nameFirst Namestringlast_nameLast NamestringcompanyCompanystringtitleTitlestringmobile_numberMobile NumberstringcityCitynullablestringstateStatenullablestringcountryCountrystringlinkedin_urlLinkedin Urlstringmobile_number_statusMobile Number Statusnullablestringadding_dateAdding Datenullablestringprevious_page_urlPrevious Page Urlnullablestring
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/reply-get-all-people. Auth: x-api-key.
/v1/reply-get-all-peoplecurl -X POST 'https://v3-api.texau.com/api/v1/reply-get-all-people' \
-H 'x-api-key: $TEXAU_API_KEY' \
-H 'content-type: application/json' \
-d '{}'{ "ok": true, "data": { "total": 1, "page": 1, "pages_count": 1, "id": "rec_4f3a91", "email": "[email protected]", "first_name": "sample", "last_name": "sample", "company": "sample", "title": "sample", "mobile_number": "sample", "city": "sample", "state": "sample", "country": 1, "linkedin_url": "https://acme.com", "mobile_number_status": "valid", "adding_date": "sample", "previous_page_url": "https://acme.com" } }
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 all contacts (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 All Contacts (Reply.io) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.