Delete Connector

DELETE

network

connectors

{linkedinId}

curl -X DELETE "https://api.clustr-ai.com/api/public/network/connectors/per_022d7w7fahrkk591vrb6bg39dx" \
  -H "Authorization: Bearer YOUR_API_KEY"

import requests

for linkedin_id in ["yvesbrunschwiler", "danielbrooker1", "philipnyborg"]:
    r = requests.delete(
        f"https://api.clustr-ai.com/api/public/network/connectors/{linkedin_id}",
        headers={"Authorization": "Bearer YOUR_API_KEY"},
    )
    print(linkedin_id, r.status_code, r.json())

await fetch("https://api.clustr-ai.com/api/public/network/connectors/per_022d7w7fahrkk591vrb6bg39dx", {
  method: "DELETE",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "clustr_connector_person_id": "per_022d7w7fahrkk591vrb6bg39dx",
    "connector_linkedin_id": "yvesbrunschwiler",
    "removed": true,
    "deleted_opportunities": 412
  }
}

{
  "success": false,
  "error": {
    "message": "No connector found with linkedin id: yvesbrunschwiler not found",
    "code": "NOT_FOUND"
  }
}

{
  "success": false,
  "error": { "message": "Invalid or missing API key", "code": "UNAUTHORIZED" }
}

Remove a connector from your network. Every opportunity that came through them is deleted, along with the engagements and overlaps behind those opportunities. This is the endpoint for someone who has left. Their intros are no longer actionable, and while they stay in the network they count toward your connector total, your opportunity total, and every owner and account roll-up that reads either.

Irreversible. The deletion is permanent. The only way back is importing the connector again, which spends credits and rediscovers the opportunities from scratch.Unassign Connector Owner is a different action: it clears who is accountable and keeps everything else. If what you want is to stop attributing someone’s book to them, use DELETE /network/connectors/{linkedinId}/owner instead.

What is deleted

Deleted	Kept
Every opportunity where this person is the connector	The prospects themselves, and any opportunity reaching them through a different connector
The engagements and overlaps those opportunities were built from	Your owners, tags and target accounts
The connector’s network membership, owner rule and tag assignments	Profile data, which is not workspace-scoped

Opportunities where the person is the prospect rather than the connector stay: this removes them as a route into other companies, while other connectors can still reach them.

Removing several people

Each call deletes one connector. Call this once per connector; the deletes are independent, so they can run concurrently. List the network first and confirm each linkedin_id, since a wrong id here deletes somebody else’s whole book.

curl -X DELETE "https://api.clustr-ai.com/api/public/network/connectors/per_022d7w7fahrkk591vrb6bg39dx" \
  -H "Authorization: Bearer YOUR_API_KEY"

import requests

for linkedin_id in ["yvesbrunschwiler", "danielbrooker1", "philipnyborg"]:
    r = requests.delete(
        f"https://api.clustr-ai.com/api/public/network/connectors/{linkedin_id}",
        headers={"Authorization": "Bearer YOUR_API_KEY"},
    )
    print(linkedin_id, r.status_code, r.json())

await fetch("https://api.clustr-ai.com/api/public/network/connectors/per_022d7w7fahrkk591vrb6bg39dx", {
  method: "DELETE",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "clustr_connector_person_id": "per_022d7w7fahrkk591vrb6bg39dx",
    "connector_linkedin_id": "yvesbrunschwiler",
    "removed": true,
    "deleted_opportunities": 412
  }
}

{
  "success": false,
  "error": {
    "message": "No connector found with linkedin id: yvesbrunschwiler not found",
    "code": "NOT_FOUND"
  }
}

{
  "success": false,
  "error": { "message": "Invalid or missing API key", "code": "UNAUTHORIZED" }
}

Authorizations

Authorization

string

header

required

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

Path Parameters

linkedinId

string

required

The connector's Clustr ID (per_…), from List Connectors. Their LinkedIn public identifier, the linkedin_id that list returns, also works: for https://www.linkedin.com/in/nicdelaye that is nicdelaye.

Response

Connector removed

success

boolean

required

data

object

required

Show child attributes

curl -X DELETE "https://api.clustr-ai.com/api/public/network/connectors/per_022d7w7fahrkk591vrb6bg39dx" \
  -H "Authorization: Bearer YOUR_API_KEY"

import requests

for linkedin_id in ["yvesbrunschwiler", "danielbrooker1", "philipnyborg"]:
    r = requests.delete(
        f"https://api.clustr-ai.com/api/public/network/connectors/{linkedin_id}",
        headers={"Authorization": "Bearer YOUR_API_KEY"},
    )
    print(linkedin_id, r.status_code, r.json())

await fetch("https://api.clustr-ai.com/api/public/network/connectors/per_022d7w7fahrkk591vrb6bg39dx", {
  method: "DELETE",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "clustr_connector_person_id": "per_022d7w7fahrkk591vrb6bg39dx",
    "connector_linkedin_id": "yvesbrunschwiler",
    "removed": true,
    "deleted_opportunities": 412
  }
}

{
  "success": false,
  "error": {
    "message": "No connector found with linkedin id: yvesbrunschwiler not found",
    "code": "NOT_FOUND"
  }
}

{
  "success": false,
  "error": { "message": "Invalid or missing API key", "code": "UNAUTHORIZED" }
}

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

Delete Connector

What is deleted

Removing several people

Authorizations

Path Parameters

Response

​What is deleted

​Removing several people

Authorizations

Path Parameters

Response

What is deleted

Removing several people