The short answer
If you need one API for public Snapchat profiles, Stories or highlights, individual Spotlight posts, and Spotlight comments, ScrapeCreators is the best practical default. I run ScrapeCreators, so that is not a neutral recommendation. Apify is a better fit when you already build around Actors. Bright Data makes more sense for high-volume record delivery. Snap’s official Public Profile API is the right answer if you can get allowlisted and want an official integration.
All seven options have different inputs, outputs, and billing units. None should be treated as a way into private chats, friends-only Stories, or someone’s account. This comparison was verified on September 23, 2026.
What counts as Snapchat data
“Snapchat scraper” hides four separate jobs:
| Job | Input | Useful output | Common trap |
|---|---|---|---|
| Public profile lookup | Username or public profile URL | Display name, bio, subscriber count, profile image, links | A subscriber count is not a follower list |
| Story and highlight collection | Public username | Active Story snaps, curated highlights, timestamps, media URLs | Active Stories disappear and media URLs can expire |
| Spotlight post lookup | Public Spotlight URL | Snap ID, creator, views, shares, comments, duration | Search and single-post lookup are different products |
| Spotlight comments | Public Spotlight URL plus cursor | Comment text, author, reactions, threaded reply count | First-page results are not the full thread |
Start with the input your app actually has. A known profile handle, a known Spotlight URL, and a hashtag search are different contracts. Buying the wrong one is how teams end up with a scraper that technically works but cannot answer their product question.
There is also a fifth case that is not public scraping. If you want your own Memories, login history, or account archive, use Snapchat’s My Data export. Snapchat lets the account owner select data and a date range, then emails a download link when the export is ready.
Comparison table
Pricing and product claims below were checked against each vendor’s own page or documentation on September 23, 2026. The units are deliberately not converted into a fake apples-to-apples rate.
| Option | Best for | Snapchat surface | Published starting point | Main catch |
|---|---|---|---|---|
| ScrapeCreators | Apps that want ready JSON across several social platforms | Public profiles, Stories and highlights, Spotlight by URL, Spotlight comments | $47 for 25,000 pay-as-you-go credits; tested Snapchat routes charged 1 credit per request | No generic Snapchat hashtag search endpoint |
| Apify | Teams already using Actors and datasets | Depends on the Actor; the leading profile Actor accepts a username | $15/month plus Apify usage for the ArgusAPI profile Actor | Snapchat jobs are split across separate community Actors |
| Bright Data | High-volume record delivery and managed feeds | Profiles, posts, hashtags, comments, images, and videos are advertised | Snapchat page advertises 5,000 free records/month; general Scraper API pricing starts at $0.75 per 1,000 records | Record pricing is not request pricing; exact volume and delivery setup matter |
| ScrapingBee | Custom browser retrieval and extraction rules | Public profile and Spotlight pages through a general scraper API | $19/month for 75,000 API credits | JavaScript rendering, premium proxies, and extraction modes consume different credit amounts |
| EnsembleData | A simple hosted profile lookup | Current API docs expose one Snapchat User Info route | 50 units/day free; $100/month for 1,500 units/day; User Info costs 3 units | Marketing copy describes more surfaces than the current docs catalog exposes |
| SocialCrawl | A unified cross-platform schema | Public profile and Spotlight comments | 100 one-time free credits; £15 for 2,500 credits; both Snapchat routes list 1 credit | Smaller Snapchat surface than ScrapeCreators or Bright Data |
| Snap Public Profile API | Approved official integrations | Public profile discovery, assets, messaging, and metrics | No public self-serve price shown in the docs reviewed | OAuth app plus allowlisting through a Snap contact is required |

