> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadterra.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Leadterra: Agent-Ready Sending APIs for GTM Workflows

> Leadterra is a private outbound email API for GTM teams and AI agents. Create campaigns, enroll leads, and route classified replies programmatically.

Leadterra is private outbound email infrastructure designed for GTM teams and the AI agents that power them. Instead of clicking through a dashboard, you drive every part of the outbound process — campaign creation, lead enrollment, send scheduling, and reply handling — through a clean REST API that works equally well from a curl command, a Python script, or an agent runtime like Deepline, Claude Code, or Codex.

## What you can build

<CardGroup cols={2}>
  <Card title="Campaign Automation" icon="paper-plane">
    Create draft campaigns with multi-step sequences, enroll leads in bulk, and launch or pause sends programmatically — no manual intervention required.
  </Card>

  <Card title="Private Sender Pools" icon="shield">
    Route sends through private delivery pools that expose capacity and sending identities without revealing the underlying infrastructure.
  </Card>

  <Card title="Reply Intelligence" icon="messages">
    Pull classified replies and thread activity back into your agent workflows so your automations can act on positive responses in real time.
  </Card>

  <Card title="Webhook Automation" icon="bolt">
    Register webhooks to receive `campaign.started`, `message.sent`, `message.bounced`, and `reply.received` events as they happen.
  </Card>
</CardGroup>

## How it works

Every Leadterra workflow follows the same four-stage path. First, your workspace is provisioned with one or more **sender pools** — private groups of sending identities with defined daily capacity. You inspect those pools to understand how much volume you can safely push before you create anything.

Next, you **create a campaign** as a draft. A campaign holds your sequence steps (subject lines, HTML bodies, and merge tags like `{{firstName}}`), and it stays in draft state until you explicitly start it. That gives you time to review configuration and enroll the right leads.

Once the campaign looks right, you **enroll leads** via the bulk endpoint. Leadterra upserts each lead record and links it to the campaign. When you're ready, you call the start endpoint and Leadterra begins queueing the first sequence step across your sender pool.

Throughout the campaign, **replies** flow back in and are automatically classified. You can pull those replies via the API or receive them in real time through webhooks, letting your agents respond, route, or escalate without polling.

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Follow the step-by-step guide to send your first campaign in minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Learn how to generate your API key and authenticate every request.
  </Card>

  <Card title="Concepts" icon="lightbulb" href="/concepts/sender-pools">
    Dive deeper into sender pools, campaigns, leads, and reply intelligence.
  </Card>
</CardGroup>