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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
lemlist

lemlist Inbox API

The unified reply inbox - conversations, messages, drafts, labels and sending on email, LinkedIn and WhatsApp.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Inbox and Multichannel Messaging. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 15 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.

15 operations 10 paths 3 schemas 2 DELETE6 GET1 PATCH6 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 Inbox API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

Paths & Operations 15

Across 10 paths, the API surfaces 15 operations — 2 DELETE, 6 GET, 1 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Inbox 15
GET
/inbox
Retrieve inbox list
3 params body → 200
GET
/inbox/{contactId}
Contact messages
6 params → 200
POST
/inbox/email
Send email
1 param body → 200
POST
/inbox/linkedin
Send LinkedIn message
1 param body → 200
POST
/inbox/whatsapp
Send WhatsApp message
1 param body → 200
GET
/inbox/labels
Get Many Labels
→ 200400401
POST
/inbox/labels
Create Label
body → 200400401409405
GET
/inbox/labels/{labelId}
Get Label
1 param → 200400401404405
POST
/inbox/conversations/labels/{contactId}
Attach Labels to Conversations
1 param body → 200400401404405
DELETE
/inbox/conversations/labels/{contactId}
Remove Labels from Conversation
1 param body → 200400401404405
GET
/inbox/{contactId}/drafts
List Drafts
2 params → 200400401405
POST
/inbox/{contactId}/drafts
Create Draft
2 params body → 201400401405
GET
/inbox/{contactId}/drafts/{draftId}
Get Draft
3 params → 200400401404405
PATCH
/inbox/{contactId}/drafts/{draftId}
Update Draft
3 params body → 200400401404405
DELETE
/inbox/{contactId}/drafts/{draftId}
Delete Draft
3 params → 200400401404405

Schemas 3

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

InboxMessage
object
A single message within an inbox conversation.
6 properties
InboxConversation
object
A message thread between a user and a contact in the inbox.
4 properties
Label
object
A label used to categorize and organize inbox conversations.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lemlist-inbox-api-openapi.yml Raw ↑

Other APIs lemlist publishes across the network.

lemlist MCP Server
AE Profile APIs.io
lemlist Campaigns API
AE Profile APIs.io
lemlist Sequences API
AE Profile APIs.io
lemlist Leads API
AE Profile APIs.io
lemlist People Database API
AE Profile APIs.io
lemlist Enrich API
AE Profile APIs.io
lemlist Contacts API
AE Profile APIs.io
lemlist Companies API
AE Profile APIs.io
lemlist Signal Agents API
AE Profile APIs.io
lemlist Webhooks API
AE Profile APIs.io
lemlist Unsubscribes API
AE Profile APIs.io
lemlist Schedules API
AE Profile APIs.io
#Inbox#Multichannel Messaging
← Back to L APIs
API Details
ID
lemlist:lemlist-inbox-api
Base URL
https://api.lemlist.com/api
Docs
https://developer.lemlist.com/api-reference
Provider
lemlist
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lemlist-inbox-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lemlist-inbox-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of lemlist Inbox 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.