TikTok Influencer Email Finder — Creator Contacts

TikTok username in, verified business email out. This Actor pulls a creator's public profile stats, extracts contact emails from the bio, and when the bio has no email it fetches the creator's link-in-bio page (Linktree, Beacons, personal sites) and mines it for addresses and mailto: links. Every found email is MX-verified via DNS so you know the domain can actually receive mail before you write to it.

Built for influencer outreach, creator sourcing, and TikTok Shop seller campaigns: you get the profile data to qualify the creator and the contact to reach them — in one run, one dataset.

What you get per creator

Field	Description
username, nickname, verified	Identity
followers, following, likes, videos	Qualification stats
bio, bioLink	Bio text and link-in-bio URL
email	Best contact email found (bio first, then link-in-bio page)
emailSource	bio or bio-link
mxValid, mxRecords	DNS MX verification result for the email domain (null when not checked or the lookup timed out)
allEmails	Every address found, if more than one
rowType	lead (email found) or profile (no email)

Pricing that matches value

You pay the full lead price only when an email is actually found (lead-with-email). Profiles delivered without an email are free: no result charge is emitted, including identity-only fallback results. Failed profiles are never charged and never pollute your dataset — they go to the run SUMMARY instead.

How it works

1. Profile extraction — three-tier fallback (profile page → embed surface → oEmbed) so a blocked tier doesn't kill the run. Fresh residential proxy session per attempt, US exits by default (TikTok serves full profiles reliably only to US IPs).
2. Bio email scan — strict pattern match with junk filtering.
3. Link-in-bio crawl — one page fetch of the creator's declared link; extracts visible emails and mailto: targets.
4. MX verification — DNS lookup per unique domain (cached across the run).

Up to three profiles are processed in parallel and rows keep your input order. Request timeouts shrink as the run's timeout approaches, so a big list never ends in a timed-out run: anything not finished in time is listed in the SUMMARY record's pendingUsernames (ready to re-run), and the run still succeeds with everything it found.

Quick start

{
  "usernames": ["creator1", "creator2", "creator3"]
}

Or paste profile URLs into urls. That's it — defaults handle the rest.