# ETB2B Key People Refresh (`event-data-api/etb2b-keypeople-refresh`) Actor

Single company → verified current key people (leadership + sales/marketing), live-verified from LinkedIn current position (no stale/namesake), seniority-ranked. Powers the ETB2B portal Refresh Key People button. By RS Niraj, ETB2B (Times Internet).

- **URL**: https://apify.com/event-data-api/etb2b-keypeople-refresh.md
- **Developed by:** [Dheeraj Singh Yadav](https://apify.com/event-data-api) (community)
- **Categories:** Automation, Lead generation
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ETB2B Key People Refresh

Lightweight single-company **key people** actor for the ETB2B portal's **"🔄 Refresh Key People"** button.

Runs ONLY the key-people cascade (no full company/event enrichment):
`company_name` → SERP discovery → harvestapi **live** verification → verified `key_people` JSON.

### What it returns (per company)

Only **verified current employees** matching the target-designation dictionary:

- **Leadership**: CEO, CTO, CFO, COO, CIO, CISO, CHRO, President, MD, Country Head/Manager
- **Sales & Marketing**: CMO, CRO, CGO, Head of Sales/Marketing/Digital/Demand-Gen/Brand/Partnerships, VP/GM/Director/Associate-Director (Sales/Marketing), Regional/Zonal Sales Head, National Sales Manager, Brand/Product-Marketing/Growth/Performance/Marketing Manager

Guarantees (mirrors the fixed bulk SponsorScope logic):

- `is_current_employee` is **strictly True** — company + role from the person's **live LinkedIn current position**; end-dated roles rejected → **no stale / no namesake** (e.g. someone who moved to another company is dropped).
- Bare "Director"/"Manager"/"Head"/"VP" with no function-anchor → rejected.
- Sorted **seniority-primary** (Founder > CEO > CXO > VP/Director > Head > Manager); India-location is a tiebreaker only.
- **No hard cap** — returns all who pass.

### Input

```json
{ "company_name": "Zoho", "apifyToken": "<full-permission token>" }
```

> The runtime token has limited permissions and cannot start the SERP/LinkedIn child actors, so the caller passes `apifyToken`. Falls back to env `APIFY_TOKEN` for local runs.

### Output (dataset item\[0])

```json
{
  "company_name": "Zoho",
  "count": 6,
  "key_people": [
    { "name": "...", "designation": "...", "company": "...",
      "linkedin": "...", "image": "...", "location": "...",
      "is_current_employee": true, "seniority_score": 90 }
  ],
  "_kp_source": "serp"
}
```

### How the portal should call it (reliable — avoids HTTP-0)

Do **not** use run-sync (long-held connection → HTTP-0 under load). Use **async run + poll + fetch**:

1. `POST /v2/acts/etb2b-keypeople-refresh/runs?token=<TOKEN>` body `{"company_name":"X","apifyToken":"<TOKEN>"}` → `run.id`, `defaultDatasetId`
2. `GET /v2/actor-runs/<run.id>?token=...` — poll every 3–5s until status ∈ SUCCEEDED/FAILED/ABORTED/TIMED-OUT
3. `GET /v2/datasets/<defaultDatasetId>/items?token=...&clean=true` → `[ { company_name, key_people[] } ]`
4. Retry 2–3× on HTTP 0 / 5xx / timeout at each step.

### Notes

- Key-people logic (`sponsor_enrichment.py`, `speaker_enrich.py`) is **copied** from the bulk SponsorScope actor. Any future key-people fix must be synced to both.
- Cascade-ready: when the Mongo → B2B/Solar → SERP source-cascade is added inside `_fetch_key_people_one`, this actor picks it up automatically.

By RS Niraj, ETB2B (Times Internet).

# Actor input Schema

## `company_name` (type: `string`):

Company / sponsor name to fetch verified current key people for.

## `apifyToken` (type: `string`):

Full-permission token used to run the SERP + LinkedIn child actors. The runtime token has limited permissions, so the caller must pass this. Falls back to env APIFY\_TOKEN for local runs.

## `tier` (type: `string`):

Optional sponsorship tier hint (e.g. Platinum, Gold).

## Actor input object example

```json
{
  "company_name": "Zoho"
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("event-data-api/etb2b-keypeople-refresh").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("event-data-api/etb2b-keypeople-refresh").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call event-data-api/etb2b-keypeople-refresh --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,event-data-api/etb2b-keypeople-refresh"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/tea6PXj5ZNkZS8GI6/builds/Une14PgFywdbQWFtv/openapi.json