Snapchat Popular Accounts Scraper By Snapcode & Bio Links

Snapchat Scraper — Extract Profiles, Snapcodes & Bio Links

Snapchat Popular Accounts Scraper By Snapcode & Bio Links pulls public Snapchat profiles by search keyword or direct URL, then builds two things a plain profile scrape skips: a ready-to-use snapcode contact card (image URL plus a canonical add-link) and a bio-mined list of the creator's other-platform handles. Every profile — subscriber count, verified badge, category, website, and more — returns as typed, normalized JSON, no HTML or CSS selectors to parse. Provide a keyword or a profile URL, and you'll have contact-ready, LLM-ready data in your dataset.

🧭 What is Snapchat Popular Accounts Scraper By Snapcode & Bio Links?

Snapchat Popular Accounts Scraper By Snapcode & Bio Links is an Apify Actor that discovers public Snapchat profiles by keyword (via Snapchat's Explore and Spotlight sections) or by direct profile/explore URL, then scrapes each one for its full public profile data plus two enrichments: a structured snapcode contact card and a mined list of cross-platform handles found in the bio text. No Snapchat account or login is required — every page it fetches is publicly accessible.

• 🔍 Scrape public Snapchat profiles by keyword or profile URL
• 📇 Build a snapcode contact card per profile — image URL + canonical add-link
• 🔎 Mine bios for cross-platform handles (Instagram, TikTok, YouTube, Twitter/X, Facebook)
• ⬇️ Export results as JSON, CSV, or Excel
• 🌐 No proxy management required — the Actor escalates its own connection if Snapchat pushes back

📊 What data does Snapchat Popular Accounts Scraper By Snapcode & Bio Links collect?

The Actor returns three distinct data shapes in every scraped row — the profile itself, a snapcode contact card, and bio-mined cross-platform mentions:

Data Type	Key Fields	JSON Field Names
Profiles	username, display name, bio, subscriber count, verified badge, category/subcategory	username, displayName, bio, subscriberCount, isVerified, profileInfo.category, profileInfo.subcategory
Snapcode Contact Cards	snapcode (QR) image URL, canonical add-link	snapcodeImageUrl, snapcodeCard.snapcodeImageUrl, snapcodeCard.addUrl
Bio-Mined Cross-Platform Mentions	platform, handle, matched raw text	bioMentions[].platform, bioMentions[].handle, bioMentions[].rawText

Need more Snapchat data?

Looking for Spotlight video content instead of profile data? API-Empire's Snapchat Spotlight Scraper (Language & Topic Filters) pulls Spotlight videos filtered by language and topic. If you already know which creators you care about and just want a focused profile-and-stats pull, Snapchat User Spotlight Scraper: Creator Profile Stats covers that narrower case.

🆚 How does Snapchat Popular Accounts Scraper By Snapcode & Bio Links differ from the official Snapchat API?

Snapchat's own Public Profile API returns metadata and stats for a profile you already know — it does not let you discover new profiles by keyword, and it requires an OAuth-authenticated business/organization account. Snapchat Popular Accounts Scraper By Snapcode & Bio Links starts from a keyword or URL, needs no account, and adds two fields the official API doesn't return at all.

Feature	Snapchat Public Profile API	Snapchat Popular Accounts Scraper By Snapcode & Bio Links
Profile discovery by keyword	Not supported — you must already know the profile ID or organization ID	Searches Explore and Spotlight by keyword, merges and deduplicates results
Authentication	OAuth access token, snapchat-profile-api scope, organization access	No Snapchat account or login required
Snapcode / QR image URL	Not returned	Returned as a dedicated snapcodeCard object (image URL + add-link)
Cross-platform handles mentioned in bio text	Not returned (only a structured website field)	Regex-mined into a bioMentions array
Entity coverage	Public Profile metadata only	Profiles, snapcode contact cards, and bio-mined mentions in one row
Setup time	Register an app, request API access, obtain an OAuth token	Provide a keyword or URL and start the run

As observed on developers.snap.com/marketing-api/Public-Profile-API, checked 2026-08-15.

The official API is the right choice when you already run these profiles through your own Snapchat organization and only need publish stats. This Actor is the right choice when you need to discover new public profiles by keyword and want the snapcode and bio-mention data the official API doesn't expose.

💼 Why do developers and teams scrape Snapchat popular accounts?

📈 For marketers and lead-gen teams

Search a niche keyword like fashion or fitness and get back every matching public profile with subscriber count, category, and a ready snapcode contact card — the image URL and add-link a landing page or CRM record can use immediately, with no manual screenshotting of a QR code. Pair that with bioMentions to also pull the same creator's Instagram or TikTok handle whenever they've written it into their bio, so one keyword search builds a cross-platform outreach list instead of a single-platform one.

🤖 For AI engineers and agent builders

Point an agent at targetKeywords and every profile comes back as typed JSON — username, bio, subscriberCount, snapcodeCard, bioMentions — with no HTML to parse before it reaches an LLM context window or a RAG index. Because searchKeyword and scrapedAt travel with every row, an agent can re-run the same keyword on a schedule and diff results without writing its own change-detection logic on top of raw markup.

🔬 For researchers and analysts

profileInfo.category and profileInfo.subcategory let you segment a keyword's results by account type — creator, business, brand — without opening a single profile page by hand. Because only public profile data is returned, building a keyword-based sample of a niche's popular accounts for content-trend or creator-demographic research doesn't require touching anything behind a login.

🛠️ For developers building data products

The Actor's output schema — nested profileInfo, flags, and metadata objects plus the snapcodeCard and bioMentions fields — stays fixed across runs, so a product built on top of it (a contact-card generator, a creator directory, a lead-scoring pipeline) can integrate against stable field names through the Apify API or a schedule, instead of maintaining its own HTML scraper.

🧩 How to scrape Snapchat popular accounts (step by step)

1. Open the Actor's page on the Apify Console (found on the Apify Store).
2. Provide at least one of Target keywords (targetKeywords) or Profile or explore URLs (profileUrls) — the Actor needs one of the two and exits with no results if both are left empty.
3. Optionally set Max contact cards per search (contactExportLimit) and Fetch concurrency (fetchConcurrency), and toggle Include snapcode contact card / Mine bio for cross-platform mentions.
4. Click Start. Results save to the Output/Dataset tab in real time as each profile is scraped.
5. Download the dataset as JSON, CSV, or Excel, or pull it through the Apify API.

What to do when Snapchat changes its page structure

The Actor is maintained, and its output schema — field names and nesting — stays stable on your end even when Snapchat's underlying page markup changes. No action is required on your integration when that happens.

⬇️ Input

All parameters are optional in the schema, but the Actor needs at least one of Target keywords or Profile or explore URLs (or their legacy aliases) to have anything to scrape.

Parameter	Required	Type	Description	Example Value
targetKeywords	No	array (string list)	Search keywords to discover profiles (e.g. fashion, beauty, fitness). Each keyword is searched across Snapchat's Explore and Spotlight sections and results are merged and deduplicated. No schema default; prefill ["fashion"].	["fashion"]
profileUrls	No	array (URL list)	Direct Snapchat profile URLs (snapchat.com/add/username) or explore/spotlight listing URLs. Use with or without target keywords. No schema default; prefill [].	["https://www.snapchat.com/add/example_creator"]
contactExportLimit	No	integer	Cap on how many profiles (and their contact cards) to export per keyword or URL. Minimum 1, maximum 200. No schema default; prefill 10 — the Actor's code applies 10 if the field is omitted.	10
fetchConcurrency	No	integer	How many profiles to fetch at the same time. Minimum 1, maximum 20. No schema default; prefill 10 — the Actor's code applies 10 if the field is omitted.	10
includeSnapcodeCard	No	boolean	Emit a structured snapcodeCard object per profile: the profile's real snapcode image URL plus a canonical add-link. URL + metadata only — the snapcode image itself is never downloaded or stored. Default true.	true
mineBioMentions	No	boolean	Scan each profile's bio text for @handle mentions and other-platform URLs (Instagram, TikTok, YouTube, Twitter/X, Facebook) into a bioMentions array. Default true.	true
keywords	No	array (string list)	Legacy alias for targetKeywords. Only read if targetKeywords is omitted. No schema default; prefill [].	[]
startUrls	No	array (URL list)	Legacy alias for profileUrls. Only read if profileUrls is omitted. No schema default; prefill [].	[]
maxProfilesPerUrl	No	integer	Legacy alias for contactExportLimit. Minimum 1, maximum 200. Default 10.	10
maxConcurrentProfiles	No	integer	Legacy alias for fetchConcurrency. Minimum 1, maximum 20. Default 10.	10
proxyConfiguration	No	object (proxy editor)	Proxy settings for requests to Snapchat. No schema default; prefill {"useApifyProxy": false} — direct connection by default. The Actor automatically escalates its own connection if Snapchat pushes back, so a run keeps going even with this left off.	{"useApifyProxy": false}

Example input (all parameters shown):

{
  "targetKeywords": ["fashion"],
  "profileUrls": [],
  "contactExportLimit": 10,
  "fetchConcurrency": 10,
  "includeSnapcodeCard": true,
  "mineBioMentions": true,
  "keywords": [],
  "startUrls": [],
  "maxProfilesPerUrl": 10,
  "maxConcurrentProfiles": 10,
  "proxyConfiguration": { "useApifyProxy": false }
}

Common pitfall: leaving targetKeywords, profileUrls, and their legacy aliases all empty. The Actor checks for at least one non-empty value and exits immediately with a warning if none is set — no rows are pushed, and nothing is charged.

⬆️ Output

Every result is a typed, normalized JSON object — one row per scraped profile, pushed to the dataset as soon as it's fetched and charged on the row_result event. Profiles that can't be fetched or parsed are skipped, not pushed as empty or error rows, so you are only ever charged for a profile that actually landed in your dataset. Download results as JSON, CSV, Excel, or via the Apify API.

Scraped profile

{
  "id": "123456789",
  "username": "example_creator",
  "displayName": "Example Creator",
  "bio": "Fashion + lifestyle. @example_ig on Instagram",
  "subscriberCount": 192700,
  "isVerified": false,
  "location": {
    "country": "",
    "state": "",
    "displayAddress": "New York, NY"
  },
  "profileInfo": {
    "logoUrl": "https://cf-st.sc-cdn.net/...",
    "heroImageUrl": "https://cf-st.sc-cdn.net/...",
    "createdAt": "2021-03-11T00:00:00.000Z",
    "lastUpdatedAt": "2026-08-01T00:00:00.000Z",
    "category": "people",
    "subcategory": "creator",
    "tier": 0
  },
  "flags": {
    "isLensCreator": false,
    "hasLenses": false,
    "hasStory": true,
    "hasCuratedHighlights": false,
    "hasSpotlightHighlights": true,
    "hasHighlights": true,
    "isBrandProfile": false,
    "isSnapchatPlusSubscriber": false
  },
  "metadata": {
    "accountId": "123456789",
    "organizationId": "",
    "profileIconColor": "#FFFC00"
  },
  "websiteUrl": "",
  "sameAsLinks": [],
  "snapcodeImageUrl": "https://app.snapchat.com/web/deeplink/snapcode?data=...",
  "snapcodeCard": {
    "snapcodeImageUrl": "https://app.snapchat.com/web/deeplink/snapcode?data=...",
    "addUrl": "https://www.snapchat.com/add/example_creator",
    "username": "example_creator"
  },
  "bioMentions": [
    { "platform": "instagram", "handle": "example_ig", "rawText": "@example_ig on Instagram" }
  ],
  "searchKeyword": "fashion",
  "scrapedAt": "2026-08-15T10:00:00.000Z",
  "sourceSections": ["explore"],
  "sourceProfileUrl": "https://www.snapchat.com/add/example_creator"
}

snapcodeCard is null when includeSnapcodeCard is set to false. bioMentions is an empty array when mineBioMentions is false, or when no mentions are found in the bio text. snapcodeImageUrl at the top level is always populated with the profile's real snapcode URL regardless of the includeSnapcodeCard toggle — the toggle only controls whether the separate snapcodeCard object is also built. Fields inside location, websiteUrl, sameAsLinks, and metadata.organizationId are only populated when Snapchat's own page actually carries that data — they are left empty rather than guessed.

🔍 How does Snapchat Popular Accounts Scraper By Snapcode & Bio Links compare to other Snapchat scrapers?

Feature	Snapchat Popular Accounts Scraper By Snapcode & Bio Links	Generic alternative
Output format	Typed, normalized JSON	Often raw HTML requiring a custom parser
Snapcode contact card	✅ Dedicated snapcodeCard object (image URL + add-link)	❌ Not typically extracted
Bio-mined cross-platform handles	✅ Regex-mined into a structured bioMentions array	❌ Not typically extracted
Keyword discovery	Searches Explore + Spotlight, merges & deduplicates	Often a single source, or manual URL lists only
Legacy input compatibility	Accepts the base actor's original field names as aliases	N/A

If you're building an AI agent or RAG pipeline, the output format row is the decision-maker — parsing HTML inside an agent loop is a reliability failure mode, not a feature.

📈 How many results can you scrape with Snapchat Popular Accounts Scraper By Snapcode & Bio Links?

Each keyword or profile/explore URL is capped at 200 profiles per run via contactExportLimit (minimum 1, maximum 200) — a limit enforced by the Actor itself, not a documented Snapchat platform rate limit. There's no cap on how many keywords or URLs you can queue in one input; the Actor works through them one at a time, so total output scales with how many you provide. Within each keyword or URL, up to fetchConcurrency profiles (maximum 20) are fetched in parallel. Actual profile count also depends on how many profile links Snapchat's own Explore/Spotlight listing returns for that keyword — if fewer than your cap are found, that's what you get.

🔌 Integrate Snapchat Popular Accounts Scraper By Snapcode & Bio Links and automate your workflow

Snapchat Popular Accounts Scraper By Snapcode & Bio Links works with any language or tool that can send an HTTP request.

REST API integration

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")

run = client.actor(
    "<YOUR_APIFY_USERNAME>/snapchat-popular-accounts-scraper-by-snapcode-and-bio-links"
).call(run_input={
    "targetKeywords": ["fashion"],
    "contactExportLimit": 10,
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["username"], item["snapcodeCard"]["addUrl"])

Works in Python, Node.js, Go, Ruby, cURL.

Automation platforms (n8n, Make)

n8n's official Apify node and Make's official Apify app can both call this Actor by its ID (snapchat-popular-accounts-scraper-by-snapcode-and-bio-links) and pass the same input JSON shown above — trigger a run on a schedule, then feed the returned dataset items (including snapcodeCard.addUrl and bioMentions) into a CRM, spreadsheet, or downstream workflow step with no custom scraping code.

⚖️ Is it legal to scrape Snapchat popular accounts?

Yes — scraping publicly accessible Snapchat profile pages is generally legal; the Actor only reads pages Snapchat serves without a login. Snapchat Popular Accounts Scraper By Snapcode & Bio Links returns only publicly available profile data: no private accounts, no login-gated content. Because the output includes personal data — username, display name, bio, and any cross-platform handles a creator has written into their own bio — collecting and storing it at scale falls under GDPR and CCPA, and you need a lawful basis for storing and using it, particularly for outreach or marketing use. Consult legal counsel for commercial use cases involving bulk personal data.

❓ Frequently asked questions

Does the scraper work without a Snapchat account?

Yes. The Actor fetches public profile and listing pages directly over HTTP with no login, session cookie, or Snapchat account required.

How often is the scraped data updated?

Live, per run. Each run fetches the current Explore/Spotlight listing and profile pages at request time — nothing is served from a cache.

What happens if a profile is deleted, private, or unreachable?

That profile is skipped, not returned as an empty or error row. If a profile or listing page can't be fetched or parsed (removed, blocked, or a soft-block interstitial page), the Actor logs a warning and moves to the next URL or keyword. No placeholder row is pushed, so you're not charged for it.

Can I scrape private Snapchat accounts?

No. Only publicly accessible profile and listing pages are fetched. Private accounts and any content requiring a Snapchat login are out of scope.

How am I charged for using this Actor?

Pay-per-event, charged on the row_result event — one charge per profile actually saved to the dataset. Skipped or unreachable profiles are never pushed, so they're never charged.

Does this Actor work for AI agent workflows and LLM pipelines?

Yes. It's callable as an HTTP endpoint through the Apify API by any agent framework, and every response is typed JSON — no HTML or selectors to parse before passing a profile to an LLM.

How does it handle Snapchat's anti-bot defenses?

It starts with a direct connection, then escalates one step at a time — to Apify Proxy, then to residential Apify Proxy — whenever a response comes back blocked (HTTP 403 or 429), errors out, or is implausibly short for a real listing/profile page. It retries up to 3 times at the top connection level before giving up on that URL.

How does it compare to other Snapchat scrapers?

See the comparison table above — the two things a generic Snapchat scraper typically doesn't return are the snapcodeCard contact-card object and the bio-mined bioMentions array; this Actor returns both alongside the full profile row.

Does it return data in a format LLMs can use directly?

Yes. Typed, normalized JSON with stable field names — pass it straight into an LLM context window, index it into a vector store, or route it through an agent tool without a parsing step.

Can I use this Actor without managing proxies?

Yes. By default it connects directly and only escalates to Apify Proxy if Snapchat blocks or rate-limits the request — nothing to configure. An optional proxyConfiguration input lets you start with Apify Proxy from the first request instead.

What happens when Snapchat changes its page structure or blocks the scraper?

The Actor is maintained, and the output schema stays stable on your end — field names and types don't change because of a Snapchat markup change. No specific turnaround time is published.

💬 Your feedback

Found a bug, or need a field this Actor doesn't return yet? We want to know. Open an issue from this Actor's page on Apify Console (Issues tab), or reach out through Apify's support contact — feedback shapes what gets fixed and built next.