Skip to main content
Change a company watchlist without losing its ID or the posts it has already collected: add companies, remove companies, rename it, or pause it.
Platform: LinkedIn only. Company watchlists track LinkedIn company pages; there is no Reddit equivalent. Collection requires your team’s OutX Chrome extension to be installed and active (within the last 48 hours). See Choose a watchlist type.

Request Body

string
required
Watchlist ID to update
array
Company pages to start tracking. Same identifier formats as create: LinkedIn company URL, company slug, full URN, or numeric URN id. An entry already on the watchlist is skipped rather than duplicated.
array
Company pages to stop tracking, in the same identifier formats. A company is matched on any identifier it is known by. Removing one deletes its collection tasks; posts already collected stay on the watchlist.
string
New watchlist name
boolean
Set to true to disable the watchlist, false to enable it. Pausing stops every collection task on the watchlist and flips disabled to true on the type’s GET endpoint, with disabledAt carrying the timestamp on the list response.
number
New fetch frequency. Allowed values: 1, 3, 6, 12, 24, 48, 72.
string | null
Update or clear the Slack webhook URL for this watchlist. Pass null to clear.
Send at least one of add_companies, remove_companies, name, fetchFreqInHours, disable or slack_webhook_url, otherwise the request is rejected with 400 No valid update fields provided.

Editing members

Removals are counted before the caps are checked, so swapping members in one call works even on a full watchlist. Nothing is written until both caps pass, so a request that would overflow changes nothing at all.

Limits

The team allowance is the real ceiling: free 400, growth 1,000, expert 4,000, ultimate 20,000, counting every profile and company on every watchlist you own. Spreading the same companies across more watchlists does not raise it, which is why the per-watchlist 400 quotes that budget instead of suggesting another list. The budget sentence is dropped for teams whose plan limits are waived, so the 400 can end at “Send fewer companies.”

Response Fields

string
Watchlist ID that was updated
string
Updated watchlist name
number
Updated fetch frequency (only present when fetchFreqInHours was in the request).
boolean
Current active/disabled status
number
Companies this call started tracking. 0 when add_companies was not sent.
number
Companies this call stopped tracking. 0 when remove_companies was not sent.
number
How many companies the watchlist holds after the change. This is the true total.
array
The raw input strings that changed nothing, exactly as you sent them: unparseable, repeated in the same request, already on the watchlist when adding, or absent from it when removing.
boolean
Whether the update was successful
string
Success message

Error Responses

Frequently Asked Questions

add_companies, remove_companies, name, fetchFreqInHours, disable and slack_webhook_url, in any combination. Everything except id is optional and omitted fields are left alone.
Read the current members with GET /api-company-watchlist?id=..., then send the ones you no longer want as remove_companies and the new ones as add_companies in a single call.
No. Renaming, pausing, adding or removing companies does not delete posts already collected. Removing a company stops future collection for that page; its existing posts stay readable through the Posts API.
It is the older way to add companies to an existing list, from before this endpoint could edit members. It still works. For adding and removing on a watchlist you already have, add_companies and remove_companies here are the path to use.