Snapchat Profile Scraper By Topic Search

Snapchat Topic Search Scraper — Creators, Clips & Topics

Snapchat Topic Search Scraper turns a subject — skincare, food challenge, crypto — into a ranked list of Snapchat creators posting about it, pulled from Snapchat's public Explore and Topic pages and expanded through Snapchat's own related-topic graph. Every discovered handle is enriched with its full public profile, Spotlight clips, and GARM brand-safety signals, returned as typed, normalized JSON — no HTML, no selectors, no manual parsing. Skip discovery and it scrapes known handles directly instead. After reading this, you'll know which inputs to set and which JSON keys to expect.

---

What is Snapchat Topic Search Scraper?

Snapchat Topic Search Scraper is an Apify Actor that discovers Snapchat creators by subject instead of by handle, then runs every discovered account through a full profile scraper. Give it one or more topics — skincare, crypto, food challenge — and it queries Snapchat's own /explore/<query> and /topic/<slug> pages, harvests the creators Snapchat itself surfaces for that subject, optionally follows Snapchat's related-topic links for a wider set, and returns each creator's public profile, Spotlight clips, and brand-safety data. No Snapchat account, login, or cookies are required — every page it fetches is publicly served.

• 🔎 Discover creators by topic — search Snapchat's Explore and Topic surfaces instead of starting from a handle list.
• 🌱 Follow Snapchat's own related-topic graph — expand one query into dozens of adjacent subjects, up to two hops deep.
• 👤 Full profile enrichment — every discovered (or supplied) handle gets the complete public profile, Spotlight clip list, and highlight data.
• 🛡️ GARM brand-safety signals — the brand-safety block Snapchat attaches to Spotlight clips, if you need it for creator vetting.
• 📤 Export as JSON, CSV, XML, or Excel — standard Apify dataset export, no extra step.

This is the topic/keyword-driven entry point into Snapchat creator data — if you already have a list of usernames and just want profile detail with no discovery step, the urls input on this same Actor runs that classic single-handle flow directly, without touching the Explore/Topic pipeline at all.

---

What data does Snapchat Topic Search Scraper collect?

Each dataset row covers four kinds of data pulled together into one creator record: the public profile, the creator's Spotlight clips, the topic/discovery context that surfaced them, and (optionally) brand-safety classification.

Data Type	Key Fields	JSON Field Names
Creator profiles	username, display name, bio, subscriber count, verification, account type	profile.username, profile.displayName, profile.bio, profile.subscriberCount, profile.isVerified, profile.profileType
Spotlight clips	play/share/comment counts, resolved title, post date, media and transcript URLs	data.spotlight[].playsFixed, data.spotlight[].sharesFixed, data.spotlight[].resolvedTitle, data.spotlight[].postedAt, data.spotlight[].mediaUrl
Topic & discovery context	which query/topic surfaced the creator, how deep the related-topic crawl went, topic snap volume	discovery.sourceType, discovery.sourceTopic, discovery.depth, topicVolume[].topic, topicVolume[].numSnaps
Brand-safety signals	GARM classification, Petra brand-safe flag, brand-friendliness score, public status	brandSafety.garmBrandSafety, brandSafety.isPetraBrandSafe, brandSafety.brandFriendliness, brandSafety.isPublic

Need more Snapchat data?

This Actor already covers both ends of Snapchat creator research inside one run: point searchQueries at a subject to discover new handles, or drop known usernames into urls for direct profile pulls with no discovery step. Both paths go through the same profile parser, so a discovered creator and a hand-supplied one return an identical profile and data.spotlight shape — you don't need a second Snapchat Actor just to switch between "find creators" and "look one up."

---

Why not build this yourself?

Snapchat has no public API for creator discovery, topic search, or public-profile lookup — Snap Kit and the Snapchat Marketing API cover login, sharing, and ad management, not reading public creator or Spotlight data. Anyone who wants this data has to scrape the same pages a browser renders, and Snapchat doesn't keep that surface consistent.

