about.me Profile Scraper — Bios, Links, Emails & Contact Info

Extract professional profile data from about.me — the personal bio directory — by handle or URL: name, headline, bio, avatar, location, public emails & phones, social and custom links, tags, interests, schools and jobs — built for B2B sales prospecting, lead enrichment, recruiting and outreach teams.

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.

Main Use Cases

• B2B sales prospecting — enrich lead lists with bios, locations, social links and public contact details.
• Lead enrichment — add professional profile data to existing CRM records to qualify and personalize outreach.
• Recruiting & talent sourcing — pull candidates' professional summaries, interests, education and social profiles.
• Networking & outreach teams — collect public emails, phones and social links for personalized outreach.
• Building a personal-contact / people database — discover profiles from about.me's public sitemap and aggregate records at scale.

Build a People & Contact Database Without a Public API

about.me does not expose a general-purpose public API for querying profile or contact data. The actor reads each public profile page and turns it into a clean, structured record — including publicly posted emails, phone numbers, social links, bio, interests, schools and jobs — without you building and maintaining your own scraper.

How It Works

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, or pull them via the Apify API.

The actor uses plain HTTP (CheerioCrawler) with no browser per page, so it is cheap: roughly 1 compute unit per ~1,000 profiles. A run of 100 profiles typically costs a fraction of a compute unit.

Input

Field	Type	Required	Default	Notes
profileUrls	array	No	[]	about.me handles or full profile URLs, e.g. ["alexandriadolan"] or ["https://about.me/alexandriadolan"].
discoverFromSitemap	boolean	No	false	Auto-discover profile URLs from about.me's public sitemap index (bounded by the limits below).
maxSitemaps	integer	No	20	How many per-user sitemap files to scan when discovery is on (max 240).
maxSitemapProfiles	integer	No	200	Max profile URLs collected from sitemaps (max 5000).
maxItems	integer	No	100	Max profiles to scrape per run (max 10000).
maxConcurrency	integer	No	5	Number of concurrent requests (max 20).
useApifyProxy	boolean	No	true	Route requests through the Apify proxy to avoid IP bans.
proxyGroup	string	No	AUTO	Proxy group: AUTO, BUYPROXIES94952 (datacenter), StaticUS3 (static).

Output

Each dataset item is one profile. Simplified example:

{
  "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"
}

Field reference

Field	Description
url	Canonical profile URL
handle	about.me username
name	Full name
headline	Roles/headline shown on the profile
bio / bioHtml	Plain-text bio and raw bio HTML
avatar / coverImage	Profile image and cover/OG image URLs
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

Download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Example Input

{
  "profileUrls": ["alexandriadolan", "shawnmichaelburns"],
  "maxItems": 100,
  "maxConcurrency": 5,
  "useApifyProxy": true,
  "proxyGroup": "AUTO"
}

Example Output

{
  "url": "https://about.me/shawnmichaelburns",
  "handle": "shawnmichaelburns",
  "name": "Shawn Burns",
  "headline": "Volunteer, Musician",
  "location": "Hollywood, FL, United States",
  "bio": "I am a graduate of the University of Central Florida currently living in Hollywood, Florida...",
  "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": [],
  "scrapedAt": "2026-08-18T12:00:00.000Z"
}

Integrations & Automation

Export results as JSON/CSV/Excel from the dataset, or call the actor programmatically via the Apify API and integrate with CRMs, outreach tools or enrichment pipelines. For lead and outreach teams, schedule recurring runs (e.g. weekly or monthly) to keep bios, locations and public contact details fresh in your people database.

Related Actors

• Fresh LinkedIn Profile Data — extract public LinkedIn profile data for the broader professional-profile / people-data cluster.
• Buy Me a Coffee Creator Scraper — scrape creator profiles, social links and public emails for outreach and lead-building across another people-data source.

FAQ

Why use this actor instead of the official about.me API?

about.me does not expose a general-purpose public API for querying profile or contact data. This actor provides that data by reading public profile pages — without you building and maintaining your own scraper.

