Set Connector Owner

PUT

network

connectors

{linkedinId}

owner

curl -X PUT "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"owner_email": "marine.b@example.com"}'

curl -X PUT "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "owner_email": "new.rep@example.com",
    "owner_name": "New Rep",
    "create_owner_if_missing": true
  }'

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

import requests

requests.put(
    "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"owner_email": "marine.b@example.com"},
)

await fetch("https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner", {
  method: "PUT",
  headers: { Authorization: "Bearer YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({ owner_email: "marine.b@example.com" }),
});

{
  "success": true,
  "data": {
    "connector_linkedin_id": "nicdelaye",
    "owner": {
      "id": "8f1b2c34-5d6e-4f70-8a91-b2c3d4e5f607",
      "email": "marine.b@example.com",
      "first_name": "Marine",
      "last_name": "B",
      "avatar_url": "",
      "is_member": true,
      "opportunity_count": 63
    },
    "updated_opportunities": 63
  }
}

{
  "success": false,
  "error": {
    "message": "No owner found for owner_email: ghost@example.com. Set create_owner_if_missing=true to add them to the owner directory.",
    "code": "BAD_REQUEST"
  }
}

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

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

Assign an owner to a connector that is already in your network. No reimport, no job, no credits. The change is immediate.

An owner owns a connector, and everything that connector produces. There is no such thing as owning a single opportunity: Update Opportunity rejects owner fields and points here.The other way to set this is owner_email on Import Connectors, at import time. This endpoint is how you set or change it afterwards, without reimporting.

Assigning an owner here does three things:

The connector reports that owner in List Connectors and counts toward it in List Owners connector_count, connectors_by_tag and opportunity_count.
Every opportunity the connector already has moves to that owner, so their book does not split between the old and the new owner.
Opportunities discovered for that connector by later imports land owned, with no further calls.

Path Parameters

string

required

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

Body

Send owner_id or owner_email, not both.

string

An owner id from List Owners.

string

Resolved against your owner directory. The same address you would send as owner_email when importing.

boolean

default:"false"

Add owner_email to the directory when no owner holds it yet, instead of failing. Use this for self-service flows where the person being assigned may not be in the directory. No seat is used, no email is sent, and no access is granted. See Owners are a directory, not a seat.

string

Display name for an owner created by create_owner_if_missing. Ignored when the address already resolves to an owner.

Response Fields

string

The connector you assigned.

object

The owner now accountable for the connector. Same shape as Get Owner. null after a DELETE.

integer

How many of the connector’s existing opportunities were written to this owner. This is the connector’s whole current book, so re-sending the same owner reports the same number rather than 0.

Removing an owner

DELETE on the same path clears it. The connector reports no owner afterwards and newly discovered opportunities stop inheriting one. Opportunities already assigned keep the owner stamped on them, so a DELETE never silently empties a live book — reassign the connector with PUT if that is what you meant. The DELETE is idempotent. Clearing an owner that is already absent succeeds.

curl -X PUT "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"owner_email": "marine.b@example.com"}'

curl -X PUT "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "owner_email": "new.rep@example.com",
    "owner_name": "New Rep",
    "create_owner_if_missing": true
  }'

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

import requests

requests.put(
    "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"owner_email": "marine.b@example.com"},
)

await fetch("https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner", {
  method: "PUT",
  headers: { Authorization: "Bearer YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({ owner_email: "marine.b@example.com" }),
});

{
  "success": true,
  "data": {
    "connector_linkedin_id": "nicdelaye",
    "owner": {
      "id": "8f1b2c34-5d6e-4f70-8a91-b2c3d4e5f607",
      "email": "marine.b@example.com",
      "first_name": "Marine",
      "last_name": "B",
      "avatar_url": "",
      "is_member": true,
      "opportunity_count": 63
    },
    "updated_opportunities": 63
  }
}

{
  "success": false,
  "error": {
    "message": "No owner found for owner_email: ghost@example.com. Set create_owner_if_missing=true to add them to the owner directory.",
    "code": "BAD_REQUEST"
  }
}

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

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

Bulk assignment

There is no batch form. Call this once per connector; the writes are independent, so they can run concurrently. To find the connectors that still need an owner, list them with List Connectors and ?owner_email=unassigned.

curl -X PUT "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"owner_email": "marine.b@example.com"}'

curl -X PUT "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "owner_email": "new.rep@example.com",
    "owner_name": "New Rep",
    "create_owner_if_missing": true
  }'

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

import requests

requests.put(
    "https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"owner_email": "marine.b@example.com"},
)

await fetch("https://api.clustr-ai.com/api/public/network/connectors/nicdelaye/owner", {
  method: "PUT",
  headers: { Authorization: "Bearer YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({ owner_email: "marine.b@example.com" }),
});

{
  "success": true,
  "data": {
    "connector_linkedin_id": "nicdelaye",
    "owner": {
      "id": "8f1b2c34-5d6e-4f70-8a91-b2c3d4e5f607",
      "email": "marine.b@example.com",
      "first_name": "Marine",
      "last_name": "B",
      "avatar_url": "",
      "is_member": true,
      "opportunity_count": 63
    },
    "updated_opportunities": 63
  }
}

{
  "success": false,
  "error": {
    "message": "No owner found for owner_email: ghost@example.com. Set create_owner_if_missing=true to add them to the owner directory.",
    "code": "BAD_REQUEST"
  }
}

{
  "success": false,
  "error": {
    "message": "No connector found with linkedin id: nicdelaye",
    "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

Set Connector Owner

Path Parameters

Body

Response Fields

Removing an owner

Bulk assignment

​Path Parameters

​Body

​Response Fields

​Removing an owner

​Bulk assignment

Path Parameters

Body

Response Fields

Removing an owner

Bulk assignment