Competitor Monitoring
List Competitor Team Refreshes
What each monthly team refresh found at a competitor
GET
Every month, before collecting a competitor’s activity, Clustr searches its Sales and CS team
again for newcomers, then checks the LinkedIn profile of every monitored and paused person on
the Team, whether or not the search still finds them:
- Joiners: people the search found who were not on the Team. They are added as to validate and take no slot until someone monitors them.
- Leavers: people whose LinkedIn profile now shows another employer. They are marked Left the company with their new company, their slot is freed, and their past activity stays.
- Role changes: people still at the competitor whose current title is no longer a Sales or CS title. They stay monitored and are flagged so you can keep or remove them.
unconfirmed and checked again three days later, up to
three times a month. People a refresh did not reach before its time ran out, or could not check
because its search failed, are counted in deferred and checked within the hour. Those follow-up
checks are listed here too, with origin: "recheck"; they search nothing, so they have no
joiners. profiles_checked is how many profiles each pass read.
Each entry lists the three counts and the names behind them, newest first. A refresh runs at the
start of the scheduled collection it rides on, once a month (origin: "run") or when you
run one now (origin: "manual"). A refresh whose
search failed has status: "failed" and an error code: SEARCH_FAILED, SEARCH_EMPTY (the
search found nobody), SEARCH_DEGRADED or ABANDONED. Its profile checks still happen, in the
recheck.
Authorizations
The API key you created on the API settings page of the Clustr app.
Path Parameters
The competitor's Clustr ID (cmp_…), from List Competitors.
The id from earlier responses also works.
Query Parameters
The maximum number of refreshes to return, from 1 to 100. Defaults to 12.
Required range:
1 <= x <= 100