The two discovery pages don't even share a data format. /explore/<query> still ships a classic <script id="__NEXT_DATA__"> payload you can json.loads() directly. /topic/<slug> has migrated to React Server Components and ships zero __NEXT_DATA__ — creator handles have to be regex-harvested out of the raw /@<user>/spotlight/ links in the HTML, and the related-topics list has to be pulled out of an escaped RSC flight string with a second pair of regexes. A scraper built against one page format silently breaks on the other.

Underneath both pages, Snapchat wraps most scalar values in a protobuf-style {"value": ...} envelope that has to be unwrapped field by field, ships engagement counters as strings with -1 as an explicit "not available" sentinel, and glues affiliate query junk (&af_web_dp=...) onto Spotlight IDs in a way that breaks naive substring matching against the highlights payload. creatorInfo.followerCount on Explore's spotlightCardMap is served as the literal string "0" on every card regardless of the creator's real following — a dead field worth knowing about before you build a pipeline around it.

Maintaining a scraper against this means tracking two independently-changing page formats, a proxy-escalation path for 403/429 responses, and retry logic with backoff — before you've written a single line of discovery ranking. This Actor absorbs that maintenance; you send a topic or a handle and get back a stable JSON schema.

---

Why do developers and teams scrape Snapchat by topic?

Searching Snapchat by subject rather than by handle serves a handful of recurring jobs, each pulling on a different slice of the output.

For marketers and brand teams

Building a creator shortlist for a campaign usually starts with a category, not a name. Run searchQueries: ["skincare"] with includeBrandSafety: true, and every candidate arrives with its topSpotlight.viewCount, topSpotlight.caption, and the brandSafety.garmBrandSafety classification from the exact clip that made them show up for that topic — enough to screen a shortlist for brand fit before a single outreach message goes out.

For AI engineers and agent builders

An agent tasked with "find me Snapchat creators talking about crypto" can call this Actor with a searchQueries array, get back typed JSON rows keyed by username, profile, and discovery.sourceType, and feed them straight into a tool-calling loop or a vector store without an HTML-parsing step in between. discovery.depth and discovery.sourceTopic give the agent a traceable reason for why each result was surfaced.

For researchers and analysts

topicVolume[].numSnaps reports how many Snaps Snapchat itself attributes to a topic at query time, and the related-topic graph (discovery.sourceType: "relatedTopic", discovery.sourceTopic) exposes what Snapchat considers adjacent to a subject — both are public, first-party signals useful for mapping how a topic is trending on the platform without any private API access.

For developers building data products

Scheduled runs against a fixed topic list, with proxyConfiguration.apifyProxyCountry pinned for a consistent exit geo, produce a repeatable creator feed suitable for a lead-generation product, a discovery dashboard, or a periodic monitoring pipeline — the dataset schema doesn't change between runs, so downstream code stays stable.

---

How to scrape Snapchat by topic (step by step)

1. Open Snapchat Topic Search Scraper on the Apify Store and click Try for free (or Run, if you already have it saved).
2. Fill in searchQueries with one or more subjects (e.g. ["skincare", "food challenge"]), urls with known handles, or both — at least one of the two must be non-empty.
3. Set the discovery controls that matter for your run: maxProfilesPerQuery for the per-topic cap, expandRelatedTopics (plus relatedTopicDepth and maxRelatedTopicsPerQuery) if you want a wider net, and minSpotlightViews if you only want Explore-ranked creators.
4. Click Start and watch the run log — it reports Explore/Topic hit counts and how many unique creators were found per query as it goes.
5. Open the Dataset tab when the run finishes and export as JSON, CSV, XML, or Excel, or pull it via the Apify API.

What to do when Snapchat changes its structure

