Reply logo

Get Campaign Details (Reply.io)

Reply → Get Campaign Details (Reply.io)

POST/v1/reply-get-campaign-details
texau__reply-get-campaign-detailsintegration
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/reply-get-campaign-details
{
  "campaign_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "created_at": "sample",
    "status": "valid",
    "owner_email": "[email protected]",
    "deliveries_count": 1,
    "opens_count": 1,
    "replies_count": 1,
    "bounces_count": 1,
    "people_active": 1
  }
}

Retrieves campaign statistics including status, step count, and lead count for a Reply.io campaign.

Install

Add get campaign details (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-campaign-details

When to use this.

The "Get Campaign Details" action for Reply.io allows users to retrieve comprehensive statistics for a specific marketing campaign, including its status, step count, and lead count. By providing the unique campaign ID as an input parameter, users can access detailed insights into their campaign's performance. The output includes critical data fields such as campaign ID, name, creation date, status code, owner email, and various metrics like deliveries count, opens count, replies count, bounces count, and active people count. This action is essential for marketers and sales teams looking to analyze campaign effectiveness, optimize engagement strategies, and improve overall communication efforts. It falls under the integration category, making it a valuable tool for seamless data management and reporting within marketing automation workflows.

Try it

Run a sample request.

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

Get Campaign Details (Reply.io)

Try it

The unique ID of the campaign to retrieve.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • id
    Id
    text
  • unique_name
    Unique Name
    string
  • created_at
    Created At
    nullablestring
  • status
    Status
    number
  • owner_email
    Owner Email
    nullablestring
  • deliveries_count
    Deliveries Count
    nullablenumber
  • opens_count
    Opens Count
    nullablenumber
  • replies_count
    Replies Count
    nullablenumber
  • bounces_count
    Bounces Count
    nullablenumber
  • people_active
    People Active
    nullablenumber

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/reply-get-campaign-details. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/reply-get-campaign-details
curl -X POST 'https://v3-api.texau.com/api/v1/reply-get-campaign-details' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"campaign_id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "created_at": "sample",
    "status": "valid",
    "owner_email": "[email protected]",
    "deliveries_count": 1,
    "opens_count": 1,
    "replies_count": 1,
    "bounces_count": 1,
    "people_active": 1
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get Campaign Details (Reply.io)→Push Existing Contact to Campaign (Reply.io)→Create Contact and Push to Campaign (Reply.io)

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 campaign details (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 Campaign Details (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.

Related

More Reply actions.

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 Campaign Details (Reply.io) in 60 seconds.

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

Start free →Read the API docs