How to get public Snapchat stories and highlights as structured data
12 Nov 2026 · benthepythondev
If you follow a set of public Snapchat creators and want their story snaps in a spreadsheet or a database, copying links by hand gets old fast. The Snapchat Stories Scraper reads the public profile page for each username you give it. It saves one row per snap, covering both the active story (when one is live) and the curated highlights pinned to the profile. You don't need a Snapchat login or an API key.
What you get
Each row is one snap. The fields fall into four groups.
Where the snap came from
source_type:active_storyfor the short-lived current story, orcurated_highlightfor snaps the creator pinned to their profile.story_id,highlight_id,snap_id: the public identifiers, when Snapchat exposes them.record_id: always filled. If Snapchat leaves out a snap ID (common for highlights), the Actor builds a deterministic key from the story, the snap index and the media URL, so the same snap gets the same ID on every run.snap_indexandrank: the snap's position inside its story or highlight.
The highlight or story itself
story_title,story_subtitle,story_emoji,story_thumbnail_url,story_type.
The media
media_type(for examplevideo),media_url,preview_url, and, when present,overlay_url,attachment_urlandtranscript_url.published_at: the timestamp for the snap.- Other per-snap fields such as
snap_title,snap_subtitles,is_sponsored,latitudeandlongitude. Snapchat often leaves these empty.
The creator
creator_username,creator_name,creator_url,creator_profile_picture_url,creator_subscriber_count,creator_badge,creator_category,creator_subcategory,creator_bio.
Every row also carries source_url and scraped_at.
A real example
Here is a trimmed excerpt from a real run on the nasa profile. It returned snaps from a curated highlight called "Moon Joy". The long CDN URLs are shortened here.
[
{
"record_id": "7c399b992daf7f5506298049f704d812",
"source_type": "curated_highlight",
"story_id": "",
"highlight_id": "ddf02468-ae16-4fc6-b1bc-bde7e1e22218",
"story_title": "Moon Joy",
"snap_id": "",
"snap_index": 0,
"media_type": "video",
"media_url": "https://cf-st.sc-cdn.net/d/wAUDrJs74QBAl504N3DhT.1322?mo=...",
"preview_url": "https://cf-st.sc-cdn.net/d/wAUDrJs74QBAl504N3DhT.410?mo=...",
"transcript_url": null,
"published_at": "2026-04-10T15:32:54+00:00",
"creator_username": "nasa",
"creator_name": "NASA",
"creator_subscriber_count": 755400,
"creator_category": "public-profile-category-v3-business-group",
"creator_subcategory": "public-profile-subcategory-v3-government-org",
"creator_bio": "Explore the universe and discover our home planet with official NASA snaps.",
"rank": 1,
"source_url": "https://www.snapchat.com/@nasa",
"scraped_at": "2026-10-07T18:19:06.116405+00:00"
},
{
"record_id": "468bb6044507c9b19e9ea5becfced356",
"source_type": "curated_highlight",
"highlight_id": "ddf02468-ae16-4fc6-b1bc-bde7e1e22218",
"story_title": "Moon Joy",
"snap_index": 1,
"media_type": "video",
"media_url": "https://cf-st.sc-cdn.net/d/h2ao1JvA4lER8PICU97Gc.1322?mo=...",
"published_at": "2026-04-10T15:32:54+00:00",
"creator_username": "nasa",
"rank": 2
}
]
In this run story_id and snap_id came back as empty strings, so record_id is the field to use as a stable key.
What people use it for
The README lists these uses, among others:
- Watching a creator list. Run it on a schedule against a set of usernames to see which public stories are live right now.
- Spotting changes between runs. Because
record_idstays the same for the same snap, you can compare two snapshots and see which snaps were added or removed. - Building a research table. Combine snap order, timestamps, media type and creator category and bio into one table you can review.
- Passing media to your own tools. Send the image, video, preview, attachment or transcript URLs into an internal workflow, keeping ephemeral stories apart from durable highlights by filtering on
source_type.
How to run it
On Apify
Open the Actor page on Apify and give it input like this:
{
"usernames": ["nasa", "jeremy-lynch"],
"includeActiveStory": true,
"includeCuratedHighlights": true,
"maxProfiles": 10,
"maxSnapsPerProfile": 15
}
usernamesaccepts plain usernames,@handles,/add/links orsnapchat.com/@...URLs.maxProfilesandmaxSnapsPerProfileboth go from 1 to 100.- At least one of
includeActiveStoryorincludeCuratedHighlightshas to stay on.
You can export results as JSON, CSV or Excel, or pull them through the Apify API, webhooks or a scheduled run.
Open the actor Call it on RapidAPI
As an API on RapidAPI
If you'd rather call it as a plain HTTP API, it's also listed on RapidAPI.
Honest limits
- Public data only. The Actor reads what an anonymous visitor can see on a public profile. It doesn't sign in, it can't see friends-only snaps, and it doesn't get around audience controls. It also won't message, follow or post.
- No full archive. You get what the profile shows at the moment of the run: the active story, if there is one, plus the curated highlights. Older stories that have expired are gone.
- Active stories may be empty. Many profiles have no live story at a given time. The default
nasainput is there because its highlights give you rows even when nothing is live. - The snap limit is shared.
maxSnapsPerProfilecounts active story and highlight snaps together, and active story snaps are handled first. With a low limit, highlights can get cut. - Lots of nulls. Fields like
snap_title,is_sponsored, location andtranscript_urlare only filled when Snapchat provides them. In the example above they were all null. - Media links are CDN URLs. The README describes
media_urlandpreview_urlas current public Snapchat CDN resources. If you need the files later, download them yourself rather than counting on the link staying the same.
Affiliate if you still need an Apify account: apify.com/?fpr=qolupv. I may earn a commission; the price you pay does not change.