# Website Contact Extractor (`pontio/website-contacts`) Actor

Emails, phone numbers and social profiles from a company website: homepage plus its contact, about and imprint pages.

- **URL**: https://apify.com/pontio/website-contacts.md
- **Developed by:** [Gabor Molnar](https://apify.com/pontio) (community)
- **Categories:** Lead generation, Marketing, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 site with contacts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Website Contact Extractor

Get the email addresses, phone numbers and social profiles a company publishes on its own website. Pass one domain or a list of up to 1,000 in a single run. For each site the Actor reads the homepage and up to three of its contact, about, team and imprint pages, and returns one clean record. You pay only for sites where it found something.

### What you get

One dataset item per site you send. Here is one of them, for input `heise.de`:

```json
{
  "domain": "heise.de",
  "reasonCode": "contacts_found",
  "emails": ["newstipps@heise.de", "webmaster@heise.de"],
  "phones": ["+4951153520", "+495115352129"],
  "socials": [
    { "network": "instagram", "url": "https://instagram.com/heiseonline" },
    { "network": "linkedin", "url": "https://linkedin.com/company/heiseonline" }
  ],
  "pagesCrawled": [
    "https://www.heise.de/",
    "https://www.heise.de/kontakt/",
    "https://www.heise.de/impressum.html"
  ]
}
```

### Use it when

- You have a list of company domains and need a way to reach each one.
- You are enriching leads from a CRM export or a scraped directory.
- You want a company's official LinkedIn, X, Facebook, Instagram, YouTube, TikTok or GitHub account, not a share button or a policy page.
- An agent needs one typed contact record per domain.

### Input

| Field | Type | Required | What it does |
| --- | --- | --- | --- |
| `domains` | array of strings | yes | The websites to read, up to 1,000 per run. A URL or an email address is accepted and reduced to its site, so `https://acme.com/pricing` and `jane@acme.com` both mean `acme.com`. A site that appears more than once is read and charged once. |

### Output

| Field | What it holds |
| --- | --- |
| `domain` | The site that was read, normalized. |
| `reasonCode` | What happened. See the pricing table. |
| `emails` | Every address found, lowercased and deduplicated. Addresses inside scripts and styles are ignored, so SDK keys and `logo@2x.png` don't show up. |
| `phones` | Valid numbers in E.164 form. Taken from `tel:` links and from page text written the way people write phone numbers. A number with no country code uses the site's country domain (`.de` means Germany). A number that doesn't validate is dropped, not guessed at. |
| `socials` | Profile links, one per account, in canonical form (`twitter.com/acme` becomes `x.com/acme`). |
| `pagesCrawled` | The pages that were actually read, after redirects. |

### Pricing

Pay per event, $3.00 per 1,000 sites with contacts ($0.003 each), charged on the `website-contacts-found` event.

You pay only when the Actor found at least one contact. If a site loads but shows nothing we recognize, that is free, because a site that draws its contact details with JavaScript looks exactly the same.

| `reasonCode` | Charged |
| --- | --- |
| `contacts_found` | yes |
| `no_contacts_found` (the pages loaded and held no contacts) | no |
| `blocked` (the site refused us with 401, 403 or 429) | no |
| `unreachable` (no DNS, no connection, a timeout, or a server error) | no |
| `invalid_domain` (an IP, a bare TLD, `localhost`, a malformed name) | no |

If you set a maximum total charge for a run, the Actor stops as soon as that limit is reached instead of working for free. Items after that point are left out of the dataset and not charged, and the run log says how many; submit them in a new run.

### Limits

- Pages are read as HTML. Contacts that appear only after JavaScript runs are not seen.
- At most four pages per site: the homepage plus three contact-type pages linked from it.
- Sites are read one after another. If you set a maximum charge for the run, or the run reaches its timeout, it stops there. The items already written stay in the dataset, so you can re-run the remainder.

### Personal data

The Actor reads only pages a site shows to every visitor, at most four per site, and identifies itself with an honest User-Agent. What it returns can still include personal data, such as a named employee's address or a direct line. You decide what that data is used for, so under the GDPR and similar laws you are the controller: you need a lawful basis for processing it (for B2B outreach that is usually legitimate interest), and you must honor objections and opt-outs. Results go to your own Apify dataset under your account's retention settings. The Actor keeps no copy.

# Actor input Schema

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

Websites to extract contacts from, as domains or URLs, e.g. example.com (max 1000 per run). Repeats of the same site are dropped. Charged only for sites where contacts were found.

## Actor input object example

```json
{}
```

# Actor output Schema

## `results` (type: `string`):

One item per input, in this run's default dataset.

# 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("pontio/website-contacts").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("pontio/website-contacts").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 pontio/website-contacts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pontio/website-contacts"
        }
    }
}
```

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/0rhANRfgy8qIyppJi/builds/8f6VIXKt1iA2kxbpG/openapi.json