Research people, discover prospects, publish content, and manage outreach on LinkedIn — all through the ABM.dev API.
Use with care — this drives your real LinkedIn account
These endpoints let agents act as you on LinkedIn — researching people, publishing posts, sending connection requests and messages — through your own connected profile. This is sensitive, carefully-engineered technology: the automation is built to behave like a real person, and ABM.dev paces every action behind conservative daily ceilings and human-like timing to protect your account. LinkedIn actively restricts automation, so treat agent-driven access deliberately — start slow, keep volumes well under the limits below, and never point it at an account you can’t afford to put at risk.
| Action | Daily limit (per account) |
|---|---|
| Profile lookups | 100 / day |
| Search requests | 50 / day |
| Connection requests | 25 / day |
| Messages sent | 50 / day |
Limits are per LinkedIn account and reset daily at midnight UTC. Exceeding a limit returns 429 with a Retry-After header — back off, don’t hammer.
How authentication works
GET /v2/linkedin/accounts to list your connected accounts and get their IDs.X-LinkedIn-Account: <id>.Choose which LinkedIn profile to act as
Endpoints below act as a specific account via the X-LinkedIn-Accountheader. With a single connected account it’s resolved automatically; pass the header to choose among multiple.
Learn about a person or company before reaching out
Find new people, companies, and signals
Search is one unified endpoint — POST /v2/linkedin/search with a type discriminator (people or companies). To discover posts, use GET /v2/linkedin/content.
Publish content, react, and join conversations
Social writes — post, react, comment, follow, unfollow — all go through one endpoint: POST /v2/linkedin/outreach with an action discriminator. To read your feed, use GET /v2/linkedin/outreach/conversations?view=feed; for a post’s comments and reactions, use GET /v2/linkedin/content?post_id=...&include=comments,reactions.
Connect, message, and manage relationships
Outreach writes — connect, message, accept or reject an invitation — go through POST /v2/linkedin/outreach with an action discriminator. Reads — conversations, invitations, connections, and the thread with one person — come from GET /v2/linkedin/outreach/conversations via the view query parameter.