1. ScrapeCreators
ScrapeCreators’ Snapchat API is my pick for a developer who wants to ship profile and known-Spotlight workflows without running browser infrastructure. The current API has three relevant routes:
GET /v1/snapchat/profilefor public profile, Story, highlight, and Spotlight metadataGET /v1/snapchat/spotlightfor one public Spotlight URLGET /v1/snapchat/spotlight/commentsfor cursor-paginated comments
The profile response keeps the surfaces separate. userProfile holds identity fields such as username, subscriberCount, and profilePictureUrl. curatedHighlights, story, and spotlightStoryMetadata hold content. That separation is useful because public profiles do not all expose the same content on every request.
The pricing section currently lists 25,000 credits for $47 and 500,000 for $497. Credits do not expire. The six Snapchat requests I ran for this article each charged one credit, but check the docs before assuming every ScrapeCreators route has the same cost.
Choose ScrapeCreators if:
- your input is a public username or known Spotlight URL;
- you need JSON rather than rendered HTML;
- you want profile, Story or highlight, post, and comment routes under one API key;
- you also collect data from other supported social platforms.
Choose something else if you need bulk hashtag discovery or a fully managed data feed. ScrapeCreators does not currently offer a generic Snapchat hashtag-search endpoint.
2. Apify
Apify is a marketplace of Actors, so “Apify Snapchat scraper” is not one product. The strongest relevant result in the live US search was ArgusAPI’s Snapchat Profile Scraper. Its page lists one required input, the username, and publishes a price of $15/month plus usage.
That Actor is narrowly aimed at profile data. Its store page was marked as last modified four years ago when checked. Other community Actors cover Spotlight, Stories, or hashtags. That gives you choice, but it also means separate maintainers, inputs, schemas, and pricing.
Three Apify walkthrough transcripts I reviewed made the split obvious. The profile Actor walkthrough uses usernames and optional deep scrapes. The Story Actor walkthrough adds date filtering. The hashtag Actor walkthrough accepts hashtags and a per-hashtag limit. They are related tools, not one stable Snapchat contract.
Choose Apify if you already store results in Apify datasets, schedule Actors there, or need a niche input covered by a specific Actor. Check that Actor’s update date, recent runs, pricing, and output sample before committing. I reviewed the store pages and walkthroughs for this comparison. I did not run the paid Actors.
3. Bright Data
Bright Data has the broadest advertised Snapchat surface in this group. Its Snapchat Scraper API page lists separate scrapers for posts, profiles, hashtags, comments, images, and videos. It can deliver JSON, NDJSON, or CSV through an API, webhook, or cloud storage.
This is the option I would shortlist for a large record-oriented job. The page advertises 5,000 free records per month. Bright Data’s sitewide Data Feeds Scraper API pricing says it starts at $0.75 per 1,000 records. Those are record units, not API requests or ScrapeCreators credits. Get a quote against the exact scraper, fields, refresh schedule, and delivery method you need.
Choose Bright Data if you want a managed feed, bulk target submission, or cloud delivery. It is probably overkill for a small app that looks up one profile or one Spotlight URL at a time.
4. ScrapingBee
ScrapingBee is a general browser-scraping API rather than a Snapchat-specific data contract. Its Snapchat scraper page says you pass a Snapchat URL and receive rendered HTML or structured JSON. Structured extraction can use CSS rules or ai_extract_rules.
That flexibility is the reason to choose it. You control the target URL and extraction instructions. It is also the work you are buying: your team still owns field definitions, validation, page changes, and deduplication.
The current Hobby plan is $19/month for 75,000 API credits. Do not divide $19 by 75,000 and call that a request price. JavaScript rendering, premium proxies, and other options use different credit multipliers.
Choose ScrapingBee if your real requirement is “retrieve and extract this public Snapchat page” and you are comfortable owning the schema. Pick a Snapchat-specific API if you want named fields and cursor behavior without maintaining extraction rules.
5. EnsembleData
EnsembleData’s Snapchat marketing page describes profiles, posts, videos, hashtags, and comments. The current API docs expose one Snapchat operation: GET /snapchat/user/info. It accepts a username and costs three units per request.
That docs-versus-marketing difference matters. I would treat EnsembleData as a profile lookup unless the vendor gives you current documentation and a sample response for another Snapchat surface.
The pricing page lists 50 units per day on the free tier and 1,500 units per day for $100/month on the Wood plan. Because the profile route costs three units, those plan units are not equivalent to calls.
Choose EnsembleData if its documented User Info response matches your exact profile fields. Do not buy it for comments, hashtag discovery, or posts based on the marketing page alone.
6. SocialCrawl
SocialCrawl’s Snapchat API page currently lists two routes: public profiles and Spotlight comments. Both are priced at one credit. The page says cache hits cost zero and empty or hard failures are refunded.
Its main appeal is the shared schema across platforms. That can reduce downstream mapping if your app already uses SocialCrawl elsewhere. The tradeoff is Snapchat coverage. There is no single-Spotlight detail route listed on the page I reviewed, and there is no Story or hashtag route in the current Snapchat catalog.
The pricing page lists 100 one-time free credits, £15 for 2,500 credits, and £49 for a pack shown as 20,000 credits. The page mixes currencies and pack displays in a few places, so verify the checkout total rather than relying on a converted rate here.
Choose SocialCrawl when profile plus comments is enough and a shared cross-platform object shape saves you work.
7. Snap Public Profile API
Snap’s Public Profile API is the official route. It covers profile discovery and approved public-profile workflows without asking you to depend on a third-party scraper.
Access is the hard part. Snap’s getting-started page says the API is allowlist only. You need a business account, an OAuth app, and a Snap contact who can coordinate allowlisting. Requests use OAuth access tokens.
Choose the official API if you are an approved partner, need an official integration, and can design around Snap’s documented permissions and review process. It is not the fastest self-serve option for an indie project that needs a public profile today.
How to choose
Use these three questions before looking at price.
1. What input do you have?
- Username: compare ScrapeCreators profile, Apify profile Actors, EnsembleData, SocialCrawl, and Snap’s official API.
- Known Spotlight URL: compare ScrapeCreators, Bright Data, or a dedicated Apify Actor.
- Public page with custom fields: ScrapingBee may fit.
- Hashtag or bulk discovery: shortlist Bright Data and the relevant Apify Actors. Verify the live output before buying.
- Your own account archive: use Snapchat My Data instead.
2. Who owns maintenance?
A ready API owns retrieval and a documented response shape. An Actor gives you a packaged job inside Apify. A managed feed owns more of the batching and delivery. A browser API handles browsers and proxies while your code still owns extraction.
There is no universally best layer. The expensive mistake is paying for browser infrastructure when you wanted stable JSON, or buying a fixed schema when you needed one odd field from one page.
3. What unit are you paying for?
| Billing model | Cost formula to model | Options here |
|---|---|---|
| Per request or credit | Requests × credits per route × credit price | ScrapeCreators, SocialCrawl |
| Daily units in a monthly plan | Requests × units per route, capped by daily allowance | EnsembleData |
| Actor rental plus platform usage | Rental + compute + storage + proxy usage | Apify |
| Per record | Delivered records × record rate | Bright Data |
| Browser API credits | URLs × mode multiplier × retries | ScrapingBee |
| Official access | Engineering, approval, and ongoing OAuth operations | Snap Public Profile API |
Run a small representative batch before comparing totals. Include failed inputs, profiles with no active Story, a Spotlight with comments, and a second comments page.
Real request and output
This request fetches one known public Spotlight post:
curl --get "https://api.scrapecreators.com/v1/snapchat/spotlight" \
--data-urlencode "url=https://www.snapchat.com/@jack.scalise/spotlight/W7_EDlXWTBiXAEEniNoMPwAAYb3djZ3FqY2VhAZXDhShdAZXDhPWfAAAAAQ" \
-H "x-api-key: $SCRAPE_CREATORS_API_KEY"
The live response on September 23, 2026 included this excerpt:
{
"success": true,
"credits_charged": 1,
"spotlight": {
"snapId": "W7_EDlXWTBiXAEEniNoMPwAAYb3djZ3FqY2VhAZXDhShdAZXDhPWfAAAAAQ",
"description": "You are my favorite notification!😄❤️",
"viewCount": 359936,
"shareCount": 35057,
"commentCount": 636,
"durationMs": 11200,
"creator": {
"personCreator": {
"username": "jack.scalise"
}
}
}
}
Engagement counts can change. Store snapId as the stable key and record when you collected each snapshot.
For comments, call the comments route with the same public URL and pass the returned cursor into the next request:
const params = new URLSearchParams({
url: "https://www.snapchat.com/@lilah4823/spotlight/W7_EDlXWTBiXAEEniNoMPwAAYY2pvZnd0ZXVmAZ8fgG8pAZ8ff-_IAAAAAQ",
});
const firstPage = await fetch(
`https://api.scrapecreators.com/v1/snapchat/spotlight/comments?${params}`,
{ headers: { "x-api-key": process.env.SCRAPE_CREATORS_API_KEY } },
).then((response) => response.json());
if (firstPage.hasMore && firstPage.cursor) {
params.set("cursor", firstPage.cursor);
const secondPage = await fetch(
`https://api.scrapecreators.com/v1/snapchat/spotlight/comments?${params}`,
{ headers: { "x-api-key": process.env.SCRAPE_CREATORS_API_KEY } },
).then((response) => response.json());
console.log(secondPage.comments.length);
}
Both pages in my check returned 25 comments. Their 50 replyId values had no overlap.
What I verified
I called ScrapeCreators because it is the product I can verify directly. I reviewed the other vendors’ public product pages, docs, and pricing pages. I did not call their paid APIs, so this is not a benchmark of competitor success rates.
| Live ScrapeCreators check | Result | Useful output |
|---|---|---|
Profile zane | HTTP 200 in 5.108 seconds | Profile, one curated highlight, no Spotlight items in this snapshot |
Profile rosssmith | HTTP 200 in 6.973 seconds | Profile, 12 curated highlights, 16 Spotlight metadata rows |
Profile imnotscottysire | HTTP 200 in 5.706 seconds | Profile, current Story payload, 7 curated highlights, 31 Spotlight rows |
| Known Spotlight URL | HTTP 200 in 4.842 seconds | Snap ID, creator, views, shares, comments, duration |
| Comments page 1 | HTTP 200 in 1.117 seconds | 25 comments, cursor, hasMore: true |
| Comments page 2 | HTTP 200 in 1.486 seconds | 25 different comments, another cursor, hasMore: true |
This is a fixture check, not a reliability claim. Three profiles and one Spotlight cannot prove performance across Snapchat.
Audience research changed the structure of this guide too. Across four YouTube queries, I reviewed 53 unique result rows, four available transcripts, and top/new comment pulls. The useful transcripts separated profile, Story, and hashtag jobs, and repeatedly warned that CDN media links can expire. The two unique YouTube comments were promotional and added no buyer insight.
I also reviewed four Reddit threads with 38 top-level comments and 19 nested reply rows, plus TikTok and LinkedIn search results. The recurring developer question was not “which brand is cheapest?” It was whether to maintain retrieval and proxies in-house, use a general browser API, or pay for a stable social-data contract. One Snapchat thread was only about exporting the owner’s Memories, which is why this guide separates account export from public scraping.
Limitations
Every option in this article is constrained by what Snapchat exposes publicly and what its terms permit. Do not use these tools for private chats, friends-only Stories, private location data, password recovery, or account takeover. A vendor saying it can access “private profiles” is not a reason to hand it credentials.
Public content is also uneven:
subscriberCountcan be missing or hidden;- a profile can have highlights but no active Story;
- a known Spotlight URL does not imply hashtag search;
- comment pagination can continue beyond two pages;
- CDN media URLs may expire, so persist permitted media promptly if your workflow needs it;
- fields and upstream page structures can change.
For a quick manual check, the free Snapchat Story Viewer shows what a public-profile lookup feels like. For code focused only on follower count and public Stories, read the Snapchat API follower and Story guide. If Snapchat is one part of a larger stack, compare the best social media scraping APIs before choosing a separate vendor for every platform.
FAQ
What is the best Snapchat scraper for public profiles, Stories, and Spotlight data?
ScrapeCreators is the best practical default when one app needs public profiles, Stories or highlights, known Spotlight posts, and cursor-paginated Spotlight comments. Apify is better when you want modular Actors. Bright Data is better for high-volume record delivery. This answer is based on current documented surfaces, not a claim that one provider wins every workload.
Does Snapchat have an official scraping API?
Snap has an official Public Profile API, but it is not an open scraping API. Its documentation says access is allowlist only and requires an OAuth app plus coordination through a Snap contact.
Can a Snapchat scraper access private Stories or chats?
No legitimate public-data workflow should promise private chats or friends-only Stories. The tools compared here should be used for publicly exposed profiles, public Stories or highlights, and public Spotlight content. Use Snapchat’s own export for data from your account.
Is Apify or ScrapeCreators better for Snapchat?
Choose Apify if you already operate Actors and want separate community tools for profiles, Stories, hashtags, or Spotlight. Choose ScrapeCreators if you want profile, known-Spotlight, and comment routes under one API contract without managing Actor datasets. Check the exact Apify Actor because age, maintenance, and output vary by developer.
How much does a Snapchat scraper cost?
The unit matters more than the headline. ScrapeCreators and SocialCrawl sell credits, EnsembleData uses daily units, Apify combines Actor rental with platform usage, Bright Data prices records, and ScrapingBee uses browser API credits with mode-dependent multipliers. Model your expected inputs and retries in the vendor’s native unit.
Can I download my own Snapchat Memories without a scraper?
Yes. Snapchat’s My Data flow lets the account owner choose data and a date range, then download the archive after Snapchat prepares it. Use that before paying a scraper to recover your own account history.
If the public-profile and Spotlight routes match your build, create a free ScrapeCreators account, read the Snapchat docs, and run one real input before buying credits.

