Read threads
List active conversations for an account and read a thread's full history, so you always have context before replying.
Fetch threads →Read conversations and send messages on LinkedIn programmatically, over MCP or REST. List threads, pull full context, and reply, all sent at a human pace that stays inside LinkedIn's limits.
# Send a message to an existing thread (REST)
POST /api/v1/send_message_to_thread
x-api-key: your_api_key
x-api-secret: your_api_secret
{ "accountId": "...", "thread_id": "...", "message": "Thanks for connecting, ..." }A complete set of messaging actions, callable from your own backend over REST or from an AI assistant over MCP.
List active conversations for an account and read a thread's full history, so you always have context before replying.
Fetch threads →Send a message to a profile or straight into an existing thread. Personalize per recipient and keep conversations moving.
Send message →Reach beyond your connections with InMail, and message members of a LinkedIn group or event, subject to your account type.
InMail docs →Schedule follow-ups and track replies, so a conversation that goes quiet gets a nudge and one that replies stops the sequence.
Trackers →Every call returns a request ID and reports back over webhooks, so your app never blocks waiting on a send.
Webhooks →Messages go out at a human pace with automatic rate management, kept inside LinkedIn's limits on every account.
Safety →Point Claude, ChatGPT or any MCP client at We-Link and it can read and send messages in the flow of a conversation, no integration code.
Call the messaging endpoints from your own backend or a workflow tool like n8n, Make or Zapier. Asynchronous, with results over webhooks.
It is an API for reading LinkedIn conversations and sending messages programmatically. You can list threads, read a thread's history, and send messages to a profile or an existing thread, over MCP or REST.
Yes. You can fetch message threads for an account and read the full message history of any thread, so you always have the context before you reply.
Yes. Alongside standard messages, the API supports InMail and messaging members of a LinkedIn group or event, subject to your account type and LinkedIn's own limits.
Every message is sent at a human pace with automatic rate management, kept inside LinkedIn's limits, on infrastructure built to keep the account healthy.
Pricing is credit-based, not per seat. You pay for the API credits you use, with no per-seat or per-account fees, and a free trial of 100 API credits with no credit card required.
Start running LinkedIn messages. 100 API credits, 14 days, no credit card required.
The LinkedIn execution layer for AI agents
One API for agents to search, connect, message and engage on LinkedIn, over MCP or REST, always at a safe pace.