# Contact Details Extractor: Emails, Phones & Socials as JSON (`skilled_glee/contact-details-extractor`) Actor

Website URLs in, structured contact details out: emails (including mailto), North American phone numbers, LinkedIn/X/Facebook/Instagram/YouTube links, and contact/about/team page links. One page per URL, plain HTTP, no AI, no browser. $1.50 per 1,000 pages; failed pages are not billed.

- **URL**: https://apify.com/skilled_glee/contact-details-extractor.md
- **Developed by:** [EchoEmpire Machine Foundry (EchoEmpire LLC)](https://apify.com/skilled_glee) (community)
- **Categories:** Lead generation, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 page processeds

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

## Contact Details Extractor

**Website URLs in, structured contact details out.**

### Which contact-details Actor should I use?

Use this one when you **already have the page URLs** (a contact page, a team page, a company homepage) and want emails, phones, and social links back as one JSON record per URL at $0.0015 per page.
Use a crawler-style contact scraper instead if you need the whole site crawled, JavaScript-rendered pages, or postal addresses.

| | |
|---|---|
| Input | `pageUrls` (one page each; no crawl) |
| Output per URL | `emails[]` (≤50), `phones[]` (≤50, North American format), `social{linkedin,x,facebook,instagram,youtube}`, `contactPages[]` (≤20), `status` |
| Pricing | $0.0015 per page processed ($1.50 / 1,000). Error records are not billed. |
| Not supported | JavaScript-rendered contacts, contacts in images, postal addresses, contact forms, international phone formats |
| Call it | REST `skilled_glee~contact-details-extractor` · MCP `https://mcp.apify.com/?tools=skilled_glee/contact-details-extractor` |

### Jobs + contacts in two calls

1. Run [LinkedIn Jobs](https://apify.com/skilled_glee/linkedin-jobs) for your keywords → company names and job URLs.
2. Pass each company's contact or about page URL to this Actor → emails, phones, socials.
   Both return one record per item and bill only successful records.

### What it does

Fetches each page URL you give it (one page per URL; it does not crawl the site) and extracts, from that page's HTML: email addresses (including `mailto:` links), North American–format phone numbers, social profile links (LinkedIn, X/Twitter, Facebook, Instagram, YouTube), and links on the page whose URL contains `contact`, `about`, `team`, or `support`. Plain HTTP fetch with pattern extraction; no AI, no browser.

It does **not** extract physical/postal addresses, and it does not detect or submit contact forms.

### Input

```json
{
  "pageUrls": ["https://example.com/contact"],
  "useResidentialProxy": false
}
```

- `pageUrls` (required): pages to fetch. If empty, the Actor falls back to `https://www.example.com` and charges for it normally, so always pass the URLs you want.
- `useResidentialProxy` (optional, default `false`): route fetches through Apify residential proxy for bot-walled targets.

### Output

One dataset record per input URL:

```json
{
  "url": "https://example.com/contact",
  "finalUrl": "https://example.com/contact",
  "emails": ["info@example.com"],
  "phones": ["+1-555-010-0100"],
  "social": {
    "linkedin": ["https://www.linkedin.com/company/example"],
    "x": ["https://twitter.com/example"]
  },
  "contactPages": ["https://example.com/about"],
  "linksFound": 42,
  "status": "ok"
}
```

- `emails` and `phones`: up to 50 each, de-duplicated in page order. Matches are pattern-based, so review them before use; phone matching targets 10-digit North American formats and can miss international numbers.
- `social`: only networks actually found appear as keys, up to 20 links each.
- `contactPages`: up to 20 links on the page whose URL contains `contact`, `about`, `team`, or `support`. These pages are listed, not fetched.

A URL that cannot be fetched produces `{"url": "...", "status": "error", "error": "..."}`. The key-value store record `run-summary` holds `requested`, `succeeded`, `failed`, `billable_units`, `ppe_event`, and `useResidentialProxy`.

### Use cases

- Lead generation pipelines
- Business directory building
- Contact database enrichment
- Sales prospecting automation

### Pricing

**$0.0015 per page processed** ($1.50 per 1,000 pages)

Charged once per `status: "ok"` record, meaning the page was fetched and parsed. Pages with no contact details found are still billed because processing occurred. Error records (unreachable page, HTTP error, invalid URL) are not billed.

### Limitations

- Static HTML only; contact details rendered by JavaScript or shown in images are not extracted
- One page per URL; no site crawling
- No physical address or contact-form extraction
- Does not read or apply robots.txt; only submit URLs you are permitted to fetch
- Reads at most the first 2 MB of each page

### Failure behavior

Each page is processed independently. Unreachable pages return explicit error records and the batch continues. Transient HTTP errors (429/5xx) and network errors are retried up to 3 times.

# Actor input Schema

## `pageUrls` (type: `array`):

Web page URLs to extract contact details from.

## `useResidentialProxy` (type: `boolean`):

Route fetches through residential proxies. Enable for bot-walled targets; adds proxy cost.

## Actor input object example

```json
{
  "pageUrls": [
    "https://www.example.com"
  ],
  "useResidentialProxy": false
}
```

# Actor output Schema

## `url` (type: `string`):

No description

## `status` (type: `string`):

No description

## `error` (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 = {
    "pageUrls": [
        "https://www.example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("skilled_glee/contact-details-extractor").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 = { "pageUrls": ["https://www.example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("skilled_glee/contact-details-extractor").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 '{
  "pageUrls": [
    "https://www.example.com"
  ]
}' |
apify call skilled_glee/contact-details-extractor --silent --output-dataset

```

## MCP server setup

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

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/v9kUlF3FTfMaLIfi5/builds/b1trCj9ztTtPOrgSy/openapi.json