Run Competitor Team Refresh

POST

competitors

{id}

team-refresh

curl -X POST https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh \
  -H "Authorization: Bearer YOUR_API_KEY"

import requests

requests.post(
    "https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
)

await fetch("https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh", {
  method: "POST",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "started": true,
    "attached": false,
    "workflow_id": "competitor-team-refresh-c1a2b3c4-d5e6-7890-abcd-ef1234567890-2026110809"
  }
}

Runs the competitor’s team refresh now: the Sales and CS search runs again, joiners are followed automatically while you have free slots (past your limit they are added Paused, not followed), and every monitored and paused person is checked on LinkedIn to mark leavers and role changes. Clustr skips people it checked in the last week, so refreshing twice in a row costs once. Activity is collected by the next scheduled collection. The call answers 202 as soon as the refresh has started. Its result appears in List Competitor Team Refreshes, usually within a few minutes. A second call within the same hour joins the refresh already started (started: false, attached: true) instead of starting another one. The request has no body.

curl -X POST https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh \
  -H "Authorization: Bearer YOUR_API_KEY"

import requests

requests.post(
    "https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
)

await fetch("https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh", {
  method: "POST",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "started": true,
    "attached": false,
    "workflow_id": "competitor-team-refresh-c1a2b3c4-d5e6-7890-abcd-ef1234567890-2026110809"
  }
}

Authorizations

Authorization

string

header

required

The API key you created on the API settings page of the Clustr app.

Path Parameters

string

required

The competitor's Clustr ID (cmp_…), from List Competitors. The id from earlier responses also works.

Response

The refresh started, or was already started this hour

success

boolean

required

Example:

true

data

object

required

Show child attributes

curl -X POST https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh \
  -H "Authorization: Bearer YOUR_API_KEY"

import requests

requests.post(
    "https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
)

await fetch("https://api.clustr-ai.com/api/public/competitors/cmp_r0jpyyqyeh0txpgdhb604j2g9s/team-refresh", {
  method: "POST",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "started": true,
    "attached": false,
    "workflow_id": "competitor-team-refresh-c1a2b3c4-d5e6-7890-abcd-ef1234567890-2026110809"
  }
}

API Reference

Import

Search

Jobs

Network

Opportunities

Owners

Accounts

Account States

Saved Views

Workflows

Intro Requests

Notes

Record Activity

Tags

Target Accounts

Client Companies

Excluded Companies

Buyer Titles

ICP

Competitor Monitoring

Connector Refresh

Notifications

Run Competitor Team Refresh

Authorizations

Path Parameters

Response