Reply logo

Get Contacts by List Name (Reply.io)

ReplyGet Contacts by List Name (Reply.io)

POST/v1/reply-get-contacts-by-list-name
texau__reply-get-contacts-by-list-nameintegration
cURL · api.texau.app
84ms
POST/v1/reply-get-contacts-by-list-name
{
  "list_name": "Jane Doe"
}
200 Accepted
{
  "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",
    "adding_date": "sample",
    "next_page_url": "https://acme.com",
    "previous_page_url": "https://acme.com"
  }
}

Retrieve a list of all contacts associated with a specific List Name from your Reply account.

Install

Add get contacts by list name (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.

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

Tool name: texau__reply-get-contacts-by-list-name

When to use this.

The "Get Contacts by List Name" action from Reply.io enables users to efficiently retrieve all contacts associated with a specified list name within their Reply account. This integration action requires a single input parameter, "listName," which is a string representing the name of the contact list from which to extract data. Upon execution, the action returns a comprehensive set of output fields, including total contacts, current page, total pages, and detailed contact information such as ID, email, first name, last name, company name, job title, phone number, city, state, country, LinkedIn profile URL, and adding date. This functionality is particularly useful for sales and marketing teams looking to manage and segment their contact lists effectively, facilitating targeted outreach and personalized communication strategies. By leveraging this action, users can streamline their contact management processes and enhance their engagement efforts.

Try it

Run a sample request.

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

Get Contacts by List Name (Reply.io)

Try it

The name of the list to retrieve contacts from.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • total
    Total
    nullablenumber
  • page
    Page
    nullablenumber
  • pages_count
    Pages Count
    nullablenumber
  • id
    Id
    number
  • email
    Email
    string
  • first_name
    First Name
    string
  • last_name
    Last Name
    string
  • company
    Company
    string
  • title
    Title
    nullablestring
  • mobile_number
    Mobile Number
    string
  • city
    City
    nullablestring
  • state
    State
    nullablestring
  • country
    Country
    nullablestring
  • linkedin_url
    Linkedin Url
    string
  • adding_date
    Adding Date
    nullablestring
  • next_page_url
    Next Page Url
    nullablestring
  • previous_page_url
    Previous Page Url
    nullablestring

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/reply-get-contacts-by-list-name. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/reply-get-contacts-by-list-name
curl -X POST 'https://v3-api.texau.com/api/v1/reply-get-contacts-by-list-name' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"list_name":"Jane Doe"}'
200 Accepted
{
  "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",
    "adding_date": "sample",
    "next_page_url": "https://acme.com",
    "previous_page_url": "https://acme.com"
  }
}

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 → get contacts by list name (reply.io) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Contacts by List Name (Reply.io)Reply 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 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.

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.

Light 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__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 Contacts by List Name (Reply.io) in 60 seconds.

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