Skip to main content
POST
Set one owner on many connectors in one call. For each connector it does what Set Connector Owner does: the connector’s owner, its existing intros moved to that owner, and intros later imports find landing owned. Send owner_id, an owner from List Owners, or unassigned to clear the owner (the intros keep theirs). Then exactly one of:
  • connector_ids: the connectors, by their per_ Clustr ids (LinkedIn slugs work too).
  • filters: the Connectors list’s filters, as a JSON object of key to string or string array, for every connector they match.
push_to_crm writes the owner to each connector’s CRM contact too, for a list of ids only; asking it of filters is a 400. Ids that are not connectors are skipped, and more than 25,000 connectors is a 400. The answer says how many connectors the selection matched, how many were updated (their owner changed), how many intros moved (updated_intros), and what the CRM push did (crm_push).

Authorizations

Authorization
string
header
required

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

Body

application/json

Exactly one of connector_ids and filters; the CRM push works on ids only.

owner_id
string
required

The owner: an own_ Clustr id or uuid, or unassigned to clear it.

connector_ids
string[]

The connectors: per_ Clustr ids or LinkedIn slugs.

filters
object

The Connectors list's query parameters, as GET /v2/people takes them, for "select all N matching": each key to a string, or to an array of strings for a repeated key.

push_to_crm
boolean

Also write the owner to each connector's CRM contact. Ticked ids only.

Response

Typed result envelope.

success
boolean
required
data
object
required