Skip to main content
Use Lemlist through Corsair: one client, typed API calls. Lemlist uses HTTP Basic authentication. Provide your Lemlist API key from your team settings (Settings -> Integrations -> API). The API key is passed as the password with an empty username (Authorization: Basic base64(:apiKey)). Things to know before calling:
  • Identifiers: Campaign IDs and Lead IDs follow Lemlist’s internal identifier format (e.g., cam_..., lea_...).
  • Rate Limiting: Lemlist enforces API rate limits. The plugin automatically handles HTTP 429 responses and backs off according to the Retry-After header.
  • Campaign Lead Actions: leads.pause and leads.resume act on every campaign unless you pass campaignId. Interest changes have separate global (leads.markInterested) and campaign (leads.markInterestedInCampaign) operations. Step operations (leads.personalizeStep, leads.skipStep) always need a campaign.
  • Unsubscribes & Blacklist: Contacts can be unsubscribed or resubscribed either by variable (such as email or domain) or via the contact management endpoints.
What you get:
  • 60 typed API operations

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

List campaigns
Add a lead to an outreach campaign
See the full list on the API page.

What’s next

API reference

Every lemlist.api.* operation with input and output types.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.