How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

lemlist Unsubscribes API

Suppression management - unsubscribe and re-subscribe contacts and variables, list and export the suppression set, and the legacy email/domain surface.

lemlist Unsubscribes API is one of 22 APIs that lemlist publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Unsubscribes and Compliance. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 19 operations across 10 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.lemlist.com/api.

19 operations 10 paths 3 schemas 4 DELETE10 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.lemlist.com/api
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

lemlist Unsubscribes API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

Paths & Operations 19

Across 10 paths, the API surfaces 19 operations — 4 DELETE, 10 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Unsubscribes 19
GET
/unsubscribes/
Retrieve Unsubscribes
3 params → 200
GET
/unsubs/export
Export Unsubscribes
1 param → 200
GET
/unsubscribes/john.doe@domain.com
Get Unsubscribe Email
1 param → 200404
POST
/unsubscribes/john.doe@domain.com
Add Unsubscribe Email/Domain
1 param → 200
DELETE
/unsubscribes/john.doe@domain.com
Delete Unsubscribe Email
1 param → 200
GET
/unsubscribesdeprecated
Get Many Unsubscribes
2 params → 200400401403404
GET
/v2/unsubscribes/variables
List Unsubscribed Variables
2 params → 200400401
POST
/v2/unsubscribes/variables
Bulk Unsubscribe Variables
body → 200400401
GET
/v2/unsubscribes/variables/{value}
Get Unsubscribed Variable
1 param → 200400401404
POST
/v2/unsubscribes/variables/{value}
Unsubscribe Variable
1 param → 200400401500
DELETE
/v2/unsubscribes/variables/{value}
Re-subscribe Variable
1 param → 200400401409
GET
/v2/unsubscribes/contacts/{contactId}
Get Contact Subscription Status
1 param → 200400401500
POST
/v2/unsubscribes/contacts/{contactId}
Unsubscribe Contact
1 param → 200400401500
DELETE
/v2/unsubscribes/contacts/{contactId}
Re-subscribe Contact
1 param → 200400401500
GET
/v2/unsubscribes/exports/variables
Export Unsubscribed Variables
→ 200400401
GET
/v2/unsubscribes/exports/contacts
Export Unsubscribed Contacts
→ 200400401
GET
/unsubscribes/{email}deprecated
Get Unsubscribe by Email
1 param → 200400401403404500
POST
/unsubscribes/{email}deprecated
Add Unsubscribe Email or Domain
1 param → 200400401404
DELETE
/unsubscribes/{email}deprecated
Delete Unsubscribe Email
1 param → 200400401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Unsubscribe (6 properties), UnsubscribedVariable (4 properties), ContactSubscriptionStatus (2 properties). Each schema is shown below with its type and property counts.

ContactSubscriptionStatus
object
Subscription status of a contact.
2 properties
Unsubscribe
object
A record of someone opting out of receiving emails.
6 properties
UnsubscribedVariable
object
A variable (email, domain, LinkedIn URL, or phone number) that has been unsubscribed.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lemlist-unsubscribes-api-openapi.yml Raw ↑

Other APIs lemlist publishes across the network.

lemlist MCP Server
lemlist Campaigns API
lemlist Sequences API
lemlist Leads API
lemlist People Database API
lemlist Enrich API
lemlist Inbox API
lemlist Contacts API
lemlist Companies API
lemlist Signal Agents API
lemlist Webhooks API
lemlist Schedules API
Where this information came from

This is an independent, third-party profile of lemlist Unsubscribes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.