Prerequisites
Before you begin, make sure you have:API Key
Get your API key from mentions.outx.ai/api-doc
Your First Watchlist
Let’s create a keyword watchlist to track LinkedIn posts about AI and machine learning.Step 1: Create a Keyword Watchlist
Step 2: Retrieve Posts from Your Watchlist
Now let’s fetch posts from the watchlist we just created:Step 3: Engage with a Post
Let’s like one of the posts we retrieved:Advanced Filtering Examples
Filter by Date Range
Usestart_date and end_date params in YYYY-MM-DD format:
Filter by Seniority Level
Filter posts by the author’s seniority. You can pass multiple values as comma-separated:Pagination
Userange_from and range_to params (0-indexed). Default page size is 20:
Sort by Engagement
recent (default), popular_first (by engagement), engagement (alias for popular_first).
Common Workflows
Track Industry Influencers
Track Industry Influencers
Create a people watchlist to monitor posts from key industry leaders:
Monitor Competitor Companies
Monitor Competitor Companies
Track posts from competitor company pages:
Filter Posts by Engagement
Filter Posts by Engagement
Retrieve trending posts with high engagement:
Automate Company Engagement
Automate Company Engagement
Like posts on behalf of your company page:
Next Steps
Keyword Watchlist API
Learn about advanced keyword filtering
Posts API
Explore all post filtering options
Like API
Automate post likes
Comment API
Add comments programmatically
Need Help?
Have questions or need assistance? Contact us at support@outx.ai
AI Agent Prompt
Use the following instructions when building an AI agent that integrates with the OutX Watchlists & Engagement 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 |
|---|---|---|---|
| Create keyword watchlist | POST | /api-keyword-watchlist | keywords (required), name, fetchFreqInHours |
| Create people watchlist | POST | /api-people-watchlist | profiles (required), name |
| Create company watchlist | POST | /api-company-watchlist | companies (required), name |
| Retrieve posts | GET | /api-posts | watchlist_id, page, sort_by, start_date, end_date |
| Like a post | POST | /api-like | post_id (required), user_email (required) |
| Comment on a post | POST | /api-comment | post_id (required), user_email (required), comment_text (required) |
Guardrails — ALWAYS DO
- Use
x-api-keyheader for authentication - Use base URL
https://api.outx.ai - Use ISO 8601 dates (
YYYY-MM-DD) forstart_dateandend_date - Use
post_idfrom the/api-postsresponse when calling/api-likeor/api-comment - Handle 429 rate limit errors with exponential backoff
Guardrails — NEVER DO
- Never hardcode API keys in source code
- Never use
fetchFreqInHoursvalues other than 1, 3, 6, 12, 24, 48, 72 - Never call
/api-likeor/api-commentwithout a validpost_idanduser_email - Never assume posts appear instantly — new watchlists populate on the next fetch cycle
For the full OutX API skill file, see outx-skill.md.
Frequently Asked Questions
How long does it take for a new watchlist to start showing posts?
How long does it take for a new watchlist to start showing posts?
It depends on the fetch frequency you set (
fetchFreqInHours). After creating a watchlist, OutX begins scanning LinkedIn on the next fetch cycle. For example, if you set fetchFreqInHours to 6, you can expect the first results within 6 hours. You can set it as low as 1 hour for faster initial results.What date format should I use for start_date and end_date?
What date format should I use for start_date and end_date?
Use the
YYYY-MM-DD format (ISO 8601 date format). For example, 2026-02-15. End dates are inclusive — setting end_date=2026-02-28 includes all posts from the full day of February 28.Can I use the API without the Chrome extension?
Can I use the API without the Chrome extension?
No. The OutX Chrome extension is required for all API functionality. At least one team member must have the extension installed and active within the last 48 hours. OutX retrieves LinkedIn data through the browser extension rather than using unofficial scraping methods, so the extension is essential for the API to work.

