# Instagram Email & Contact Scraper - Bio, Website & Link in Bio (`aolmo/instagram-contacts`) Actor

Emails, phones and social links of public Instagram profiles: contacts written in the bio plus the emails, phones and socials found on the website or link-in-bio page the profile links to. Followers, bio and name included. Only profiles with a contact are charged. $0.004 per profile.

- **URL**: https://apify.com/aolmo/instagram-contacts.md
- **Developed by:** [Antonio del Olmo Tena](https://apify.com/aolmo) (community)
- **Categories:** Lead generation, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 contact founds

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

Turn public Instagram profiles into contact rows: the emails and phones written in the bio, plus the emails, phones and social profiles found on the website or link-in-bio page the profile links to. Give usernames or profile URLs and get one row per profile with name, followers, bio, links and every contact found. Influencer outreach, creator and brand prospecting, local business lists and CRM enrichment at $0.004 per profile, and only profiles with at least one contact are charged.

The Actor reads what Instagram shows to a visitor of the profile (no login, no cookies of yours) and then opens the linked website or link-in-bio page (Linktree, Beacons, Stan, Bio.site...) to collect `mailto:` links, emails and phones in the text and the social icons. It never bypasses logins, CAPTCHAs or rate limits.

### What you get

**Profile**: `username`, `url`, `fullName`, `verified`, `private`, `followers`, `following`, `posts`, `bio`, `externalUrl`, `bioLinks`.

**Contacts from the bio**: `bioEmails`, `bioPhones`.

**Contacts from the website**: `siteEmails`, `sitePhones`, `websitesCrawled`, `pagesCrawled`, `websiteStatus` (`found`, `none`, `no-website`, `not-crawled` or `error`), `siteError`.

**Merged**: `emails` and `phones` (bio first, then website, no duplicates), `email` and `phone` (the first of each), `socials` (instagram, facebook, linkedin, twitter, youtube, tiktok, whatsapp, telegram... from the bio links and the website) and `hasContact`.

**Changes** on scheduled runs: `newContacts` lists the emails and phones that were not there in the previous run.

Profiles that do not exist, are private or could not be read return a row with an `error` field and are not charged. Profiles without any contact are returned (`hasContact: false`) and not charged.

### How to use it

1. Open the **Input** tab.
2. Add **Usernames or profile URLs**, one per line (up to 500 per run): `nasa`, `@natgeo` or `https://www.instagram.com/nike/`.
3. Keep **Read the website** on to collect the contacts of the linked site (2 pages by default: home, then contact or about), or turn it off to read the bio only.
4. Click **Start** and export the rows as JSON, CSV or Excel.
5. Schedule the Actor to be told when a profile adds an email or phone.

### Input

```json
{
  "usernames": ["nasa", "natgeo"],
  "crawlWebsite": true,
  "maxPagesPerSite": 2,
  "validateEmails": true
}
```

### Output

```json
{
  "username": "acmestudio",
  "url": "https://www.instagram.com/acmestudio/",
  "fullName": "Acme Studio",
  "followers": 12345,
  "bio": "Design studio in Madrid. Bookings: hello@acme.studio",
  "externalUrl": "https://acme.studio/",
  "bioEmails": ["hello@acme.studio"],
  "bioPhones": [],
  "siteEmails": ["hello@acme.studio", "sales@acme.studio"],
  "sitePhones": ["+34912345678"],
  "socials": { "linkedin": "https://www.linkedin.com/company/acme", "youtube": "https://www.youtube.com/@acmestudio" },
  "emails": ["hello@acme.studio", "sales@acme.studio"],
  "phones": ["+34912345678"],
  "email": "hello@acme.studio",
  "phone": "+34912345678",
  "websiteStatus": "found",
  "pagesCrawled": 2,
  "hasContact": true,
  "newContacts": null,
  "timestamp": "2026-10-21T10:00:00.000Z"
}
```

### Pricing

Pay per event: **$0.004 per profile with at least one contact** and **$0.002 per profile with a new email or phone** on a scheduled run. Profiles without contacts, private or missing accounts are free. A list of 1,000 profiles where 600 have a contact costs $2.40.

### Limits and notes

- Instagram shows visitors the bio and the links of public profiles; private profiles return their counters but no contacts.
- Only the website and link-in-bio page linked from the profile are read (up to 2 sites, up to 5 pages each). Marketplaces, maps and app stores are skipped.
- Website emails are checked against the domain's mail records when **Validate email domains** is on; bio emails are kept as written.
- Large lists run at about one profile per second.

### Related Actors

- **Instagram Profile Scraper**: followers, bio, links and latest posts without the website crawl.
- **Website Contact Extractor**: emails, phones and socials of any website.
- **Google Maps Email & Leads Extractor**: businesses from Google Maps with the contacts of their websites.
- **LinkedIn Company Leads Scraper**: LinkedIn company pages with the contacts of their websites.

# Actor input Schema

## `usernames` (type: `array`):

One per line: nasa, @natgeo or https://www.instagram.com/nike/. Up to 500 per run.

## `crawlWebsite` (type: `boolean`):

Open the website or link-in-bio page linked from the profile and collect its emails, phones and social links. Off reads the bio only.

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

How many pages of the linked website are read: home first, then contact and about pages.

## `validateEmails` (type: `boolean`):

Drops website emails whose domain cannot receive mail (DNS MX check).

## `product` (type: `string`):

Internal. Leave as is.

## Actor input object example

```json
{
  "usernames": [
    "nasa",
    "natgeo"
  ],
  "crawlWebsite": true,
  "maxPagesPerSite": 2,
  "validateEmails": true,
  "product": "instagram-contacts"
}
```

# Actor output Schema

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

Dataset items: url, changed, events, data, timestamp and error (when the target failed).

# 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 = {
    "usernames": [
        "nasa",
        "natgeo"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("aolmo/instagram-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 = { "usernames": [
        "nasa",
        "natgeo",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("aolmo/instagram-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 '{
  "usernames": [
    "nasa",
    "natgeo"
  ]
}' |
apify call aolmo/instagram-contacts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aolmo/instagram-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/ifraI6dzVGp75m6kX/builds/QNxAmsNpGIk7jbLlC/openapi.json