LinkedIn Data - Fetch Profiles, Posts, and Automate Engagement

Fetch LinkedIn profiles, retrieve posts, like and comment on content via the OutX API. A Proxycurl alternative powered by real browser sessions.

The OutX LinkedIn API is a middleware layer that lets you interact with LinkedIn data and automate engagement through a simple REST API. Unlike traditional scraping tools, OutX uses real browser sessions via the OutX Chrome extension, giving you reliable, authentic access to LinkedIn data without the risk of account bans.

How It Works

OutX is not a scraper. Instead of simulating HTTP requests or using headless browsers, it routes API calls through real LinkedIn sessions maintained by the OutX Chrome extension installed on your team members’ browsers. This means:

• No proxy rotation or CAPTCHA solving required
• No risk of IP bans since requests go through authentic browser sessions
• Real-time data from LinkedIn, not cached or stale datasets
• Full compliance with browser-level session handling

At least one team member must have the OutX Chrome extension installed and active within the last 48 hours for API calls to work. See Authentication for details.

Why OutX vs. Alternatives

Feature	OutX	Proxycurl	PhantomBuster	Unipile
Real browser sessions	Yes	No	No	No
No proxy needed	Yes	No	No	No
Profile data	Yes	Yes	Yes	Yes
Post fetching	Yes	Limited	Yes	Yes
Like/Comment automation	Yes	No	Yes	Limited
Risk of LinkedIn bans	Minimal	Moderate	High	Moderate

Important: LinkedIn Safety

OutX does not rate-limit you, LinkedIn does. Every request executes as a real action on LinkedIn through the Chrome extension. OutX itself imposes no per-minute or per-hour cap, so if you burst, the underlying LinkedIn account is what gets flagged.

You are responsible for pacing. Stay under ~50 API calls per hour total across all endpoints, distribute calls throughout the day, and mix action types when you can. See Rate Limits for the per-endpoint daily caps and live usage dashboard.

Async Task Model

All LinkedIn API endpoints are asynchronous. When you make a request, the API immediately returns a task ID. The actual work is performed in the background by the Chrome extension. You then poll the task status endpoint to retrieve results.

1. POST /linkedin-agent/fetch-profile  -->  { api_agent_task_id: "abc-123" }
2. GET  /linkedin-agent/get-task-status?api_agent_task_id=abc-123  -->  { status: "pending" }
3. GET  /linkedin-agent/get-task-status?api_agent_task_id=abc-123  -->  { status: "completed", task_output: {...} }

This async model ensures reliability since the Chrome extension processes tasks on its own schedule, typically within seconds to a few minutes.

Base URL

All LinkedIn API requests should be made to:

https://api.outx.ai

Authentication

Include your API key in the x-api-key header of every request:

x-api-key: YOUR_API_KEY

Get your API key at mentions.outx.ai/api-doc.

Available Endpoints

Method	Endpoint	Description	Details
POST	/linkedin-agent/fetch-profile	Fetch a LinkedIn profile by slug	Open
POST	/linkedin-agent/fetch-profiles-posts	Fetch recent posts from one or more profile URNs	Open
POST	/linkedin-agent/fetch-company	Fetch a LinkedIn company page	Open
POST	/linkedin-agent/fetch-company-posts	Fetch recent posts from companies	Open
POST	/linkedin-agent/search-profiles	Search LinkedIn for profiles by filters	Open
POST	/linkedin-agent/fetch-connections	Fetch your 1st-degree connections	Open
POST	/linkedin-agent/like-post	Like a post by activity URN	Open
POST	/linkedin-agent/comment-post	Comment on a post by activity URN	Open
POST	/linkedin-agent/send-message	Send a direct message to a 1st-degree connection	Open
POST	/linkedin-agent/send-connection-request	Send a connection request	Open
GET	/linkedin-agent/get-task-status	Poll the status of an async task	Open

For upcoming endpoints (jobs, etc.), see Coming Soon.

Looking for Watchlist Endpoints?

For ongoing monitoring with watchlists, see the Watchlists & Engagement section. Watchlists automatically scan LinkedIn for keywords, people, and companies over time with AI-powered categorization.

What is the difference between LinkedIn Data and Watchlist endpoints?

LinkedIn Data (this section) provides direct access to LinkedIn actions: fetch a profile, get posts, like, comment. Each call is a one-off async task.

Watchlists & Engagement provides higher-level features: create watchlists that automatically monitor keywords, people, or companies over time, with built-in post retrieval and filtering.

Use LinkedIn Data when you need direct control. Use Watchlists when you want ongoing, automated monitoring.

Do I need the Chrome extension?

Yes. The OutX API works by routing requests through real browser sessions maintained by the Chrome extension. At least one team member must have the extension installed and active within the last 48 hours. See Authentication for details.

Is OutX a Proxycurl alternative?

Yes. OutX provides similar LinkedIn data fetching capabilities to Proxycurl but with key differences: OutX uses real browser sessions instead of scraping, which provides more reliable data access and lower risk of LinkedIn restrictions. OutX also offers engagement automation (likes, comments) which Proxycurl does not.

How long do async tasks take to complete?

Most tasks complete within seconds to a few minutes, depending on when the Chrome extension picks up the task. The extension checks for new tasks on a regular cron schedule. You can poll the Get Task Status endpoint to check progress.

What’s Next?

1. Get Your API Key

   Visit mentions.outx.ai/api-doc and click “Reveal API Key”

2. Install the Chrome Extension

   Install the OutX Chrome extension and keep it active

3. Follow the Quick Start

   Fetch your first LinkedIn profile in under 2 minutes with our Quick Start guide

4. Explore Endpoints

   Dive into the individual endpoint docs for full details

Have questions? Contact us at [e-mail] or visit outx.ai.

---

Learn More

• LinkedIn API Guide - OutX Blog
• Proxycurl Alternative - Why Developers Choose OutX
• LinkedIn Social Listening Platform

Frequently Asked Questions

How is the LinkedIn API different from the Social Listening API?

The LinkedIn API is for direct, on-demand calls - you fetch a profile, retrieve posts, or perform an engagement action as a one-off task. The Social Listening API (Intelligence API) creates watchlists for ongoing monitoring with AI-powered categorization and intent detection. Use the LinkedIn API for programmatic access; use the Social Listening API for continuous tracking.

Is the LinkedIn API a replacement for Proxycurl?

OutX offers similar profile fetching capabilities to Proxycurl. The key difference is that OutX uses real browser sessions via the Chrome extension rather than scraping, which provides more reliable data access and lower risk of LinkedIn restrictions. OutX also supports engagement automation (likes, comments), which Proxycurl does not offer.

What happens if my Chrome extension is not active?

API calls will return a 403 error with a “Plugin installation required” message. At least one team member must have the OutX Chrome extension installed and active within the last 48 hours for API calls to work.