Snapchat has already changed the underlying format once — /topic/<slug> moved from the classic __NEXT_DATA__ payload to React Server Components with no __NEXT_DATA__ at all — and this Actor's output schema didn't change when that happened; only the internal harvesting method did. The Actor is maintained against Snapchat's current page structure, and the field names and shapes documented below are what you should expect on every run. No specific turnaround time is promised for future breakage.

---

⬇️ Input

All fields are optional at the schema level, but the run does nothing useful unless searchQueries or urls (or both) contain at least one entry — with neither set, the Actor logs a warning and exits after writing an empty run summary, producing zero dataset rows and no error.

Parameter	Required	Type	Default	Constraints
searchQueries	No	array of strings	[] (prefilled with ["skincare"])	Subjects to discover creators for. Each query is looked up on https://www.snapchat.com/explore/<query> and https://www.snapchat.com/topic/<slug>.
expandRelatedTopics	No	boolean	false	Crawls a capped number of Snapchat's own related topics per query for extra creators. Costs one extra request per related topic.
relatedTopicDepth	No	integer	1	minimum: 1, maximum: 2. 1 = only topics related to your query; 2 = also topics related to those.
maxRelatedTopicsPerQuery	No	integer	5	minimum: 0, maximum: 50. How many related-topic pages to crawl per query when expandRelatedTopics is on.
maxProfilesPerQuery	No	integer	20	minimum: 1, maximum: 500. Hard cap on discovered creators actually scraped per query, ranked by top discovered Spotlight clip views.
minSpotlightViews	No	integer	0	minimum: 0. Only scrape creators whose discovered Spotlight clip has at least this many views. 0 disables the filter.
includeBrandSafety	No	boolean	true	Adds the GARM brand-safety block Snapchat ships on discovered Spotlight clips.
urls	No	array of strings	[] (prefilled with ["djkhaled305"])	Snapchat usernames or full profile URLs to scrape directly, skipping discovery for those handles.
maxRetries	No	integer	3	minimum: 1, maximum: 10. How many times a failing page is retried before the row is written as a failure.
requestTimeoutSecs	No	integer	30	minimum: 5, maximum: 300. Per-request timeout in seconds.
proxyConfiguration	No	object (proxy editor)	{ "useApifyProxy": false }	Apify Proxy configuration. Uses a direct connection by default.

Example input — topic discovery:

{
  "searchQueries": ["skincare", "food challenge"],
  "expandRelatedTopics": true,
  "relatedTopicDepth": 1,
  "maxRelatedTopicsPerQuery": 5,
  "maxProfilesPerQuery": 15,
  "minSpotlightViews": 0,
  "includeBrandSafety": true,
  "urls": [],
  "maxRetries": 3,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyCountry": "US" }
}

Example input — classic mode, direct handles only:

{
  "searchQueries": [],
  "urls": ["djkhaled305", "https://www.snapchat.com/@kyliejenner"],
  "proxyConfiguration": { "useApifyProxy": false }
}

Common pitfalls: setting minSpotlightViews above 0 silently keeps only Explore-sourced creators — creators harvested from /topic/ pages carry no view-count data at all, so any positive threshold drops them regardless of how relevant they were to the query. And if you're trying to disable related-topic expansion entirely, use expandRelatedTopics: false rather than setting maxRelatedTopicsPerQuery to 0 — a 0 value there currently falls back to the field's default of 5 instead of crawling nothing.

---

⬆️ Output

Every dataset row is charged one row_result pay-per-event unit when it is pushed — including failed scrapes and unparseable input rows, which are written to the dataset but flagged with "ok": false rather than being dropped or skipped. Exact per-event pricing is set on this Actor's Apify Store pricing page. Export the dataset as JSON, CSV, XML, Excel, or via the Apify API.

The dataset's default Overview view surfaces 18 flattened columns (username, profile.displayName, profile.subscriberCount, discovery.sourceType, topSpotlight.viewCount, runGeo.country, and so on) for quick scanning in the Apify Console. The rows the Actor actually pushes carry considerably more — every field documented below.

