Build LinkedIn automation into your product

The We-Link API lets you run connection requests, messaging, and search from your own code, or from Claude, ChatGPT, and Cursor with the live MCP server.

Build with us diagram connecting the We-Link API, We-Link MCP, and We-Connect API

Tell your assistant what you want on LinkedIn

The We-Link API powers connection requests, messaging, and search. With the live MCP server, the same actions run from Claude, ChatGPT, or Cursor.

You
input

“Find 20 VPs of Sales at SaaS companies in Boston and send each a connection request with a short note.”

We-Link runs
01Search profiles
02Get profile data
03Send connection request

Three ways to build

Start with the full automation API, drive it from an AI assistant, or sync your campaign data.

We-Link API

Automation API

A full LinkedIn automation API to embed connection requests, messaging, and search into your own software.

Over 70 REST endpoints: connections, messaging, search, posts, and outreach

Asynchronous by design, results delivered to your webhooks

Dedicated proxies, human-like pacing, and automatic rate-limit handling

apidocs.we-link.ai

Read the We-Link docs

We-Link MCP

Live · Beta

Run LinkedIn actions from Claude, ChatGPT, or Cursor in plain language.

Set up the MCP

We-Connect API

Data sync

Sync your We-Connect campaign data with your own stack.

Read the API docs
Coming soon

Build campaigns from your AI assistant

The We-Connect Lead Engine MCP lets your assistant build a full Lead Engine campaign in plain language.

See the preview

Which one do I use?

A few ways to build with us. Here is how to find yours.

Embedding LinkedIn actions into your product?

Use the We-Link API.

Want an assistant to run LinkedIn tasks?

Use the We-Link MCP server.

Syncing We-Connect campaign data?

Use the We-Connect API.

Not sure where to start?

and we will point you.

Why build with us

Real coverage, real safety, and a team that answers.

Safety is built in

Dedicated geo-matched proxies, human-like pacing, and automatic rate-limit handling keep accounts protected, whether the call comes from your code or an assistant.

Code or conversation

REST when you want to write it in, MCP when you want to just ask. The same actions, two ways to reach them.

A direct line to the team

Real developer support and a say in what ships next. You are not a ticket in a queue.

Frequently asked questions

What is the We-Link API?+
Is there a LinkedIn MCP server?+
Which AI assistants work with the MCP server?+
How is the We-Link API different from the We-Connect API?+
Is this an official LinkedIn integration?+
Is the We-Link API free?+
How does We-Link API pricing work?+
How does We-Link keep LinkedIn accounts safe?+
Does We-Link support Sales Navigator and Recruiter?+
How do I get started with the We-Link API?+

Ready to start building?

Get your key and make your first call in minutes.

Explore the APIs