Add people to a watchlist

Add people to a Job Change Watchlist without recreating the signal — grow the list as you win new champions, or swap it wholesale when your CRM segment changes.

Input: signalId (path), profiles (1 to 10,000 entries), and mode: append (default — adds these and leaves everyone else in place) or replace (makes this the whole list; anyone not in it stops being watched, with their history kept).

Each entry in profiles is either a LinkedIn profile URL on its own, or an object {url, currentTitle, currentCompany, currentCompanyUrl} carrying the role you already have on file. Both forms can be mixed in one call. Country subdomains and tracking query strings are accepted and normalized.

Send the role you have. Every check is billed, the first one included. With a role on file, the first check compares against it and reports any change straight away. With a bare URL, the first check can only report a move made in the last 6 months (it compares the current job with the one before it); anyone who moved earlier stays invisible, recorded as they stand today, and a later move is reported at the next check, one cadenceHours later. Either field helps on its own — currentCompany catches an employer change, currentTitle catches a promotion.

One watchlist holds at most 40,000 people. That is a limit on the list, not on the request: send a larger list as successive append calls of up to 10,000, and the call that would take the list past 40,000 is rejected with 400.

Output: added (now watched, were not before), alreadyWatched (already on the list, unchanged), rejected (not a usable personal profile URL), stoppedWatching (dropped by a replace; always 0 on append), and totalWatched (the size of the list after this call).

A bad URL never fails the request — it is counted in rejected so one typo in a 500-person list does not reject the other 499. Check rejected against what you sent. Re-adding someone previously removed resumes their history rather than reporting their current role as a fresh change.