Pinterest Email Scraper

Pinterest Email Scraper

Observe email addresses that account owners visibly publish on public Pinterest profile pages. The actor returns a source-bound profile observation for each reachable profile and a separate public-email row for each address found in visible profile content. It never guesses addresses, signs in, reads private messages, or treats an access challenge as data.

Input

Field	Type	Default	Description
startUrls	array	Pinterest's official profile	One to 20 public HTTPS Pinterest profile URLs. Localized Pinterest subdomains are supported.
maxPages	integer	10	Maximum profiles to process, from 1 to 20.
timeoutSecs	integer	30	Per-profile request timeout, from 5 to 120 seconds.
proxyConfiguration	object	direct	Optional Apify or custom proxy transport.

Only HTTPS Pinterest profile paths such as https://www.pinterest.com/pinterest/ or https://in.pinterest.com/example/ are accepted. Pin, search, login, arbitrary website, credential-bearing, and private-network URLs are rejected before a request is made.

{
  "startUrls": [
    "https://www.pinterest.com/pinterest/",
    "https://in.pinterest.com/example/"
  ],
  "maxPages": 2,
  "timeoutSecs": 30,
  "proxyConfiguration": { "useApifyProxy": false }
}

If a proxy is explicitly requested but cannot be created, the run fails rather than silently sending traffic directly. Proxy credentials are handled by the transport layer and are never logged or stored in dataset rows.

Collection behavior

The actor fetches public Pinterest HTML and embedded public profile state. It selects the user object whose username exactly matches the requested profile URL, avoiding unrelated board owners and route metadata. Emails are accepted only from rendered page content, the page title/description, and the matching public profile's name or bio. Repeated appearances of the same address on one page are deduplicated.

Output

Normal rows use entityType values pinterest_profile and pinterest_public_email. Profile rows include the public profile ID, username, name, bio, website, follower count, canonical profile URL, email count, and source URL. Public-email rows include the owning profile ID, username, normalized address, emailSource: "public-profile-content", profile URL, and source URL.

{
  "entityType": "pinterest_public_email",
  "id": "424605208526455283:public@example.com",
  "profileId": "424605208526455283",
  "username": "example",
  "email": "public@example.com",
  "emailSource": "public-profile-content",
  "profileUrl": "https://www.pinterest.com/example/",
  "sourceUrl": "https://www.pinterest.com/example/",
  "scrapedAt": "2026-09-08T00:00:00.000Z"
}

Blocked access, redirects away from Pinterest, non-HTML responses, missing public profile state, and profiles without a published email are represented honestly. Diagnostics contain only the requested Pinterest URL, sanitized error, stable code, and timestamp:

{
  "url": "https://www.pinterest.com/example/",
  "error": "The public profile page was reachable, but no email address was present in visible page content.",
  "errorCode": "SOURCE_UNAVAILABLE",
  "scrapedAt": "2026-09-08T00:00:00.000Z"
}

A reachable profile without an address still produces a pinterest_profile row with emailsFound: 0; the no-email observation is not counted as an email. The OUTPUT_SUMMARY key-value record contains run status, normal/diagnostic counts, profile/email counts, proxy state, source mode, and completion time. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Run locally

npm install
npm run check
npm test
apify run --purge --input-file qa-inputs/pinterest-email-scraper/local-primary.json
npm run validate

Use a batch-specific APIFY_LOCAL_STORAGE_DIR when validating alongside other local runs. The actor uses bounded pages, timeouts, sequential requests, strict URL validation, minimal logging, and explicit diagnostics.

Responsible use and limitations

Collect and use contact data only for lawful purposes with an appropriate legal basis. Honor opt-outs, anti-spam laws, privacy obligations, and Pinterest's terms. Profile owners can edit or remove public content, and Pinterest can change its HTML. Private content, messages, emails, and hidden user data are not collected.