Discovered creator (successful scrape)

{
  "ok": true,
  "username": "djkhaled305",
  "url": "https://www.snapchat.com/@djkhaled305",
  "attempt": 1,
  "proxyMode": "apify-selected",
  "rowType": "discovered",
  "profile": {
    "profileType": "publicProfile",
    "username": "djkhaled305",
    "displayName": "DJ Khaled",
    "title": "DJ Khaled",
    "bio": "ANOTHER ONE",
    "subscriberCount": 8412345,
    "location": null,
    "websiteUrl": "https://djkhaled.com",
    "profilePictureUrl": "https://cf-st.sc-cdn.net/...",
    "snapcodeImageUrl": "https://app.snapchat.com/web/deeplink/snapcode?username=djkhaled305&type=SVG",
    "isVerified": true,
    "hasCuratedHighlights": true,
    "hasSpotlightHighlights": true,
    "createdAt": "2016-02-11T00:00:00Z",
    "lastUpdatedAt": "2026-07-01T00:00:00Z",
    "pageType": "PUBLIC_PROFILE"
  },
  "data": {
    "search": "https://www.snapchat.com/@djkhaled305",
    "spotlight": [
      {
        "spotlightId": "W7_EDlXWQfmZAEEniN76dQ",
        "link": "/@djkhaled305/spotlight/W7_EDlXWQfmZAEEniN76dQ&af_web_dp=...",
        "thumbnailSrc": "https://cf-st.sc-cdn.net/...",
        "spotlightTitle": "",
        "plays": 214000,
        "shares": 812,
        "comments": 340,
        "isSponsored": null,
        "timestampInSec": null,
        "mediaUrl": "https://cf-st.sc-cdn.net/...",
        "transcriptUrl": null,
        "spotlightIdClean": "W7_EDlXWQfmZAEEniN76dQ",
        "absoluteLink": "https://www.snapchat.com/@djkhaled305/spotlight/W7_EDlXWQfmZAEEniN76dQ",
        "playsFixed": 214000,
        "sharesFixed": 812,
        "resolvedTitle": "Another one in the studio",
        "postedAt": "2026-06-14T18:22:05Z",
        "transcriptUrl_fixed": "https://cf-st.sc-cdn.net/transcript/...",
        "transcriptUrls": ["https://cf-st.sc-cdn.net/transcript/..."],
        "timestampsInSec": [1749925325]
      }
    ],
    "userProfile": { "publicProfileInfo": { "...": "raw Snapchat payload, unwrapped scalars" } },
    "spotlightHighlights": [ { "...": "raw, unprocessed highlight objects as Snapchat serves them" } ]
  },
  "discovery": {
    "sourceQuery": "skincare",
    "sourceType": "explore",
    "sourceTopic": null,
    "sourceTopicUrl": "https://www.snapchat.com/explore/skincare",
    "depth": 0,
    "discoveredAt": "2026-07-25T09:12:44Z"
  },
  "creatorPreview": {
    "userId": "8f2c1a...",
    "displayName": "DJ Khaled",
    "snapproTier": "PARTNER"
  },
  "topSpotlight": {
    "storyId": "W7_EDlXWQfmZAEEniN76dQ",
    "rawSnapId": "9f0e21...",
    "spotlightUrl": "https://www.snapchat.com/@djkhaled305/spotlight/W7_EDlXWQfmZAEEniN76dQ",
    "caption": "skincare routine before the show",
    "playCountText": "214K",
    "viewCount": 214000,
    "shareCount": 812,
    "boostCount": 44,
    "replyCount": 12,
    "postedAtMs": 1749925325000,
    "postedAt": "2026-06-14T18:22:05Z",
    "thumbnailUrl": "https://cf-st.sc-cdn.net/..."
  },
  "brandSafety": {
    "garmBrandSafety": "SAFE",
    "isPetraBrandSafe": true,
    "brandFriendliness": "HIGH",
    "spotlightSnapStatus": "PUBLISHED",
    "isPublic": true
  },
  "topicVolume": [
    { "topic": "skincare", "numSnaps": 34844, "topicUrl": "https://www.snapchat.com/topic/skincare" }
  ],
  "runGeo": {
    "country": "US",
    "locale": "en-US",
    "isGdprCountry": false,
    "proxyMode": "apify-selected"
  }
}