What are alternatives to this actor / to the about.me API?

For professional profile data across another people-data source, the Fresh LinkedIn Profile Data actor covers LinkedIn profiles. about.me data is often combined with LinkedIn and creator-platform data for richer people databases.

How do I get about.me emails and phone numbers for outreach?

The actor extracts public emails and phones directly from the public bio text via regex. about.me does not expose raw emails/phones for most profiles (contact usually goes through a form), so emails and phones are empty unless a profile publishes them — that's expected, not an error.

How do I build a lead list from about.me for B2B outreach?

Pass a list of handles/URLs, or enable discoverFromSitemap to pull profiles from about.me's public sitemap index. Set maxItems to cap the run, then export the deduplicated records to CSV/Excel/JSON and merge them into your CRM or outreach tool.

How do I find candidate profiles for recruiting / talent sourcing?

Use handles/URLs for known candidates, or enable sitemap discovery for volume. Each record includes headline, bio, interests, schools and jobs, plus linked social profiles, to qualify candidates from public about.me pages.

How do I export about.me profiles to CSV?

After a run, open the Dataset tab and export as CSV, Excel or JSON, or pull the dataset via the Apify API (api.apify.com/v2/datasets/{datasetId}/items).

How does about.me data compare to LinkedIn profile data?

about.me pages are self-authored personal bios (headline, bio, links, interests) and often carry public contact details, while LinkedIn is the standard professional network. The two complement each other for people data — use this actor for about.me pages and a LinkedIn scraper for LinkedIn profiles.

SEO Keywords

about.me profile scraper, about.me data, about.me api, about.me api alternative, about.me email scraper, about.me contact scraper, people search data, professional profile data, personal bio data, b2b lead enrichment, b2b sales prospecting, lead enrichment tool, recruiting talent sourcing, candidate sourcing, candidate profiles, networking outreach emails, social links and contact info scraping, people database, scrape email and phone from profiles, about.me alternative

For AI Agents & LLM Apps

Purpose: returns one dataset record per about.me profile containing name, headline, bio, location, public emails/phones, social and custom links, interests, schools, jobs and flags.

Minimal working input:

{ "profileUrls": ["alexandriadolan"], "maxItems": 10 }

Variant input (discovery mode):

{ "discoverFromSitemap": true, "maxSitemaps": 20, "maxSitemapProfiles": 200, "maxItems": 100 }

Output fields: url, handle, name, headline, bio, bioHtml, avatar, coverImage, location, emails, phones, links, tags, interests, schools, jobs, contactMeEnabled, customDomains, themeColor, premium, userId, scrapedAt.

Behaviors an agent should know:

• If profileUrls is provided, those exact profiles are scraped; discoverFromSitemap adds sitemap discovery on top (bounded by maxSitemaps/maxSitemapProfiles).
• maxItems caps profiles per run (default 100); maxConcurrency caps parallel requests (default 5).
• emails and phones are extracted from public bio text only — they are frequently empty because most about.me pages route contact through a form rather than publishing raw details.
• Proxy is on by default (useApifyProxy: true, group AUTO); switch group to BUYPROXIES94952/StaticUS3 only if you hit blocks at scale.

Billing: pay-per-event — ~$0.005 per result (dataset record) plus a small per-run start event.

Legal & Compliance Disclaimer

This actor is an independent tool and is not affiliated with, endorsed by, or sponsored by about.me. It only accesses publicly available profile pages and extracts information publicly posted there (including emails and phones only when a profile publishes them); it does not bypass logins, solve CAPTCHAs, or access private data. Users are responsible for their own compliance with about.me's Terms of Service and with applicable data-protection law (e.g. GDPR / CCPA) when processing profiles of individuals. Any emails, phone numbers or other contact data collected must not be used for unsolicited commercial outreach in violation of applicable law (e.g. CAN-SPAM, GDPR, TCPA). This is not legal advice.