Public API · v1

Build on LeadRails.

The LeadRails REST API lets you manage sources, destinations, routes, and events from code. The MCP server lets your AI agent do the same. Everything authenticated with a single API key. Everything documented here.

Start the quickstart Browse the reference

Need an account first? Sign up free — 1,000 leads / month, no card required.

Five minutes

Quickstart

Create an API key, send your first signed event, and confirm delivery — start to finish.

API Reference

Live OpenAPI 3.1 spec rendered with Scalar. Every endpoint, every field, with try-it-now examples.

MCP server

Install @leadrails/mcp in Claude Desktop, Claude Code, or Cursor. Your agent talks to LeadRails over stdio.

Error types

Every error the API emits, with the type URL, status code, and the fix.

What you can build.

The v1 API is everything you need to put LeadRails inside another product.

Provisioning

Create sources, destinations, and routes for a new customer in one script. Hand them a working integration the first time they log in.

Monitoring

Poll /v1/events for delivery status. Build a status dashboard, fire a Slack alert on failures, or replay a dropped event.

AI agents

Drop the MCP server into Claude Desktop. Ask "pause the source I created yesterday." Your agent does it.

Stability.

The v1 surface is committed. Field additions are non-breaking. Breaking changes ship under a new prefix (/v2) with at least 12 months of overlap. The error type URLs at https://docs.leadrails.dev/errors/… are stable identifiers — pin against them in your client code, not against the human-readable title.