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
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
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.Base URL
All LinkedIn API requests should be made to:Authentication
Include your API key in thex-api-key header of every request:
Available Endpoints
Fetch Profile
Retrieve full profile data for any LinkedIn user by their profile slug
Fetch Posts
Get recent posts from one or more LinkedIn profiles by URN
Like Post
Programmatically like any LinkedIn post via its activity URN
Comment on Post
Post comments on LinkedIn content via its activity URN
Get Task Status
Poll for async task results by task ID
Coming Soon
Company data, search, connection requests, messaging, and more
Endpoint Categories
Data Retrieval
- Fetch Profile -
POST /linkedin-agent/fetch-profile- Get profile data by slug - Fetch Posts -
POST /linkedin-agent/fetch-profiles-posts- Get posts by profile URNs
Engagement Automation
- Like Post -
POST /linkedin-agent/like-post- Like a post by activity URN - Comment on Post -
POST /linkedin-agent/comment-post- Comment on a post by activity URN
Task Management
- Get Task Status -
GET /linkedin-agent/get-task-status- Check task status and retrieve results
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?
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?
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?
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?
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?
Get Your API Key
Visit mentions.outx.ai/api-doc and click “Reveal API Key”
Follow the Quick Start
Fetch your first LinkedIn profile in under 2 minutes with our Quick Start guide
Have questions? Contact us at support@outx.ai 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?
How is the LinkedIn API different from the Social Listening API?
Is the LinkedIn API a replacement for Proxycurl?
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?
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.