Rows discovered via /topic/<slug> or the related-topic crawl carry discovery.sourceType: "topic" or "relatedTopic", and creatorPreview, topSpotlight, and brandSafety are all null on those rows — Topic pages don't ship the engagement or brand-safety data Explore does. Rows you supplied directly through urls carry "rowType": "input" and discovery filled with a static placeholder (sourceType: "input", everything else null).

Note on transcriptUrl and timestampInSec inside data.spotlight[]: these two fields are kept in the output for backward compatibility, but they match a Spotlight clip's transcript against its highlight record using the clip's raw ID — which still carries Snapchat's affiliate query suffix (&af_web_dp=...) glued onto it — so the match fails and both fields come back null on effectively every row. The corrected values are the fields sitting right next to them: spotlightIdClean (the ID with the affiliate suffix stripped), transcriptUrl_fixed / transcriptUrls (matched against the cleaned ID, across every snap in the highlight, not just the first), and postedAt / timestampsInSec (the same fix applied to the post timestamp). Use the _fixed/plural fields, not the originals, if you need transcripts or accurate post times.

Failed scrape

The data and profile keys are omitted entirely on a failed row rather than written as null — check for the key's presence, not just its value, if you're consuming this in a strict schema:

{
  "ok": false,
  "username": "some_deleted_or_blocked_handle",
  "url": "https://www.snapchat.com/@some_deleted_or_blocked_handle",
  "error": "HTTPError 404: HTTP 404 for https://www.snapchat.com/@some_deleted_or_blocked_handle",
  "attempt": 3,
  "proxyMode": "apify-residential",
  "rowType": "discovered",
  "discovery": { "sourceQuery": "crypto", "sourceType": "explore", "sourceTopic": null, "sourceTopicUrl": "https://www.snapchat.com/explore/crypto", "depth": 0, "discoveredAt": "2026-07-25T09:14:02Z" },
  "creatorPreview": { "userId": "...", "displayName": "...", "snapproTier": null },
  "topSpotlight": { "...": "as above" },
  "brandSafety": null,
  "topicVolume": [],
  "runGeo": { "country": "US", "locale": "en-US", "isGdprCountry": false, "proxyMode": "apify-residential" },
  "profile": null
}

Invalid input row

If an entry in urls can't be parsed into a username at all, a minimal row is written instead of being silently dropped:

{ "ok": false, "input": "not a snapchat url or handle @@@", "error": "Invalid Snapchat username / URL" }

Run summary (key-value store, not the dataset)

Alongside the dataset, every run writes a SUMMARY.json record to the default key-value store: total, processed, successes, fallbackToResidential (boolean), searchQueries, discoveredProfiles, and discoveryStats — a per-query breakdown of seedCreators, totalCreators, fanoutMultiple, relatedTopicsAvailable, and selected, plus run-wide exploreOk/exploreFail, topicOk/topicFail, topicPagesFetched, relatedTopicsSeen, candidatesBeforeFilter, and candidatesAfterFilter counters. Useful for auditing why a topic returned fewer creators than maxProfilesPerQuery allowed.

---

How does Snapchat Topic Search Scraper compare to other Snapchat scrapers?

