Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Reply.io (BYOK) — connector documentation

  • MCP endpoint: https://byok-replyio.connectorbay.com/mcp
  • REST API: POST https://byok-replyio.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-replyio.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Reply.io Reply API key (needs read scopes such as contacts:read and sequences:read), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-replyio.connectorbay.com/health · Tool schemas: https://byok-replyio.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-replyio · agent@connectorbay.com

What Reply.io (BYOK) is for

Reply.io (BYOK) lets an AI assistant read your own Reply.io data through the Reply.io API with a key you supply (Reply API key (needs read scopes such as contacts:read and sequences:read)). Read-only: 12 tools (whoami, list_team_users, list_sequences, get_sequence, list_sequence_contacts, list_contacts, list_contact_lists, list_contact_accounts, list_tasks, list_inbox_threads, list_email_accounts, list_sequence_folders). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.reply.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Reply.io. Reply.io and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Reply.io user is my API key for?"
  • "Who is on my Reply.io team?"
  • "Which Reply.io sequences are active?"
  • "Show Reply.io sequence 1234"
  • "Who is enrolled in Reply.io sequence 1234 and has replied?"
  • "Find the Reply.io contact jane@example.com"

What it does

  • whoami: Show the Reply user and team the key belongs to.
  • list_team_users: List the users of your Reply team with name, email and role.
  • list_sequences: List Reply sequences with owner, status (new, active, paused), health and creation time. Filter by status, name, owner or folder.
  • get_sequence: Get one Reply sequence: status, health, schedule, connected email accounts and sending settings.
  • list_sequence_contacts: List the contacts enrolled in a Reply sequence with their status in the sequence, reply and bounce flags and current step.
  • list_contacts: List Reply contacts, or look one up by exact email or LinkedIn URL, with company, title, location and stage.
  • list_contact_lists: List Reply contact lists with name and sharing flag.
  • list_contact_accounts: List Reply accounts (companies) with domain, industry, size, country, stage and activity dates.
  • list_tasks: List Reply tasks (to-dos, calls, meetings, LinkedIn and manual email steps) with type, status, assignee and due date.
  • list_inbox_threads: List Reply inbox threads with subject, preview, contact, sequence, category and last activity.
  • list_email_accounts: List the email accounts connected to Reply with sender name, type, daily limit and connection status. No passwords are returned.
  • list_sequence_folders: List Reply sequence folders (id and name).

BYOK key

You bring your own Reply.io Reply API key (needs read scopes such as contacts:read and sequences:read) (https://docs.reply.io/api-reference/introduction). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.reply.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Reply.io API (api.reply.io) with a BYOK key; documentation: https://docs.reply.io/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Reply.io. Reply.io and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Reply.io account.

Built for: Worldwide. Languages: English.