LinkedIn API
The LinkedIn API for messages, invitations, profiles and posts.
Read profiles, inboxes, posts and search, and send messages, invitations, posts and comments from your users' own LinkedIn accounts. Unipile-compatible, paced like a person, with a dry run on every write.
- 7-day free trial
- No card needed
- Unipile-compatible
What you can do
Everything a person does on LinkedIn, through one API.
Profiles and companies
- A profile with its sections, or one looked up by URL
- Company pages and their employees
- The account's connections and followers
Inbox and messages
- Every conversation and message
- Start a chat, reply, send files and voice notes
- React to, edit and delete messages
Invitations
- Send invitations, with a note
- List sent and received ones
- Accept, decline or withdraw
Posts, comments and reactions
- A person's or a page's posts, each with its exact date
- Publish posts with mentions, images or a video
- Comment, reply and react
Search
- LinkedIn's classic search for people, posts and jobs
- Companies by keyword
- The ids its filters take
Webhooks
- New messages, reads and reactions within seconds
- New connections
- Account status changes
Why not LinkedIn's own API
The official API stops at sign-in and sharing.
LinkedIn opens only two products to every developer: Sign In with LinkedIn and Share on LinkedIn. Messages, invitations and other members' profiles aren't part of it. Lempile works through the accounts your users connect, so your product can do what they do on LinkedIn, at their pace.
Does LinkedIn have an API?curl -X POST "https://direct.lempile.com/api/v1/chats" \
-H "X-API-KEY: $LEMPILE_KEY" \
-H "Idempotency-Key: first-message-bob" \
-H "Content-Type: application/json" \
-d '{ "account_id": "'"$ACCOUNT_ID"'",
"attendees_ids": ["https://www.linkedin.com/in/bob-buyer"],
"text": "Hi Bob, quick question about your post." }'Built to keep accounts healthy
Each account keeps one session, one IP and one pace.
- Calls reuse the account's signed-in session: no new login per call.
- Every call leaves through that account's own proxy.
- One call at a time, 1.5 to 3 seconds apart, 1,500 a day at most.
- A 15-minute rest whenever LinkedIn asks the account to slow down.
?dry_run=trueon every write shows exactly what LinkedIn would receive.- An Idempotency-Key means a retry never sends twice.
FAQ
Questions, answered.
Is this LinkedIn's official API?
No. LinkedIn's official API opens only sign-in and sharing to every developer. Lempile works through accounts your users connect themselves, in their own session, which is how it offers messages, invitations, profiles and search.
Does it work with Unipile code?
Yes. Lempile answers Unipile's LinkedIn paths, fields, status codes and error types, so an integration moves by changing its base URL and key. Anything Lempile doesn't cover answers Unipile's own 501.
Does it support Sales Navigator or Recruiter?
Not yet. Lempile serves LinkedIn's classic features; Sales Navigator and Recruiter calls answer feature_not_subscribed.
Will LinkedIn restrict the accounts I connect?
No API can promise it never happens, and LinkedIn's User Agreement restricts automated access. Lempile keeps the risk low: each account keeps its own session and IP, calls are paced 1.5 to 3 seconds apart with at most 1,500 a day, and an account rests 15 minutes whenever LinkedIn asks it to slow down.
How much does it cost?
Per connected account: €49 a month for up to 10, then €5.00 down to €3.00 per account, with every endpoint and no per-call fees. 7-day free trial, no card needed.
Your first LinkedIn call in a minute.
Create a key, connect an account, call /users/me. 7-day free trial, no card needed.
Get your free API key