Feature	Snapchat Topic Search Scraper	Generic alternative
Discovery method	Topic/keyword search via Snapchat Explore + Topic pages, with related-topic expansion	Direct username lookup only — argusapi/snapchat-profile-scraper's listing states "there is only 1 input... the Snapchat username" (checked on the Apify Store, 2026-07-25)
Entity coverage	Creator profiles, Spotlight clips, topic/related-topic graph, brand-safety block	Profile fields only, per the same listing's documented sample output
Brand-safety data	GARM classification, Petra brand-safe flag, brand-friendliness score per clip	Not documented on the compared listing
Pricing model	Pay-per-event (row_result)	Flat monthly price, per the Apify Store listing (checked 2026-07-25)
Anti-bot handling	Direct connection by default, automatic escalation to Apify RESIDENTIAL proxy on 403/429 with datacenter fallback	Not documented on the compared listing
Output format	Typed JSON, stable field names across runs	Typed JSON, nested under a json wrapper key per the compared listing's sample output

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, and both of these Actors avoid it. The discovery-method row is what actually separates a topic-search tool from a lookup tool: one starts from a subject you know, the other requires a handle you don't have yet.

---

How many creators can you discover with Snapchat Topic Search Scraper?

There's no global maxItems cap in the Actor itself. The real ceiling per query is maxProfilesPerQuery (1–500, default 20), multiplied by however many entries are in searchQueries, plus every handle you list directly in urls (unbounded array length). Related-topic expansion can surface far more candidates than that before the cap trims them — the input schema's own measurements found 258–444 related topics listed per topic page across six sampled slugs, and relatedTopicDepth: 2 compounds that further, gated by maxRelatedTopicsPerQuery (0–50 per hop).

Two filters reduce the pool before the cap applies: minSpotlightViews above 0 drops every creator sourced from a Topic page (they carry no view-count data), and duplicate handles across Explore, Topic, related-topic, and your own urls list are deduplicated by username before scraping — a creator surfaced by two different paths is only scraped once. No benchmark run numbers are published here; actual throughput depends on how many creators a given topic surfaces on Snapchat at the time you run it.

---

🔌 Integrate Snapchat Topic Search Scraper and automate your workflow

Snapchat Topic Search Scraper works with any language or tool that can send an HTTP request, since every run and every dataset sits behind the standard Apify API.

REST API integration

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")

