# about.me Profile Scraper — Bios, Links, Emails & Contact Info (`ahmed_jasarevic/aboutme-profile-scraper`) Actor

Scrape about.me professional profiles by handle or URL: name, headline, bio, avatar, location, public emails & phones, social and custom links, cover image, tags, interests, schools and jobs. Built for B2B prospecting, recruiting and outreach teams

- **URL**: https://apify.com/ahmed\_jasarevic/aboutme-profile-scraper.md
- **Developed by:** [Ahmed Jasarevic](https://apify.com/ahmed_jasarevic) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## about.me Profile Scraper

### What does about.me Profile Scraper do?

**about.me Profile Scraper** extracts professional profile data from [about.me](https://about.me) — the personal bio/profile directory where millions of professionals, freelancers, entrepreneurs and creators present themselves. Give it a list of **handles or profile URLs** (e.g. `alexandriadolan` or `https://about.me/alexandriadolan`) and it returns structured data for each profile: **name, headline, bio, avatar, location, public emails & phone numbers, social and custom links, cover image, tags, interests, schools and jobs**.

The actor runs on the **Apify platform**, so you get API access, scheduling, monitoring, proxy rotation and easy integration with your existing workflows out of the box.

### Why use about.me Profile Scraper?

- **B2B sales prospecting** — enrich your lead lists with bios, locations and contact details.
- **Recruiting & talent sourcing** — find candidates' professional summaries, interests and social profiles.
- **Networking & outreach teams** — collect public emails, phones and social links for personalized outreach.
- **Lead list building** — optionally discover thousands of profiles straight from about.me's public sitemap.

### How to use about.me Profile Scraper

1. Open the actor in Apify Console and click **Start**.
2. In the **Input** tab, paste a list of about.me handles or full profile URLs (one per line).
3. Optionally enable **Discover profiles from sitemap** to auto-find profiles.
4. Click **Start** and wait for the run to finish.
5. Download the results from the **Dataset** tab as JSON, CSV, Excel or HTML.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `profileUrls` | array of strings | `[]` | about.me handles or full profile URLs |
| `discoverFromSitemap` | boolean | `false` | Auto-discover profiles from about.me's public sitemap |
| `maxSitemaps` | integer | `20` | How many per-user sitemap files to scan when discovery is on |
| `maxSitemapProfiles` | integer | `200` | Max profile URLs collected from sitemaps |
| `maxItems` | integer | `100` | Max profiles to scrape per run |
| `maxConcurrency` | integer | `5` | Concurrent requests |
| `useApifyProxy` | boolean | `true` | Route requests through the Apify proxy |
| `proxyGroup` | string | `AUTO` | Proxy group (`AUTO`, `BUYPROXIES94952`, `StaticUS3`) |

### Output

Each dataset item is one profile:

```json
{
  "url": "https://about.me/shawnmichaelburns",
  "handle": "shawnmichaelburns",
  "name": "Shawn Burns",
  "headline": "Volunteer, Musician",
  "bio": "I am a graduate of the University of Central Florida currently living in Hollywood, Florida...",
  "avatar": "https://assets.about.me/background/users/s/h/a/shawnmichaelburns_1503074044_26.jpg",
  "coverImage": "https://aboutme.b-cdn.net/background/users/s/h/a/shawnmichaelburns_1503074044_26.jpg",
  "location": "Hollywood, FL, United States",
  "emails": [],
  "phones": [],
  "links": [{ "platform": "linkedin", "url": "https://www.linkedin.com/in/shawnmichaelburns/" }],
  "tags": [],
  "interests": ["Sports", "Innovation", "Politics", "Volunteering", "Entrepreneurship"],
  "schools": ["University of Central Florida"],
  "jobs": [],
  "contactMeEnabled": true,
  "customDomains": [],
  "themeColor": "D93B26",
  "premium": false,
  "userId": 2248623,
  "scrapedAt": "2026-08-18T12:00:00.000Z"
}
```

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

### Data table

| Field | Description |
|-------|-------------|
| `url` | Canonical profile URL |
| `handle` | about.me username |
| `name` | Full name |
| `headline` | Roles/headline shown on the profile |
| `bio` | Plain-text bio |
| `bioHtml` | Raw bio HTML |
| `avatar` | Profile image URL |
| `coverImage` | Cover/OG image URL |
| `location` | Location string |
| `emails` | Public email addresses found in the bio |
| `phones` | Public phone numbers found in the bio |
| `links` | Social platform links + custom links (`{platform, url}`) |
| `tags` | Profile tags/keywords |
| `interests` | Interest list |
| `schools` | Education entries |
| `jobs` | Work entries |
| `contactMeEnabled` | Whether the profile exposes a contact button |
| `customDomains` | Custom domains mapped to the profile |
| `themeColor` | Profile theme color |
| `premium` | Premium account flag |
| `userId` | Internal about.me user ID |
| `scrapedAt` | Timestamp of the scrape |

### Pricing / Cost estimation

How much does it cost to scrape about.me? The actor uses **CheerioCrawler** (plain HTTP, no browser), so it is very cheap to run — roughly **1 compute unit per ~1,000 profiles**. A run of 100 profiles typically costs a fraction of a compute unit. Free Apify accounts get a capped preview of 10 profiles per run.

### Tips or Advanced options

- **Discovery mode**: enable `discoverFromSitemap` to pull profiles from about.me's public sitemap index — great for building fresh lead lists. Keep `maxSitemaps`/`maxSitemapProfiles` modest to control run cost.
- **Emails & phones**: these are extracted from the public bio text via regex. Profiles that don't publish contact details in their bio will return empty arrays — that's expected, not an error.
- **Proxy**: the default `AUTO` proxy group works fine for about.me. If you ever see blocks at scale, switch to `BUYPROXIES94952` or `StaticUS3`.

### FAQ, disclaimers, and support

- **Is scraping about.me legal?** This actor only extracts publicly visible profile data. Always respect about.me's Terms of Service, applicable laws (e.g. GDPR), and use the data responsibly.
- **Limitations**: about.me does not expose raw emails/phones for most profiles — contact is usually via a form. The actor extracts whatever contact details are publicly posted in the bio.
- **Support**: found a bug or want a custom feature? Open an issue on the actor's Issues tab, or contact us for a custom solution.

# Actor input Schema

## `profileUrls` (type: `array`):

List of about.me profile handles or full URLs, e.g. "alexandriadolan" or "https://about.me/alexandriadolan".

## `discoverFromSitemap` (type: `boolean`):

Automatically discover profile URLs from about.me's public sitemap index (bounded by the two limits below).

## `maxSitemaps` (type: `integer`):

How many per-user sitemap files to scan when discovery is enabled.

## `maxSitemapProfiles` (type: `integer`):

Maximum number of profile URLs to collect from sitemaps.

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

Maximum number of profiles to scrape in one run.

## `maxConcurrency` (type: `integer`):

Number of concurrent requests.

## `useApifyProxy` (type: `boolean`):

Route requests through the Apify proxy to avoid IP bans.

## `proxyGroup` (type: `string`):

Apify proxy group to use.

## Actor input object example

```json
{
  "profileUrls": [
    "alexandriadolan",
    "shawnmichaelburns"
  ],
  "discoverFromSitemap": false,
  "maxSitemaps": 20,
  "maxSitemapProfiles": 200,
  "maxItems": 100,
  "maxConcurrency": 5,
  "useApifyProxy": true,
  "proxyGroup": "AUTO"
}
```

# Actor output Schema

## `results` (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 = {
    "profileUrls": [
        "alexandriadolan",
        "shawnmichaelburns"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ahmed_jasarevic/aboutme-profile-scraper").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 = { "profileUrls": [
        "alexandriadolan",
        "shawnmichaelburns",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("ahmed_jasarevic/aboutme-profile-scraper").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 '{
  "profileUrls": [
    "alexandriadolan",
    "shawnmichaelburns"
  ]
}' |
apify call ahmed_jasarevic/aboutme-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ahmed_jasarevic/aboutme-profile-scraper"
        }
    }
}

```

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/An57ZULmTeCZWO3H6/builds/OVWZ85eJd47mfZxq5/openapi.json