Skip to main content
This guide will help you make your first API requests to OutX and get familiar with the core workflows.
This quick start creates a LinkedIn keyword watchlist. Reddit is a separate watchlist type with its own endpoint (/api-reddit-watchlist, same body shape); tracking a topic on “LinkedIn and Reddit” means two create calls. See Choose a watchlist type for the platform comparison.

Prerequisites

Before you begin, make sure you have:
1

API Key

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

Base URL

All requests go to: https://api.outx.ai

Your First Watchlist

Let’s create a keyword watchlist to track LinkedIn posts about AI and machine learning.

Step 1: Create a Keyword Watchlist

Response:
Save the id from the response - you’ll need it to retrieve posts from this watchlist!

Step 2: Retrieve Posts from Your Watchlist

Now let’s fetch posts from the watchlist we just created:
Response (abridged, see Get posts for the full post shape):
A brand-new watchlist backfills recent matching posts in the background, and each post’s tags (intent labels) are written asynchronously during enrichment. Empty data or empty tags right after creation means “not processed yet”, not “no matches”. See Intent labels & defaults.

Step 3: Engage with a Post

Let’s like one of the posts we retrieved:
Response:

Advanced Filtering Examples

Filter by Date Range

Use start_date and end_date params in YYYY-MM-DD format:
Dates should be in YYYY-MM-DD format (e.g., 2026-02-15). End dates are inclusive - end_date=2026-02-28 includes the full day of Feb 28.

Filter by Seniority Level

Filter posts by the author’s seniority. You can pass multiple values as comma-separated:

Pagination

Use page (1-indexed) and page_size (default 20). The response’s count field is the total number of matching posts, so pages run out when page * page_size >= count:
The parameter names are page and page_size on every paginated endpoint; aliases like limit, offset, per_page, or pageSize are rejected with a 400. (An offset-based alternative, range_from/range_to, also exists on /api-posts; see Get posts.)

Sort by Engagement

Sort options: recent (default), popular_first (by engagement), engagement (alias for popular_first).

Common Workflows

Create a people watchlist to monitor posts from key industry leaders:
Track posts from competitor company pages:
Retrieve trending posts with high engagement:
Like posts on behalf of your company page:

Next Steps

Choose a Watchlist Type

LinkedIn vs Reddit, and which endpoint creates what

Posts API

Explore all post filtering options

Intent Labels

How posts get classified and what default labels do

Like API

Automate post likes

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_KEY environment variable
  • OutX Chrome extension installed and active on at least one team member’s browser

Quick Reference

Guardrails, ALWAYS DO

  1. Use x-api-key header for authentication
  2. Use base URL https://api.outx.ai
  3. Use ISO 8601 dates (YYYY-MM-DD) for start_date and end_date
  4. Use post_id from the /api-posts response when calling /api-like or /api-comment
  5. Handle 429 rate limit errors with exponential backoff

Guardrails, NEVER DO

  1. Never hardcode API keys in source code
  2. Never use fetchFreqInHours values other than 1, 3, 6, 12, 24, 48, 72
  3. Never call /api-like or /api-comment without a valid post_id and user_email
  4. Never assume posts appear instantly, new watchlists populate on the next fetch cycle
  5. Never expect one call to cover two platforms: “LinkedIn and Reddit” is one POST to /api-keyword-watchlist plus one POST to /api-reddit-watchlist
  6. Never invent pagination params: use page and page_size (limit, offset, per_page, and pageSize are rejected with a 400)
For the full OutX API skill file, see outx-skill.md.

Frequently Asked Questions

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.
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.
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.

Learn More