# Domain to LinkedIn Company URL — Verified, with Headcount (`northbell/domain-to-linkedin-company`) Actor

Turn company websites, domains or work emails into their LinkedIn company pages. Uses the link on the company's own site first, then checks guesses against the website LinkedIn lists, so you never get a same-name stranger. Adds headcount, industry and HQ. Pay only for matches.

- **URL**: https://apify.com/northbell/domain-to-linkedin-company.md
- **Developed by:** [Northbell](https://apify.com/northbell) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.20 / 1,000 company matcheds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Domain to LinkedIn Company URL — Verified, with Headcount

Paste a list of **company websites, domains or work email addresses** and get each company's **LinkedIn company page** — checked, not guessed — plus its **headcount, followers, size band, industry, HQ and founding year**. **$4 per 1,000 matched companies; domains with no match are free.** No login, no cookies.

### How it finds the right page

1. **The link on the company's own site.** Most companies put their LinkedIn page in the footer. That is the company telling you which page is theirs — `anthropic.com` → `linkedin.com/company/anthropicresearch`, which no name-guessing would find.
2. **Verified guesses.** If the site has no link, it tries the likely handles (`stripe`, `stripe.com`, `stripehq`, `stripeinc`, `stripeapp`) and keeps one only if **the website on that LinkedIn page is the same domain**. `booking.com` returns Booking.com (17,313 employees), not the café called "Booking".
3. **Same name, different ending.** If the only page found lists `notion.com` for `notion.so`, you get it as `status: "probable"` — clearly marked, never mixed in with the sure matches.

### What you get

| Field | What it is |
|---|---|
| `domain` | the domain looked up (from a URL or an email address) |
| `status` | `matched`, `probable` or `not-found` |
| `matchedBy` | `website-link` (from the company's site), `linkedin-website` (the LinkedIn page lists this domain) or `same-name-website` |
| `linkedinUrl`, `slug`, `name` | the LinkedIn company page |
| `employees`, `followers`, `sizeBand` | LinkedIn's own headcount count, followers and the size band the company states |
| `industry`, `headquarters`, `founded`, `companyType`, `website` | from the LinkedIn page |

### Use it for

- **CRM and lead-list enrichment** — LinkedIn URL and headcount for every account in a list of domains
- **Signup qualification** — work emails in, company size and industry out
- **Account research** — find the right LinkedIn page before you prospect or track the company

### Input

```json
{ "domains": ["stripe.com", "https://www.notion.so", "jane@monzo.com"] }
```

Measured on October 7, 2026: 11 domains → 9 matched (6 from the company's own site link), 1 probable, 1 not found (example.com) — including anthropic.com, booking.com, linear.app, vercel.com and gymshark.com. At the default 20 LinkedIn requests per minute, plan on 5–25 seconds per domain.

Want headcount **growth** over time for the companies you found? Feed the LinkedIn URLs to [LinkedIn Company Scraper with Headcount Growth](https://apify.com/northbell/linkedin-company-growth-scraper).

### Pricing

**$4 per 1,000 matched companies** (`matched` or `probable`), plus $0.01 per run. **Not-found domains and error rows are free.** The $0.01 run-start fee is the one charge every run pays, even one that returns nothing.

### For AI agents

`{"domains": ["acme.com"]}` returns one row with `status`, `linkedinUrl` and `employees`. Rows have `type`: `company` or `error`.

# Actor input Schema

## `domains` (type: `array`):

One per line: "stripe.com", "https://www.notion.so/product" or "jane@acme.com" (the part after @ is used).

## `checkWebsite` (type: `boolean`):

Most companies link their LinkedIn page in the site footer — the most reliable match. Turn off to rely on verified guesses only.

## `maxRequestsPerMinute` (type: `integer`):

Kept polite by default.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "booking.com",
    "https://www.notion.so"
  ],
  "checkWebsite": true,
  "maxRequestsPerMinute": 20
}
```

# Actor output Schema

## `companies` (type: `string`):

Domain, match status, LinkedIn URL, headcount and industry.

# 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 = {
    "domains": [
        "stripe.com",
        "booking.com",
        "https://www.notion.so"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/domain-to-linkedin-company").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 = { "domains": [
        "stripe.com",
        "booking.com",
        "https://www.notion.so",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/domain-to-linkedin-company").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 '{
  "domains": [
    "stripe.com",
    "booking.com",
    "https://www.notion.so"
  ]
}' |
apify call northbell/domain-to-linkedin-company --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbell/domain-to-linkedin-company"
        }
    }
}
```

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/9cQjveCo62t0mVndJ/builds/eWJEbRCBanNgZPFUs/openapi.json