run = client.actor("<YOUR_USERNAME>/snapchat-profile-scraper-by-topic-search").call(
    run_input={
        "searchQueries": ["skincare"],
        "maxProfilesPerQuery": 20,
        "includeBrandSafety": True,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["username"], item.get("profile", {}).get("subscriberCount"))

Works in Python, Node.js, Go, Ruby, cURL — anything that can call the Apify API with your account's API token.

Automation platforms (n8n, Make, Zapier)

The Apify platform ships official integrations for Zapier, Make, and n8n's Apify node that can start any Actor run and read its dataset without custom code. Point the integration at this Actor's ID, map searchQueries or urls to your trigger's output fields, and route the finished dataset into a spreadsheet, CRM, or downstream workflow step.

---

⚖️ Is it legal to scrape Snapchat?

Yes — scraping publicly accessible Snapchat data is legal in most jurisdictions, and this Actor only reads pages Snapchat serves without a login: /explore/<query>, /topic/<slug>, and public @<username> profile pages. No authentication, cookies, or private-account content are involved anywhere in this pipeline.

The data returned — usernames, bios, subscriber counts, locations where a creator has listed one, Spotlight clip metrics — is personal data about identifiable individuals in most cases, so GDPR and CCPA considerations apply to how you store and use it, not to the act of reading it from a public page. The Actor stamps runGeo.isGdprCountry on every row so you can flag rows originating from a GDPR-applicable exit region. Consult legal counsel before using bulk personal data from this Actor for commercial purposes, particularly outreach or profiling at scale.

---

❓ Frequently asked questions

Does Snapchat Topic Search Scraper work without a Snapchat account?

Yes. No login, cookies, or API key are used anywhere in the pipeline — every request hits a public Snapchat page (Explore, Topic, or profile) the same way an anonymous browser would.

How often is the scraped data updated?

Every run fetches Explore, Topic, and profile pages live from Snapchat at execution time. Nothing is cached between runs — two runs of the same topic minutes apart can return different view counts, different related topics, or a different creator ranking if Snapchat's own results changed.

What happens if my topic search returns zero creators?

The query is still logged in discoveryStats.queries[] with seedCreators: 0 and totalCreators: 0, but no dataset row is written for a query that surfaced nobody — a zero-result topic produces no rows and no error, not a failure row. Check the run log or SUMMARY.json for the per-query breakdown before assuming something broke.

Can I scrape private Snapchat accounts?

No. Only publicly accessible Explore results, Topic pages, and public profile pages are read. A private or non-existent account returns no usable __NEXT_DATA__ and the row for that handle is written with "ok": false.

Why did I get fewer creators than maxProfilesPerQuery allowed?

Two filters run before the cap: minSpotlightViews above 0 removes every Topic-page-sourced creator (they carry no view stats), and duplicate handles found across Explore, Topic, related topics, and your own urls are merged into one entry before scraping. If a topic simply doesn't have that many creators posting about it on Snapchat, the cap can't manufacture more.

Am I charged for failed or invalid rows?

Yes. Every row pushed to the dataset — including a scrape that failed after maxRetries attempts ("ok": false) and an unparseable entry in urls ("error": "Invalid Snapchat username / URL") — is billed under the same row_result pay-per-event unit as a successful row. There's no separate uncharged path for errors, so a malformed urls list or a run of dead handles is not free to run.

Does Snapchat Topic Search Scraper work for AI agent workflows and LLM pipelines?

Yes. It's callable as a standard HTTP/JSON endpoint through the Apify API from any agent framework — LangChain, CrewAI, or a custom tool-calling loop — and every response is typed JSON with stable field names, so no parsing step sits between the scraper and the model.

How does Snapchat Topic Search Scraper handle Snapchat's anti-bot system?

Requests go out with a Chrome TLS fingerprint via curl_cffi (falling back to plain requests if that library is unavailable), retried up to maxRetries times with exponential backoff capped at 6 seconds. The Actor starts on a direct connection by default and automatically escalates to Apify's RESIDENTIAL proxy group the moment it sees a 403, 429, or a block/timeout-shaped error; if RESIDENTIAL isn't entitled on the account or its CONNECT tunnel is refused, it degrades to a datacenter proxy group instead of failing the run outright.

How does Snapchat Topic Search Scraper compare to other Snapchat scrapers?

See the comparison table above. The short version: a direct-handle Snapchat scraper like argusapi/snapchat-profile-scraper (checked on the Apify Store, 2026-07-25) needs a username you already have; this Actor is built for the case where you have a subject instead, and it still runs the direct-handle case through urls.

Does Snapchat Topic Search Scraper return data in a format LLMs can use directly?

Yes. Typed, normalized JSON with stable field names — no HTML, no CSS selectors, no regex on your end. Pass a dataset item straight into an LLM's context window, index it into a vector store, or route it through an agent tool call.

Can I use Snapchat Topic Search Scraper without managing proxies?

Yes. The default is a direct connection with no proxy at all; if you want geo-consistent discovery — Snapchat ranks Explore and Topic results by exit-IP country — set proxyConfiguration.apifyProxyCountry explicitly and the Actor stamps the country actually used on every row as runGeo.country.

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

The Actor is maintained against Snapchat's current page structure, and its output schema stays stable on your end — field names and shapes don't change just because Snapchat's internal page format did, as already happened once when /topic/<slug> moved to React Server Components. No specific turnaround time is promised for future breakage.

---

💬 Your feedback

Found a bug, a missing field, or a Snapchat page format this Actor doesn't handle yet? Message API Empire through this Actor's Apify Store page or open a note from the Console's Issues tab on the run — reports get triaged directly against this Actor's source.