List Owners
List the people an opportunity can be assigned to
clustr_owner_id as owner_id, or the email as owner_email, with the Update Opportunity endpoint.
Finding teammates who have not built their own network
connectors_by_tag is how you tell a teammate who was added by a bulk roster import
from one who has connected their own network. Import-created connectors carry whatever
tag the import assigned them; self-service connectors carry the tag your workspace uses
for personal contacts.
opportunity_count will not tell you this. Someone imported from a roster
has a non-zero opportunity count and looks active, even though they have contributed
nothing personally.
Which tag means “personal” is your decision: tag names are yours to define, so the API
returns the breakdown rather than guessing.
Checking a batch of people at once
Pass every address you care about in a single request (for example the members of one deal channel) and read the counts back together:Authorizations
The API key you created on the API settings page of the Clustr app.
Query Parameters
Filter owners by name or email. Omit to return the whole directory.
Set to true to populate opportunity_count on each owner. Off by default, because counting makes the request slower.
true, false Restrict the directory to these exact addresses, matched case-insensitively. Repeat the parameter (?email=a@x.com&email=b@x.com) or comma-separate them (?email=a@x.com,b@x.com).
Use this to resolve a batch of addresses in one request rather than one request each. An address that matches no owner is left out of the response, so comparing what you sent against what came back tells you which people are owners.
Set to true to populate connector_count and connectors_by_tag on each owner. This is separate from with_counts and off by default, because it makes the request slower.
true, false