Sales Signals You Can Read From People Data
By Kooperativa Engineering
A sales signal is a dated event that gives a rep a reason to write this week and not next quarter. Most lists of signals mix two very different kinds of event, and the difference decides what you can build.
The first kind is behavioral: someone visited your pricing page, a team started researching your category, an account's ad spend changed. A people data API cannot see any of that. The second kind is organizational: people joining, leaving or changing role at a company. That is what profile data records, and it is what this article covers. Intent data is a different product, and nothing below replaces it.
Three signals you can read from people data
Each of these is a count or a list that you can compute for any account on a schedule.
- New people at an account. A burst of joins in 30 days compared with the previous 60 shows a team being built, which usually means new tooling decisions.
- Senior arrivals. A new VP or director in the function you sell to is the classic reason to reach out, because new leaders tend to review what they inherit.
- Changes at people you already know. A contact who moves or changes title is a reason to contact them again, and a monitor reports it without any polling.
Reading joins and senior arrivals
The hiring-signals endpoint lists people who started their current role at a company inside a window, and its total tells you how many. It has no location filter, so a global company's count includes every country. To keep the signal to the US, use people search with a company id, a seniority level, a country and a start date.
# New people at an account in the last 30 days (all levels, all countries)
curl "https://kooperativa.io/api/v1/company/hiring-signals?company_id=COMPANY_ID&days=30&per_page=1" \
-H "Authorization: Bearer ik_live_..."
# The same, restricted to the US and to one senior level
curl -X POST "https://kooperativa.io/api/v1/people/search" \
-H "Authorization: Bearer ik_live_..." \
-H "Content-Type: application/json" \
-d '{
"company_id": "COMPANY_ID",
"seniority": "vp",
"location": "US",
"job_changed_after": 1792000000,
"per_page": 50
}'Two things to know before you trust the output. The hiring-signals endpoint reports people who joined, not open roles, so it shows that a team is growing and cannot say which jobs are being filled. And seniority is derived from the words in a job title, not entered by anyone.
That second point matters. In a quick check on two large software companies on 15 November 2026, results labelled VP included a partner development intern, a principal software engineer and a solution architect enablement partner. The label is a starting filter, not a verdict. Read the title before you count the person as a senior arrival, or filter obvious junior words out in code, as the script below does.
A weekly ranking in one function
Put the three counts into one score per account and sort. The weights below are arbitrary on purpose: they are a place to start, and the right values are the ones that best predict your own closed deals.
const BASE = 'https://kooperativa.io/api/v1';
const headers = {
Authorization: `Bearer ${process.env.KOOPERATIVA_API_KEY}`,
'Content-Type': 'application/json',
};
const SENIOR = ['c-level', 'vp', 'director'];
const JUNIOR_TITLE = /\b(intern|assistant|associate|trainee)\b/i;
const since = (days) => Math.floor(Date.now() / 1000) - days * 86400;
async function joins(companyId, days) {
const res = await fetch(
`${BASE}/company/hiring-signals?company_id=${companyId}&days=${days}&per_page=1`,
{ headers },
);
return res.ok ? (await res.json()).total ?? 0 : 0;
}
async function seniorJoins(companyId, days) {
let count = 0;
for (const seniority of SENIOR) {
const res = await fetch(`${BASE}/people/search`, {
method: 'POST',
headers,
body: JSON.stringify({
company_id: companyId,
seniority,
location: 'US',
job_changed_after: since(days),
per_page: 50,
}),
});
if (!res.ok) continue;
const { results = [] } = await res.json();
// seniority comes from title text, so drop obvious false positives
count += results.filter((p) => !JUNIOR_TITLE.test(p.current_title ?? '')).length;
}
return count;
}
export async function scoreAccount(companyId) {
const [recent, earlier, senior] = await Promise.all([
joins(companyId, 30),
joins(companyId, 90),
seniorJoins(companyId, 30),
]);
// arbitrary starting weights: tune them against your own closed deals
return { companyId, recent, earlier, senior, score: senior * 3 + recent };
}Run it over a list of target accounts once a week and read the top of the list, not the whole thing. Each account costs three to five calls, so a few hundred accounts is a few thousand calls. Watch for a 429 response and wait for the Retry-After header it carries.
What this approach cannot do
It cannot tell you that anyone is looking for a vendor. A company that hired thirty people may have budget and may also have a signed contract with your competitor. It reflects what people updated on their professional profiles, so it lags by however long that takes, and records in the index refresh on a cycle of up to 90 days. And it sees joins at companies where people keep their profiles current, which is better in some industries than in others.
Treat the ranking as a reason to look at an account today, and confirm the reason before a message goes out.
Get started
Try Kooperativa
One API key. Person and company enrichment, structured search, and monitors under one flat license.