https://reply.io logo
#announcements
  • d

    deactivateduser

    05/06/2026, 10:46 AM
    👋 Welcome to the Reply.io API community! This Slack is the place for anyone building with or connecting to Reply — whether you're enjoying the API directly, wiring up flows in n8n or plugging Reply into your AI agent through the Reply MCP server. Whether you write code, drag-and-drop in n8n, or just want to talk to other people automating their outreach — you're in the right place. Quick tour of the channels: 📢 #C0B02EDRC1X — Release notes, new endpoints, breaking changes, n8n / MCP updates. Check here first before asking "is X live yet?" 💬 #C0B02SVE8QH — Feature requests, ideas, "it would be great if Reply could…", rough edges in the API or n8n node. The dev team reads this. Upvote with 👍 on the messages you care about. 🆘 #C0B22AGCP8U — Stuck on something? Unexpected error, n8n workflow not firing, MCP tool returning weird results? Drop a thread here. To get help quicker, please include: • What you're trying to do (the goal, not just the symptom) • The endpoint / n8n action / MCP tool involved • The request you sent and the response/error you got (redact secrets!) A few house rules: 🔒 Never paste your API key, OAuth token, or other secrets in public channels. If you need to share a real example, DM the responder. 🧵 Keep replies in threads so the channels stay easy to scan. 🌍 Be kind, assume good faith, help each other out.
    🙌 1
  • d

    Dasha

    05/14/2026, 4:53 PM
    📢 New Webhook Event: 
    linkedin_account_alerts
     Hey everyone! 👋 We've shipped a new webhook event that lets you stay on top of LinkedIn account health in real time. Instead of finding out after a sequence stalls, you'll get notified the moment something needs attention. What you'll be alerted about: • 🔌 Sales Navigator disconnected - reconnect needed to keep InMail steps running • 💬 InMail credits depleted - the account can't send InMails until credits renew • 🔒 Weekly connection request limit reached - sending resumes after LinkedIn resets the quota Why this matters: Build automations that auto-pause sequences, ping the account owner in Slack, open a ticket, or trigger any custom recovery flow, no more silent failures. Example payloads: Sales Navigator disconnected
    Copy code
    {
  "event": {
    "date": "2026-05-13T10:45:46.3926107Z",
    "id": "22ff637a-fd81-40ba-b597-0c8f26189dca",
    "type": "linkedin_account_alerts",
    "user_id": 12345,
    "team_id": 67890,
    "subscription_id": 492
  },
  "workspace_id": 67890,
  "workspace_name": "Default Team",
  "linkedin_owner_name": "Jane D.",
  "linkedin_owner_email": "<mailto:jane.d@example.com|jane.d@example.com>",
  "linkedin_id": 262,
  "linkedin_name": "Jane Doe",
  "linkedin_account_alert": "Sales Navigator is disconnected. Please reconnect your LinkedIn account to continue sending InMail steps.",
  "sequence_fields": {}
}
    InMail credits depleted
    Copy code
    {
  "event": {
    "date": "2026-05-13T10:47:16.6543506Z",
    "id": "7227258a-8624-410a-bf6c-bd5197810d66",
    "type": "linkedin_account_alerts",
    "user_id": 12345,
    "team_id": 67890,
    "subscription_id": 492
  },
  "workspace_id": 67890,
  "workspace_name": "Default Team",
  "linkedin_owner_name": "Jane D.",
  "linkedin_owner_email": "<mailto:jane.d@example.com|jane.d@example.com>",
  "linkedin_id": 262,
  "linkedin_name": "Jane Doe",
  "linkedin_account_alert": "InMail credits are used up — this account can't send InMails until credits renew.",
  "sequence_fields": {}
}
    Weekly connection limit reached
    Copy code
    {
  "event": {
    "date": "2026-05-13T10:47:27.4486303Z",
    "id": "654258f1-a426-4d3c-96a2-b3da5f78af29",
    "type": "linkedin_account_alerts",
    "user_id": 12345,
    "team_id": 67890,
    "subscription_id": 492
  },
  "workspace_id": 67890,
  "workspace_name": "Default Team",
  "linkedin_owner_name": "Jane D.",
  "linkedin_owner_email": "<mailto:jane.d@example.com|jane.d@example.com>",
  "linkedin_id": 262,
  "linkedin_name": "Jane Doe",
  "linkedin_account_alert": "Weekly connection request limit reached. Sending new connection requests will resume after LinkedIn resets the quota.",
  "sequence_fields": {}
}
    📚 Full docs: https://docs.reply.io/webhook-event-payloads#linkedin_account_alerts Would love to hear what you build with it, drop a comment or share your workflow! 🚀
    🎉 3
    🔥 1
    • 1
    • 1
  • d

    Dasha

    05/18/2026, 12:37 PM
    🛠️ New: Webhooks Management Page (v3) Hey folks! 👋 Following up with another shipment, we've added a dedicated Webhooks page where you can manage your v3 webhook subscriptions directly from the UI. No more juggling subscriptions through API calls only. Availability: Currently rolled out for Beta users, wider release coming soon. 🎥 Quick walkthrough from our product team below ⬇️ Got feedback or feature requests for the page? Drop them in the thread, we're actively iterating. 🚀
    Webhook page_demo.mov
    🎉 2
    🔥 2
    • 1
    • 1
  • d

    Dasha

    05/27/2026, 3:18 PM
    🚀 New API Endpoints: Inbox, Background Jobs & Email Validations Hey everyone 👋 We've just shipped a fresh batch of brand-new endpoints. Three entirely new sections in the API where there was nothing before: 📥 Inbox ⚙️ Background Jobs ✅ Email Validations Inbox status: most endpoints are live and ready to use. Two are still coming soon (we wanted to give you a heads-up so you can plan ahead): • Generate an AI draft reply • Submit feedback on a generated AI draft Background Jobs & Email Validations: all endpoints are live and ready to go. 🎉 Have a look, build something cool, and drop your feedback in the thread. Especially curious to hear what you're planning for the AI draft endpoints once they ship.
    🎉 1
  • d

    Dasha

    06/08/2026, 5:41 PM
    📢 Reply API V3 — Changelog (June 5) Hey folks! 👋 We've shipped a chunky batch of API updates - full AI SDR Sequences coverage, new Live Data + Intent Signals typeahead endpoints, and a few breaking changes worth a quick look before your next deploy. Quick rundown below 👇 ────────────────────────────── 🚨 Breaking changes — please check these 1️⃣ 
    totalCount
    removed from Contacts endpoints
    Affects 
    GET /v3/contacts
    · 
    POST /v3/contacts/filter
    Response now returns only 
    items
    + 
    hasMore
    . If you read 
    totalCount
    , switch to cursor-style pagination using 
    hasMore
    .
    2️⃣ Sequence Preview feedback path moved — now under the 
    ai-sdr
    segment: 
    /v3/sequences/ai-sdr/{id}/contacts/{id}/preview/steps/{step_id}/feedback
    3️⃣ Tag renames 
    AI SDR Live Data
    → 
    Live Data
    · 
    AI SDR Contact Enrichment
    → 
    Contact Enrichment
    · 
    JasonAi credits
    → 
    Reply credits
    ────────────────────────────── ✨ AI SDR Sequences — now fully covered All 14 endpoints are live under 
    /v3/sequences/ai-sdr/{id}
    (Create = base path, no 
    {id}
    ):
    Copy code
    Action                         Method          Path
