Delete Connector

DELETE

network

connectors

{linkedinId}

curl -X DELETE "https://api.clustr-ai.com/api/public/network/connectors/yvesbrunschwiler" \
  -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/yvesbrunschwiler", {
  method: "DELETE",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "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. Nothing here is soft-deleted and there is no undo. The only way back is importing the connector again, which spends credits and rediscovers the opportunities from scratch.This is not Unassign Connector Owner. That clears who is accountable and deletes nothing. 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, statuses 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 are untouched: this removes them as a route into other companies, not as a person other connectors can reach.

Path Parameters

string

required

The connector’s LinkedIn public identifier, as returned in linkedin_id by List Connectors. For https://www.linkedin.com/in/yvesbrunschwiler that is yvesbrunschwiler.

Response Fields

string

The connector you removed.

boolean

Always true on a 200. An id that is not one of your connectors returns 404 rather than a 200 that removed nothing, so a typo cannot read as a successful delete.

integer

How many opportunities went with the connector. Check this against the opportunities_count List Connectors reported before the call.

Removing several people

There is no batch form. 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/yvesbrunschwiler" \
  -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/yvesbrunschwiler", {
  method: "DELETE",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "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" }
}

curl -X DELETE "https://api.clustr-ai.com/api/public/network/connectors/yvesbrunschwiler" \
  -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/yvesbrunschwiler", {
  method: "DELETE",
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});

{
  "success": true,
  "data": {
    "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

Target Accounts

ICP

Competitor Monitoring

Delete Connector

What is deleted

Path Parameters

Response Fields

Removing several people

​What is deleted

​Path Parameters

​Response Fields

​Removing several people

What is deleted

Path Parameters

Response Fields

Removing several people