🚀 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