Colleagues API: Multi-Thread a Deal
By Kooperativa Engineering
Multi-threading, reaching more than one stakeholder inside a target account instead of betting everything on a single contact, is standard sales advice, but it usually requires manual research to find the additional names. A colleagues endpoint automates exactly that step: given one known profile, it returns everyone else currently at the same company.
How the lookup actually works
The endpoint takes an internal profile ID, not a raw name or URL, so it assumes you have already enriched the starting contact once. That single enrichment gives you both the person and the company_id needed for this and most other company-scoped endpoints going forward.
{
"id": "f9413465-...",
"company_id": "1035",
"company_name": "Microsoft",
"colleagues": [
{
"id": "a1b2c3d4-...",
"full_name": "Brad Smith",
"current_title": "Vice Chair and President",
"linkedin_url": "https://www.linkedin.com/in/bradsmith"
}
],
"total": 231464,
"page": 1,
"per_page": 25,
"pages": 9259
}Why this returns the same shape as current employees
Colleagues and current employees answer nearly the same underlying question, everyone currently at company X, filtered by whether you started from a known person or a known company ID. For a company the size of Microsoft, 231,464 colleagues is not a usable list on its own, which is the same reason current-employees rosters need a follow-up filter by title or seniority rather than a raw page-through.
The workflow this is actually built for
In practice this endpoint is most useful immediately after a first successful conversation: you have one engaged contact, you want to find their manager, their peers, or an adjacent department, and colleagues gives you the roster to filter down manually rather than requiring a second round of company-level search.
Get started
Try Kooperativa
One API key. Person and company enrichment, structured search, and monitors under one flat license.
