Reply, programmatically
The outreach layer for agents, automations and products.
213 REST endpoints, 70 MCP tools, a CLI and packaged skills,
and the mailbox infrastructure underneath all of it.
Three doors. Pick yours.
Five ways in. Pick the one that fits.
What you get
213 endpoints, nine modules
Everything the dashboard does, callable
Contacts & Lists
Create, import, enrich, filter, and manage contacts and lists. Find missing emails and phone numbers. Sync contact data from any source in real time.
38
endpoints
Multichannel Sequences
Create sequences, manage steps and variants, assign email and LinkedIn accounts, add or remove contacts, and control the full campaign lifecycle.
59
endpoints
Unified Inbox
Access all replies, categorize threads, assign owners, send responses, and generate AI draft replies – without opening Reply.
17
endpoints
Email & LinkedIn Accounts
Connect Gmail and Office 365 via OAuth, manage IMAP/SMTP accounts, and control LinkedIn account settings – all programmatically.
30
endpoints
Reports & Analytics
Pull performance data across email, LinkedIn, calls, and tasks. Feed it directly into your dashboards – no CSV exports needed.
12
endpoints
Automation & Webhooks
Trigger workflows in real time with webhooks, manage background jobs, and control schedules and holiday calendars.
23
endpoints
Contact Enrichment
Enrich contacts by email or LinkedIn URL, find missing phone numbers, fill AI custom fields, and validate emails before sending – all automated.
7
endpoints
Email Templates
Create, manage, and render email templates from your own systems. Organize into shared folders and send test emails without touching the UI.
18
endpoints
Live Data Search
Search and discover prospects by department, industry, job title, location, and seniority – and pull results directly into your sequences via API.
9
endpoints
If it speaks MCP, it speaks Reply
A standard MCP server over JSON-RPC 2.0. Anything implementing the protocol can call it.
-
Claude Code
claude mcp add
-
Codex
MCP config
-
Cursor
JSON config
-
Claude Desktop
OAuth connector
-
ChatGPT
OAuth connector
-
Windsurf
MCP config
-
Cline
MCP config
-
n8n
HTTP / MCP node
-
Make
HTTP module
-
Zapier
REST
Top-rated on G2
10+
years running outbound
3000+
businesses
4.6/5
on G2, from 1,480 reviews
98%
email delivery rate
Documentation
Frequently Asked Questions
What’s the difference between the API, MCP, the CLI and Skills?
They’re four doors into one platform. The REST API is the exhaustive surface, all 213 endpoints. MCP is 70 curated tools for agents in clients like Claude and Cursor. The CLI is reply in your shell for scripts and CI. Skills are packaged multi-step workflows with confirmation gates. The table above compares them directly.
Do they share one account and one key?
Yes. One account, one API key, one object model and one rate-limit budget across all four. Switching between them needs no new credentials, which is why picking one isn’t an architectural commitment.
What features can be included in the white label solution?
The solution includes multichannel automation (emails, LinkedIn, calls, SMS, WhatsApp), AI SDR tools, and real-time global data access.
Which one should I start with?
If you want an agent to run outbound conversationally, start with MCP. If you’re scripting or working in CI, start with the CLI. If you’re building a product integration, start with the REST API, because webhooks, bulk imports and background jobs live there and nowhere else.
How many endpoints are there really?
213, across nine modules: contacts and lists, multichannel sequences, unified inbox, email and LinkedIn accounts, reports, automation and webhooks, contact enrichment, email templates, and live data search. The breakdown per module is on this page.
How many MCP tools, and what do they cover?
70, across seven domains: Jason AI SDR (31), sequences (16), contacts (8), workspace resolvers (5), help and meta (4), inbox (3) and tasks (3). 31 are annotated read-only and 39 destructive.
Do I need to write code?
Not necessarily. Reply’s API is standard REST, so Zapier, Make and n8n drive it without a custom integration, and any MCP-aware assistant drives it in natural language. Code is required only when you’re embedding Reply in something you ship.
How is access secured?
Scoped API keys on a domain:verb model with least-privilege defaults, over SOC 2 certified and GDPR compliant infrastructure. Credentials go in the Authorization header, and passing them in the URL isn’t supported.
What are the rate limits?
100 requests per minute and roughly 3,000 per hour, per user, shared across every surface. A 429 includes a Retry-After header with the exact wait.
Where’s the full reference?
docs.reply.io covers the API, MCP, CLI and Skills, including OpenAPI specs. The endpoint catalogue is on Reply’s API page, linked from the modules above.
Is all of this in the free trial?
Yes. Every surface is included. Get your key from Settings → API Key and start calling.