Create sequence                POST            (base)
Get settings                   GET             /settings
Update settings                PATCH           /settings
Enable autopilot               POST            /autopilot/enable
Disable autopilot              POST            /autopilot/disable
Force-start autopilot          POST            /autopilot/force-start
Set approval mode              PUT             /approval-mode
Set generated step types       PUT             /generated-step-types
Get/Set/Remove playbook        GET/PUT/DELETE  /playbook
Get/Set/Remove knowledge base  GET/PUT/DELETE  /knowledge-base
    Heads up on force-start errors: 
    409 autopilotDisabledByContactsLimit
    (limit reached) · 
    409 autopilotDisabledByLackOfContacts
    (no contacts) · 
    404
    on playbook/KB DELETE when nothing's attached.
    ✨ More new endpoints • Intent Signals (typeahead) — 
    GET /v3/ai-sdr/intent-signals/industries
    · 
    …/technologies
    ⚠️ These return Sales Navigator strings — different from Live Data filter-value industries (Reply taxonomy), so don't mix them up. • Live Data Filter Values are live (finally off "coming soon" 🎉) — 5 typeahead endpoints under `/v3/live-data/filter-values`: industries · departments · seniorities · locations · job-titles ────────────────────────────── 🔧 Smaller improvements • Inbox — filter by owner via new `ownerUserId`: 
    POST /v3/inbox/threads/filter
    (body, integer nullable) and 
    GET /v3/inbox/threads/categories
    (query param, integer). Target user must be on your team, else 
    400
    . • Rate limiting — all 
    429
    responses now include a 
    Retry-After
    header (integer, seconds) so you can back off cleanly. • Sidebar reordered to strict A–Z, parent-first grouping. • Auth guide rewritten — now covers Master API key + Organization API key (with impersonation details). ────────────────────────────── 📚 Full docs: https://docs.reply.io/api-reference Questions or hit a snag migrating? Drop them in the thread 🧵
  • d

    Dasha

    06/15/2026, 5:12 PM
    🚀 Reply API V3 — Changelog TL;DR: AI-drafted replies now surface in the Inbox API, companyDescription limits triple to 3,000 chars, and the AI SDR Pending Approvals API is fully documented ahead of its mid-June release. One breaking change — the AI voice LinkedIn endpoint drops playback-speed settings. 🟢 New: live now Inbox - AI Draft support GET /v3/inbox/threads/{id} now returns AI reply data: • aiDraft (nullable) - pending AI-drafted reply: message (HTML), cc, bcc, attachments. null if no active draft. • aiSentType (nullable) on email & LinkedIn messages - aiGenerated / aiGeneratedEdited / autoSent. Offers: larger company description • companyDescription max length raised 1,000 → 3,000 on create + patch. icp / reasonForOutreach stay 1,000. 🔜 Coming soon - targeted late-June 2026 AI SDR Pending Approvals - full API coverage • GET /v3/ai-sdr/approvals — list (filters sequenceId / userId / channel / sortMode, top/skip) • POST /v3/ai-sdr/approvals/send-bulk — batch of 1–20 pairs • GET|POST|DELETE /v3/sequences/ai-sdr/{sequence_id}/contacts/{contact_id}/approval[/send|/regenerate] • Regenerate is async: returns 202 {jobId} → poll GET /v3/background-jobs/{jobId} for subject/body. • Reject discards the draft and removes the contact from the sequence. AI SDR Sequences - limits & error contract • companyDescription 1,000 → 3,000 on offer-generation inputs. • Intent signals: technologyUsed & jobHiring now mutually exclusive. • Email-only sequences reject contacts without an email address. ⚠️ Breaking change
    AI voice LinkedIn message - playback speed removed
    Before: body accepted textToSpeechSettings with a speed multiplier.
    After: textToSpeechSettings / speed removed; only text is accepted.
    Action required: remove textToSpeechSettings from your request body - it has no effect.
    📚 Full docs: https://docs.reply.io/api-reference
  • d

    Dasha

    06/30/2026, 3:45 PM
    🚀 Reply API V3 — Changelog (June 30, 2026)
    TL;DR: Mostly AI SDR + Live Data roadmap — search, autopilot-preview, and per-contact personalization endpoints are now fully documented ahead of their mid-June 2026 launch (still Coming Soon, not callable yet). The one live change is cosmetic: direct-outreach sends moved into their own Direct Outreach section.
    🟢 Now Live Direct Outreach — sends get their own section. The 6 direct-send endpoints (already beta) moved out of Contacts into a new Direct Outreach group. Paths, methods, and behavior are unchanged — docs grouping only, no action needed. 🔜 Coming Soon (not callable yet) Live Data — Search API • Preview a search — 
    POST /v3/live-data/searches/preview
    → 
    202 {jobId}
    (no prospects, no credits) • Start a search — 
    POST /v3/live-data/searches
    → 
    200 {searchId}
    (note: 200, not 202; consumes credits) • List searches — 
    GET /v3/live-data/searches
    (default 
    top
    100) • Get a search — 
    GET /v3/live-data/searches/{id}
    New 
    422 liveDataSearch.noMatchingContacts
    . Status enum: 
    inProgress
    / 
    finished
    / 
    noMoreContacts
    / 
    manuallyPaused
    / 
    pausedDueToInsufficientCredits
    . AI SDR — Autopilot preview • 
    POST /v3/sequences/ai-sdr/{sequence_id}/autopilot/preview
    → 
    202 {jobId}
    , poll 
    GET /v3/background-jobs/{id}
    for 
    {contactsCount, companiesCount, sampleContacts}
    . Try-before-save: filter config doesn't need saving first. AI SDR — Sequence preview & personalization • Get preview — 
    GET /v3/sequences/{sequence_id}/contacts/{contact_id}/preview
    (generic, not AI-SDR-only) • Reset preview — 
    POST .../preview/reset
    • Personalize — 
    POST /v3/sequences/ai-sdr/{sequence_id}/contacts/{contact_id}/preview/personalize
    → 
    202 {jobId}
    , progress 
    personalizedSteps/totalSteps
    Early adopters: personalization endpoint renamed from 
    .../personalization/start
    to `.../preview/personalize`; bulk stub removed. Never shipped, so no live impact.
    🔧 Housekeeping • New Direct Outreach tag (after Custom Fields) • Live Data list + AI SDR Approvals list 
    top
    default corrected 25 → 100 • Live Data search status enum casing fixed to camelCase • 
    totalSteps
    documented in the personalization job result 📚 Full docs: docs.reply.io/api-reference
  • d

    Dasha

    07/08/2026, 3:51 PM
    Hey everyone 👋 We've just released a new, extended version of our MCP! We've significantly expanded the functionality, so I'd recommend reconnecting to pick up all the updates. Enjoy, and please share your feedback, we'd love to hear your thoughts and ideas. All the details here: docs.reply.io/reply-mcp P.S. @Hessan Haiderzada, you've been especially interested in MCP, so tagging you directly, I think you'll want to give this a spin 🙂
    🎉 1
    ❤️ 1
  • d

    Dasha

    07/17/2026, 11:17 AM
    🚀 Reply API V3 — Changelog (July 16, 2026)
    TL;DR: Sequence sorting & date filters, 
    emailProvider
    on contact accounts, new team-users endpoint. Counts, unarchive, CSV export & email stats documented ahead of July releases.
    🟢 Now Live • Workspace — 
    GET /v3/whoami/team-users
    lists all users in your team: 
    teamId
    , 
    teamName
    , 
    userId
    , 
    userName
    , 
    userEmail
    • Sequences — 
    GET /v3/sequences
    gains 
    sortBy
    (`created`/`name`/`status`), 
    sortDirection
    (`asc`/`desc`, requires 
    sortBy
    ), 
    createdAfter
    (ISO-8601); invalid sort → 
    400 sequence.invalidSort
    • Contact Accounts — single-account responses add read-only 
    emailProvider
    , resolved from the domain's MX records (
    gSuite
    , 
    office
    , 
    gmail
    , …); 
    null
    when undetermined • AI SDR Reply Handlers (beta) — new 
    deliveryMode
    (`draft`/`auto`/`stopAndNotify`) + `additionalNotificationEmail`; 
    stopAndNotify
    is feature-gated → 
    403 knowledgeBase.stopAndNotifyNotEnabled
    🔜 Coming Soon late July 2026: • Counts (return 
    {"count": N}
    ): 
    POST /v3/contacts/filter/count
    • 
    GET /v3/sequences/count
    • 
    GET /v3/sequences/{id}/contacts/count
    • Unarchive: 
    POST /v3/sequences/{id}/unarchive
    • 
    POST /v3/sequences/unarchive
    (bulk, 1–100 ids, non-atomic) • Email account stats: 
    GET /v3/email-accounts/{id}/stats
    • 
    POST /v3/email-accounts/stats
    (
    emailsSentToday
    , 
    totalEmailsSent
    , 
    dailySendingLimit
    ) mid-July 2026: • 
    GET /v3/holiday-calendars/{id}/export-csv
    — CSV download, filename = calendar name 📚docs.reply.io/api-reference/introduction
  • d

    Dasha

    07/27/2026, 3:27 PM
    🚀 Reply API V3 — Changelog (July 27, 2026) TL;DR: New beta endpoint for a contact's inbox threads, a new channel-agnostic 
    contact_replied
    webhook, 
    email_replied
    now fires on every email reply (was first-reply-only), richer 
    sequence_fields
    on all sequence webhooks — and one breaking change: 
    email_replied
    dropped its 
    reason
    field. All webhook changes are v3 only — v2 is untouched. 🟢 Now Live Contacts — inbox threads on a contact's timeline (Beta) • 
    GET /v3/contacts/{id}/inbox-threads
    — email/LinkedIn threads for a contact; paged 
    top
    (default 25, max 1000) / `skip`; scope 
    contacts:read
    . New Contact Inbox Thread schema. Inbox — reply to a specific message • 
    messageId
    (string, nullable) now returned on email & LinkedIn messages. • 
    replyToMessageId
    (string, nullable) on the email send request — omit to reply to the last message in the thread. Webhooks — 
    email_replied
    now fires on every reply • Previously it fired only on the first reply from a contact, so any replies after that weren't tracked. Now you get an event for every new email reply. Webhooks — new 
    contact_replied
    event • Channel-agnostic status signal — fires whenever a contact's status changes to "Replied", regardless of how (email, LinkedIn, SMS, or manual/API mark). `reason`: 
    EmailDetected
    / 
    LinkedInDetected
    / 
    SmsDetected
    / 
    StatusSetManually
    . • Payload: 
    reply_date
    , 
    reply_message_id
    , 
    reason
    , 
    contact_fields
    , 
    contact_custom_fields
    , 
    sequence_fields
    . Correlate to per-channel webhooks via 
    reply_message_id
    . Webhooks — richer 
    sequence_fields
    • Now consistently carries 
    id
    + 
    name
    + 
    step_number
    across sequence events (was 
    id
    -only or `id`+`step_number` on some). • 
    linkedin_reply_categorized
    now carries 
    sequence_fields
    + opt-in 
    linkedin_message
    (needs 
    includeLinkedInMessageText
    ). Auth — stable error codes for Organization API keys • Rejected impersonation → 
    application/problem+json
    with a `code`: 
    403 USER_REQUIRED
    , 
    401 USER_NOT_FOUND
    , 
    403 TEAM_NOT_ACCESSIBLE
    . Breaking Changes 
    email_replied
    — 
    reason
    removed; scope narrowed Before: fired only on the first detected reply or when contact status was set to "Replied"; payload had 
    reason
    (`EmailDetected`/`StatusSetManually`). After: no `reason`; fires on every detected email reply — and only on detected replies. Manual "Replied" marks now flow through 
    contact_replied
    . Action: stop reading `reason`; expect multiple events per contact; to catch manual marks subscribe to 
    contact_replied
    (
    reason: StatusSetManually
    ). Note: these webhook changes apply to v3 webhooks only — v2 behavior is unchanged. 📚 Full docs: docs.reply.io/api-reference
    🎯 1