# Contact Details Scraper: Company Emails & Phones (`usta/website-contact-details`) Actor

For sales-operations leads: paste a list of company websites and get one row per site with the shared mailboxes, switchboard phones, company social pages and postal address the company publishes for itself. Named staff contacts are skipped.

- **URL**: https://apify.com/usta/website-contact-details.md
- **Developed by:** [US Tech Automations](https://apify.com/usta) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 result rows

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

## Company Contact Details from a List of Websites

This contact details scraper is a website email scraper for public contact info: paste company website addresses and get, for each site, the shared mailboxes, switchboard phones, and company social pages that company publishes for itself.

Named staff mailboxes, personal mobiles, home addresses, and staff profile links are skipped. Each skipped named mailbox is counted on the row.

### Input

| Field | What it does |
|---|---|
| **Company website addresses** | Your list of public company sites (home pages or a contact/about URL). One row per URL. |
| **Maximum pages per site** | Home page plus same-site pages whose path or link text looks like contact, about, impressum, support, or locations. Default 5, cap 15. Staff/profile pages are not opened. |
| **Maximum rows** | Hard ceiling on site rows, and therefore on the cost of the run. Default 50, maximum 1,000. |
| **Proxy configuration** | Optional Apify proxy. Off by default, including on a local run. |

Each host is checked against its `robots.txt` `User-agent: *` rules before any HTML page is read. A disallowed start URL becomes one error row for that site (`robots_allowed` is false). When `robots.txt` sets a crawl delay, that delay is honoured.

### Pricing

**Pay per result. $0.005 per row. No start fee.**

Every dataset row bills from row one, including an error row for a site that 404s or is blocked by robots.txt. A run that returns no rows costs nothing. **Maximum rows** is the spend cap.

### Output (one row per site)

One example row from a real local run on 2026-09-21 against `https://www.eff.org/about/contact` (3 HTTPS GETs on this machine: robots.txt, the contact page, the home page):

```json
{
  "site": "https://www.eff.org/about/contact",
  "company_name": "Electronic Frontier Foundation",
  "company_mailboxes": [
    "info@eff.org",
    "press@eff.org",
    "membership@eff.org",
    "activist@eff.org",
    "hr@eff.org"
  ],
  "mailbox_source_pages": {
    "info@eff.org": "https://www.eff.org/about/contact",
    "press@eff.org": "https://www.eff.org/about/contact",
    "membership@eff.org": "https://www.eff.org/about/contact",
    "activist@eff.org": "https://www.eff.org/about/contact",
    "hr@eff.org": "https://www.eff.org/about/contact"
  },
  "named_addresses_skipped": 0,
  "company_phones": [],
  "company_social_links": [
    "https://www.facebook.com/eff",
    "https://www.instagram.com/efforg/",
    "https://www.youtube.com/efforg",
    "https://www.linkedin.com/company/EFF"
  ],
  "postal_address": null,
  "pages_read": [
    "https://www.eff.org/about/contact",
    "https://www.eff.org/"
  ],
  "robots_allowed": true,
  "error": null,
  "http_status": 200,
  "message": null,
  "fetched_at": "2026-09-21T01:00:53Z"
}
```

`company_phones` is empty on that row because the page prints a number as text and does not expose a `tel:` link or schema.org `telephone`. `postal_address` is empty because the page does not publish a schema.org PostalAddress. Those fields are not guessed.

| Field | What it holds |
|---|---|
| `site` | The URL you pasted |
| `company_name` | From schema.org Organization, `og:site_name`, or the page title |
| `company_mailboxes` | Shared role addresses only (`info`, `sales`, `press`, `hr`, and similar). Named people are omitted. |
| `mailbox_source_pages` | The page each kept mailbox was first read from |
| `named_addresses_skipped` | Count of first.last-style addresses that were dropped |
| `company_phones` | `tel:` links and schema.org `telephone` values |
| `company_social_links` | Company pages only: LinkedIn `/company/`, Facebook, X/Twitter, Instagram, YouTube, from header/footer, a contact page, or Organization `sameAs`. `/in/` staff profiles are skipped. |
| `postal_address` | schema.org address when present; otherwise `null` |
| `pages_read` | HTML pages actually fetched |
| `robots_allowed` | `true` when `User-agent: *` allowed the start URL |
| `error` / `message` / `http_status` | Set only when that site failed |
| `fetched_at` | When this run read the site, in UTC |

### What this does not do

- It does not output a named person's email, a personal mobile, a home address, or a staff LinkedIn/Facebook profile. Those are dropped. Named mailboxes are counted in `named_addresses_skipped`.
- It does not guess addresses. A mailbox has to appear on a fetched page (including simple `info [at] host [dot] com` obfuscation).
- It does not log in, send cookies, or solve a CAPTCHA. A block becomes an error row.
- It does not render JavaScript. Contact details that exist only after a script runs are not read.
- It does not ignore `robots.txt`. If `User-agent: *` disallows the path, that site is not crawled.
- It does not grant a licence to use a company's contact details. You supply the URLs; each site's terms still apply.
- It does not verify that a mailbox receives mail.

### Limits

- At most 15 HTML pages per site, 1,000 sites per run.
- One second between requests to a host, or that host's `Crawl-delay` when it is larger (EFF's `robots.txt` asks for 30 seconds).
- Public HTML only. No sitemap dump, no DNS mailbox guessing, no enrichment against other databases.

# Actor input Schema

## `startUrls` (type: `array`):

The buyer's own list of public company website home pages (or a contact/about URL). One row is produced per URL. Local addresses and URLs with passwords are refused.

## `maxPagesPerSite` (type: `integer`):

Home page plus same-site pages whose path or link text looks like contact, about, impressum, support, or locations. Default 5. Cap 15. Staff/profile pages are not opened.

## `maxItems` (type: `integer`):

Hard ceiling on site rows returned, and therefore on the cost of the run. Every row bills at the listed price from row one; there is no start fee. A blocked or missing site produces one error row for that URL.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Leave off for a local run. Each site is ordinary HTTPS GET of robots.txt and a few public HTML pages.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.python.org/",
    "https://www.mozilla.org/"
  ],
  "maxPagesPerSite": 5,
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `sites` (type: `string`):

No description

## `csv` (type: `string`):

No description

## `report` (type: `string`):

No description

# 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 = {
    "startUrls": [
        "https://www.python.org/",
        "https://www.mozilla.org/"
    ],
    "maxPagesPerSite": 5,
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/website-contact-details").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 = {
    "startUrls": [
        "https://www.python.org/",
        "https://www.mozilla.org/",
    ],
    "maxPagesPerSite": 5,
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("usta/website-contact-details").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 '{
  "startUrls": [
    "https://www.python.org/",
    "https://www.mozilla.org/"
  ],
  "maxPagesPerSite": 5,
  "maxItems": 50
}' |
apify call usta/website-contact-details --silent --output-dataset

```

## MCP server setup

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

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/7Sogb4IEalDqTmc4I/builds/cKh5mgN4MnYT08QOM/openapi.json