Prerequisites
Before you begin, make sure you have:- An OutX account (sign up at outx.ai)
- The OutX Chrome extension installed and active
- Your API key from mentions.outx.ai/api-doc
End-to-End Walkthrough
Get Your API Key
- Log in to your OutX account
- Go to mentions.outx.ai/api-doc
- Click “Reveal API Key”
- Copy your API key
Install the Chrome Extension
Install the OutX Chrome extension and log in with your OutX account. The extension will automatically maintain a browser session that the API uses to execute tasks.
Fetch a LinkedIn Profile
Send a Response:
POST request to create a profile fetch task. You will receive an api_agent_task_id that you use to check for results.Poll for Results
The task is now queued. Poll the task status endpoint until the status changes from Pending response:
pending to completed.Complete Working Example
Here is a single, copy-paste-ready script that performs the entire flow:Next Steps
Fetch Profile
Full endpoint reference for profile fetching
Fetch Posts
Retrieve posts from LinkedIn profiles
Like Post
Automate liking LinkedIn posts
Comment on Post
Post comments programmatically
AI Agent Prompt
Use the following instructions when building an AI agent that integrates with the OutX LinkedIn Data API.Prerequisites
- API key stored in
OUTX_API_KEYenvironment variable - OutX Chrome extension installed and active on at least one team member’s browser
Quick Reference
| Action | Method | Endpoint | Key Params |
|---|---|---|---|
| Fetch profile | POST | /linkedin-agent/fetch-profile | profile_slug (required) |
| Fetch posts | POST | /linkedin-agent/fetch-profiles-posts | profile_urns (required, array) |
| Like post | POST | /linkedin-agent/like-post | social_urn (required) |
| Comment on post | POST | /linkedin-agent/comment-post | social_urn (required), comment_text (required) |
| Check task status | GET | /linkedin-agent/get-task-status | api_agent_task_id (required, query param) |
Async Pattern
All LinkedIn Data endpoints return{api_agent_task_id} immediately. You must poll get-task-status until status is "completed", then read task_output.
Guardrails — ALWAYS DO
- Use
x-api-keyheader for authentication - Use base URL
https://api.outx.ai - Poll
get-task-statusevery 5 seconds after submitting a task - Set a timeout (30 attempts / 2.5 minutes) to avoid polling indefinitely
- Check
statusfield:"pending"→"processing"→"completed"or"failed" - Space API calls at least 10–30 seconds apart — OutX is a proxy, not a rate limiter
- Distribute calls throughout the day — don’t batch everything in a short window
Guardrails — NEVER DO
- Never hardcode API keys in source code
- Never assume responses are synchronous — always poll for results
- Never send engagement actions without a valid
social_urn - Never skip error handling for 403 (Chrome extension not active)
- Never burst API calls — sending many requests in rapid succession risks LinkedIn flagging the account
For the full OutX API skill file, see outx-skill.md.
Frequently Asked Questions
How long does a profile fetch task take to complete?
How long does a profile fetch task take to complete?
Usually seconds to a few minutes, depending on when the Chrome extension picks up the task. The extension checks for new tasks on a regular schedule. Most tasks complete within 30 seconds under normal conditions.
How often should I poll for task status?
How often should I poll for task status?
Every 5 seconds is recommended. Set a timeout of 2-3 minutes to avoid polling indefinitely. The example code on this page uses 30 attempts with a 5-second delay, which provides a 2.5-minute window for task completion.

