Skip to main content
New to the platform? How OutX works covers the pipeline, the update flow, and the extension dependency in one page. A watchlist is a saved monitoring job that continuously collects posts. Each watchlist tracks exactly one platform and one tracking mode, and each type has its own endpoint. There is no generic “create watchlist” call and no single call that spans two platforms. One watchlist also carries one signal for one audience. Competitor mentions, buying intent and your own brand mentions are three watchlists, not one prompt, because the relevance objective and the default labels are shared by everything in a watchlist. Design your watchlists covers the layout, and GET /api-watchlists lists what you already have before you add more.

​
The four types

All four types share one CRUD pattern (POST create, GET read, PUT update, DELETE delete on the same URL) and all four count toward the same plan watchlist limit (a 402 error names your limit; check remaining quota first with GET /api-team). Posts collected by any watchlist type are read from the same endpoint: GET /api-posts?watchlist_id=.... The response shape adapts automatically to the watchlist’s platform.

​
Task-to-endpoint map

“LinkedIn and Reddit” means two watchlists. A request like “monitor AI CRM tools on LinkedIn and Reddit” is two API calls: one POST /api-keyword-watchlist and one POST /api-reddit-watchlist. They return different watchlist IDs, run on independent fetch cycles, and their feeds are read separately.

​
Recipe: one topic on LinkedIn and Reddit

Send the same prompt to both endpoints. OutX generates platform-appropriate keywords and intent labels for each in the background.
Each call returns 201 with its own id. Save both. To read the feeds:
There is no cross-watchlist feed endpoint; merge the two result sets client-side if you need a combined view.

​
Differences that matter to an agent

  • Keyword and Reddit watchlists are twins. Same body shape on create and update (keywords, prompt, labels, fetchFreqInHours, slack_webhook_url, append), same intent label system. The platform, the endpoint, the default fetch frequency (12h vs 24h) and the backfill differ: a keyword watchlist backfills recent posts on create and on every keyword or prompt change, and a Reddit watchlist never backfills at all.
  • People and company watchlists have no Reddit equivalent and no keywords, prompts, or intent labels. They track a named set of profiles or company pages, edited with add_profiles / remove_profiles (or the company equivalents) on PUT. They hold up to 200 members each, under a team-wide allowance. They do take fetchFreqInHours on create and update, the same as keyword and Reddit watchlists.
  • Collection runs through the OutX Chrome extension. For every watchlist type, at least one team member must have the extension installed and active (it must have checked in within the last 48 hours); otherwise API requests return 403 Plugin installation required.
  • Only the keyword (LinkedIn) type backfills on create. A new LinkedIn keyword watchlist backfills recent matching posts automatically, so it is usually non-empty within minutes. Reddit, people, and company watchlists start filling on their first fetch cycle.

​
Next steps

Design your watchlists

How many to create and what goes in each one

List all watchlists

Every watchlist of every type in one call

Create Keyword Watchlist

LinkedIn keyword tracking, prompt or direct mode

Create Reddit Watchlist

The Reddit twin of the keyword watchlist

Intent Labels Explained

How posts get classified and what default labels do

Get Posts

Read and filter any watchlist’s feed