canonical: https://jentic.com/apis/lemlist.com/lemlist

# lemlist API

The lemlist API runs cold-outreach campaigns: it creates and manages campaigns and their sequences, adds and updates leads, marks leads as interested or not interested, and reads campaign reports and exports. It also manages schedules, message templates, snippets, and team membership. With 164 operations it covers the full sending workflow, authenticated with HTTP Basic using an API key, so an agent can build and drive multichannel outreach programmatically.

## For AI agents

Create and manage campaigns and sequences, add and update leads, mark lead interest, read reports and exports, and manage schedules and templates across 164 endpoints.

## Scope

Manages campaigns, sequences, leads, schedules, and templates that drive lemlist sending. Does not act as a general SMTP relay or handle billing.

## Capabilities

- Create, update, pause, and start campaigns
- Build and edit sequence steps and their branches
- Add, update, and remove leads on a campaign
- Mark leads interested or not interested and pause or review them
- Read campaign reports and start or fetch lead exports
- Manage schedules, message templates, snippets, and team members

## Use cases

### Lead sync into outreach

An AI agent adds and updates leads on a lemlist campaign as they arrive from a CRM or form, setting personalization variables so each contact enters the right sequence without manual CSV imports.

Example prompt: Add a lead with the given email and company to campaign CAMP123 and set the firstName variable

### Campaign control

An agent creates a campaign, starts it, and pauses it on demand, letting an operator run sending workflows conversationally instead of clicking through the lemlist dashboard.

Example prompt: Create a campaign named 'Q4 Outbound', then start it

### Reply triage

An agent marks leads as interested or not interested based on reply signals and reads campaign reports, keeping pipeline status current across active campaigns.

Example prompt: Mark the lead with email jane@acme.com as interested on campaign CAMP123 and return the campaign report

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/campaigns` | List campaigns on the account |
| POST | `/campaigns` | Create a campaign |
| POST | `/campaigns/{campaignId}/start` | Start a campaign so sending begins |
| POST | `/campaigns/{campaignId}/pause` | Pause a running campaign |
| POST | `/campaigns/{campaignId}/leads/` | Add a lead to a campaign |
| GET | `/campaigns/reports` | Read campaign reports |

## Key resources

- **Campaigns** — Create, start, pause, and report on outreach campaigns
- **Sequences** — Define and edit sequence steps and branches
- **Leads** — Add, update, and mark the interest state of contacts
- **Schedules** — Control when campaigns send
- **Templates and snippets** — Reusable message templates and snippets

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 32 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 47 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 30 / 100
  - Agent Usability: 60 / 100
  - Security: 10 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/lemlist.com/lemlist/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring lemlist by hand means holding an API key, sending it as HTTP Basic on every request, and paging through campaigns, leads, and sequences across 164 operations yourself. Through Jentic you install once, import the lemlist API from the Directory, store the key once, and your agent calls it.
- **Permission scoping:** Campaign, lead, and sequence ids are path parameters, so scope by operation and by resource: allow reading campaigns, leads, and reports while withholding start, pause, and delete operations, or restrict the agent to one campaign.
- **Credential handling:** Your lemlist API key credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent, such as 'add a lead to a campaign' or 'start an outreach campaign', and Jentic returns the matching lemlist API operation with its input schema so the agent calls the right endpoint without reading the reference docs by hand.

## Related APIs

- **Salesloft Platform API** — Sales engagement cadences and activity tracking
- **Outreach API** — Sales engagement sequences and prospect management
- **Instantly API** — Cold email campaigns and deliverability tooling
- **SendGrid Mail API** — Transactional and bulk email delivery

## FAQ

### What can an AI agent do with the lemlist API?

An agent can create and control campaigns, build sequences, add and update leads, mark lead interest, read reports and exports, and manage schedules and templates across the sending workflow.

### How do I connect the lemlist API to an AI agent with Jentic?

Import the lemlist API from the Jentic API Directory, store your API key once, and your agent calls the operations it needs. To get started, install the self-hosted Jentic One runtime from its GitHub repository and import the lemlist API from the Jentic API Directory.

### What authentication does the lemlist API use?

The lemlist API uses HTTP Basic authentication with your API key. Jentic One stores that key encrypted in your own instance and applies it at execution time.

### Can I limit what my agent is allowed to do with the lemlist API?

Yes. Campaign, lead, and sequence ids are path parameters, so you can scope the agent by operation and by resource: permit reading campaigns and reports while withholding start, pause, and lead-removal operations, or confine it to a single campaign.

### Does the lemlist API send email directly for me?

It manages campaigns, sequences, leads, and schedules that drive lemlist's own sending; it does not act as a raw SMTP relay for arbitrary messages outside a campaign.