# Snapchat Profile & Story Scraper (`s-r/snapchat-profiles`) Actor

Read public Snapchat profiles: subscriber count, bio, website and verification, plus each Spotlight and Story highlight with its snap count, thumbnail and dates. Paste usernames or profile links.

- **URL**: https://apify.com/s-r/snapchat-profiles.md
- **Developed by:** [SR](https://apify.com/s-r) (community)
- **Categories:** Social media, Videos
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Snapchat Profile & Story Scraper

Read public Snapchat profiles as structured data: the account with its
subscriber count, bio, website and verification, and every Spotlight and Story
highlight with its snap count, thumbnail and dates.

Paste usernames or profile links. No login, no API key, no browser.

### Two kinds of profile, and only one of them has subscribers

Snapchat has two sorts of public account, and they carry different data. This
matters more than it sounds, because most scrapers pick one and silently return
nothing for the other.

**Creator profiles** carry a subscriber count, a bio, a website, a profile
picture and a verification badge. `mrbeast` is one: 1,463,000 subscribers.
`kyliejenner` is another: 29,581,900.

**Ordinary accounts** carry a username, a display name and a snapcode. That is
all there is. `teamsnapchat` is one.

Both are returned. `is_creator` says which arrived, and `subscriber_count` is
**empty** rather than `0` on an ordinary account, because it does not have one.
Zero would be a claim about its audience. The run summary counts the two kinds
apart, so a run of fifty tells you how many were creators without you having to
check row by row.

### Stories and Spotlight

Each account's highlights come back one row per story:

- `story_type` — `spotlight` or `story`
- `title` where the creator set one, `thumbnail_url`, `story_id`
- `snap_count` — how many snaps are in it
- `posted_at` and `latest_snap_at` — the first and last snap in the story, so a
  long-running highlight shows its span rather than a single date
- `media_url` and `first_snap_id`
- the account fields on every row, so a multi-account run is one table

Four accounts returned **64 stories containing 1,186 snaps** in under ten
seconds.

Turn **Include stories** off to read only the accounts. That is one request per
account and the cheap way to track subscriber counts on a schedule.

### Empty highlights are dropped, and reported

A profile lists highlights that have nothing behind them: a story id with an
empty snap list and every other field null. Published, those are rows that look
like stories and contain nothing.

They are dropped. And when an account's own profile says it has highlights but
none of them carried snaps, the run reports it by name in
`accountsClaimingHighlightsButServingNone`. That distinction matters: an account
with no highlights and an account whose highlights were not delivered look
identical in a table of results, and only one of them is worth running again.

### Missing accounts are named

Snapchat answers a username that does not exist with a **404**, which is
unusually direct, so a bad handle is reported by name instead of quietly
returning fewer rows. A run of fifty tells you exactly which one was wrong.

### Reading the dates properly

`posted_at` is the **first** snap in a highlight and `latest_snap_at` is the
last. A creator who builds one highlight over a week and a creator who posts
seven separate ones look very different in a table sorted by date, and only the
span tells them apart.

Both are UTC. Snapchat publishes them as unix seconds, and the same field
arrives as a bare number on one snap and wrapped in an object on the next, which
is the sort of inconsistency that turns a sort into nonsense if it is not
unwrapped first. It is.

### What this does not cover

**No private accounts, no friends, no messages.** This reads what a public
profile page shows to anyone who visits it, and nothing else exists to read
without an account.

**No Lenses.** They sit on the same page and are a different kind of object with
different fields; mixing them into a story table would give you rows with half
the columns empty.

**No snap contents.** A snap is identified, not transcribed or downloaded. You
get its id, its media URL and its timestamp.

**No search.** Snapchat has no public way to search accounts or stories by
keyword, so you name the accounts you care about.

### What people use this for

**Creator research.** Subscriber count next to how many stories an account
actually publishes separates a large account from an active one. The two are
often not the same account.

**Campaign tracking.** Run the accounts in a campaign on a schedule with stories
on, and `posted_at` gives you publishing cadence per creator over time.

**Audience benchmarking.** Subscriber counts across a set of creators in one
table, refreshed whenever you like, at one request each.

**Content research.** `snap_count` and the date span show how creators actually
structure a story: a fifteen-snap highlight built over a day is a different
thing from a single snap, and the counts make that visible without opening any
of them.

### Notes

Only public profiles are readable. A private account has no public profile page
and is reported as not found.

Subscriber counts move, and stories expire. A run is a snapshot, which is why
every story carries its own dates.

Snaps are identified rather than downloaded: `media_url` points at Snapchat's
own CDN and the media itself is not part of the output.

The account's Lenses are visible on the same page but are not returned here;
they are a different kind of object and would need their own columns.

# Actor input Schema

## `profiles` (type: `array`):

Usernames or profile links, one per line. @name, a bare name and a snapchat.com/add link all work.

## `include_stories` (type: `boolean`):

Read each account's Spotlight and Story highlights. Turn this off to read only the accounts, which is the cheap way to track subscriber counts on a schedule.

## `max_accounts` (type: `integer`):

Stop after this many accounts, counted after duplicates are removed.

## `attempts` (type: `integer`):

How often to retry an account whose page comes back without its payload. Every account measured succeeded on the first try.

## `region` (type: `string`):

Two-letter country code the request should appear to come from.

## Actor input object example

```json
{
  "profiles": [
    "kyliejenner"
  ],
  "include_stories": true,
  "max_accounts": 25,
  "attempts": 3,
  "region": "gb"
}
```

# Actor output Schema

## `stories` (type: `string`):

One row per story highlight.

## `summary` (type: `string`):

Accounts read with their subscriber counts, creator and ordinary profiles counted apart, and stories and snaps returned.

## `errors` (type: `string`):

Accounts that could not be read.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "profiles": [
        "mrbeast",
        "https://www.snapchat.com/add/nba"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("s-r/snapchat-profiles").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "profiles": [
        "mrbeast",
        "https://www.snapchat.com/add/nba",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("s-r/snapchat-profiles").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "profiles": [
    "mrbeast",
    "https://www.snapchat.com/add/nba"
  ]
}' |
apify call s-r/snapchat-profiles --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,s-r/snapchat-profiles"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/uGDdGpHieus3lU9PT/builds/LvY41LIAxv5vbahCv/openapi.json