How to Get Snapchat Follower Counts, Stories, and Spotlights

A Snapchat follower count API can return subscriberCount for a public profile, plus public Stories, saved highlights, and Spotlight metadata when Snapchat exposes them. It cannot give you private Stories, messages, or a complete list of follower usernames.

If you own the account and only need its current count, use Snapchat’s app. If you are building profile monitoring or creator research, ScrapeCreators’ GET /v1/snapchat/profile route reads public profile data without requiring the creator to complete Snap OAuth. Snap’s official Public Profile API is the better fit for approved partners that need authorized analytics or content management. Its access was still allowlist-only when checked on September 5, 2026.

I run ScrapeCreators, so this guide is not a neutral review of my own API. I will show what the endpoint returned in live calls, where the public-data route is useful, and where it is the wrong tool.

Choose the right way to check Snapchat followers

The phrase “Snapchat follower count” hides three different jobs. Pick the route that matches yours.

What you need	Best route	Login or approval	What you get	Main limitation
Check the count on your own account	Snapchat app and Public Profile Insights	Your Snapchat login	Your displayed count and owner-only insights that Snapchat makes available	Manual, not a data feed for other profiles
Read public profile fields for research or monitoring	ScrapeCreators Snapchat profile endpoint	ScrapeCreators API key	subscriberCount, bio, category, public content, Spotlight metadata, and related public fields	Public data only; no full follower list
Manage content or use authorized partner analytics	Snap Public Profile API	Snap business account, OAuth, allowlisting, and access token	Official public and authorized partner workflows	Longer setup and access is not automatic
Look up one public Story without writing code	Free Snapchat Story Viewer	No Snapchat login	Current public profile, Story, highlight, and Spotlight preview	A manual lookup, not scheduled monitoring

The current Google results mix Snapchat’s support pages, one-off checker tools, tutorials, Reddit discussions, and APIs. That split is useful. People asking “where is my count?” need the app instructions. Developers asking for an API need an honest field map and a working request.

What subscriberCount actually means

A Snapchat follower is not the same thing as a friend.

Snapchat’s own support documentation describes a friend as a two-way relationship and a follower as a one-way relationship attached to a Public Profile. That distinction showed up repeatedly in the public questions reviewed for this update. People expected their follower count to match their friends list, then assumed one of the numbers was broken.

Use these definitions in your product:

• subscriberCount is the public profile’s follower or subscriber count when exposed.
• Friends are mutual connections. This endpoint does not return them.
• Following describes accounts the person follows. It is not their audience.
• Story viewers watched one Story. They are not automatically followers.
• Snap Score is an activity score, not audience size.

A public count also does not imply a public follower directory. One widely viewed YouTube tutorial correctly found the count, then disappointed viewers by suggesting that friends and Quick Add could reveal who every follower was. The comments were blunt because the title promised more than the app provides. Do not repeat that mistake in an API product.

If you are checking your own count in the app, Snapchat’s follower-count visibility instructions point to your Public Profile and its edit controls. A current Tech Life Unity walkthrough also shows the practical difference between the rounded profile-card number and the exact count available through Insights for the profile owner.

What a public profile API can and cannot return

The useful boundary is public profile data, not “everything about a Snapchat user.”

Data	Public profile API	Notes
Username, display name, bio, category, website, public profile image	Yes	Values depend on what the profile publishes
Public subscriberCount	Yes, when exposed	Save collection time because it changes
Current public Story flag and public Story media	Sometimes	A profile can have no active public Story at collection time
Saved public highlights	Sometimes	Availability varies by profile
Public Spotlight posts and engagement metadata	Sometimes	Views, shares, comments, descriptions, and media fields vary by post
Related public accounts	Sometimes	A discovery hint, not proof of a relationship
Complete follower username list	No	The count is not an exportable identity graph
Friends-only Stories, private Stories, messages, or Memories	No	These are outside the public-data boundary
Posting or editing a creator’s profile	No	Use Snap’s authorized product if you need content management
Owner-only demographics and private analytics	No	Those require account access or an authorized partner flow

This boundary matters because searches for follower “trackers” are full of products that imply private access. Public TikTok and Reddit discussions reviewed for this guide included requests to reveal private Stories, identify people who unfollowed, and monitor a partner’s activity. A public-profile API does none of that. If the requested feature depends on private account access, do not relabel it as public scraping.

Make a live Snapchat profile request

The public route takes one required parameter: handle.

curl --request GET \
  --url 'https://api.scrapecreators.com/v1/snapchat/profile?handle=rosssmith' \
  --header 'x-api-key: YOUR_API_KEY'

A shortened response from a live call on September 5, 2026 looked like this:

{
  "success": true,
  "credits_charged": 1,
  "userProfile": {
    "username": "rosssmith",
    "title": "Ross Smith",
    "subscriberCount": "3020400",
    "categoryStringId": "public-profile-category-v3-people",
    "subcategoryStringId": "public-profile-subcategory-v3-comedian",
    "hasStory": false,
    "hasCuratedHighlights": true,
    "hasSpotlightHighlights": true
  },
  "spotlightStoryMetadata": [
    {
      "description": "...",
      "engagementStats": {
        "viewCount": "...",
        "shareCount": "...",
        "commentCount": "..."
      }
    }
  ]
}

Counts are strings in this response. Convert them before doing arithmetic, but preserve the raw response if you need an audit trail.

const response = await fetch(
  'https://api.scrapecreators.com/v1/snapchat/profile?handle=rosssmith',
  { headers: { 'x-api-key': process.env.SCRAPE_CREATORS_API_KEY } }
);

if (!response.ok) {
  throw new Error(`Snapchat profile request failed: ${response.status}`);
}

const body = await response.json();
const rawCount = body.userProfile?.subscriberCount;
const followerCount = rawCount == null ? null : Number(rawCount);

if (followerCount !== null && !Number.isFinite(followerCount)) {
  throw new Error(`Unexpected subscriberCount: ${rawCount}`);
}

console.log({
  handle: body.userProfile?.username,
  followerCount,
  collectedAt: new Date().toISOString()
});

Keep null as null. A missing field, hidden public count, unavailable profile, or upstream failure is not zero followers.

Three public profiles checked on September 5, 2026

I called the real endpoint for three public handles while updating this article. All three calls returned HTTP 200 with success: true, and each charged one credit.

Public handle	subscriberCount returned	Active public Story	Spotlight metadata rows	Request time
zane	1,469,600	No	0	6.471 seconds
imnotscottysire	1,167,500	No	17	3.423 seconds
rosssmith	3,020,400	No	30	5.532 seconds

This is a dated API check, not a reliability benchmark. Three successful profiles do not prove that every public handle will work forever. They do prove the request and response fields shown above were real on the verification date.

The empty Story values also make an important point: “no active Story right now” is a valid profile response. It should not be treated as a failed profile lookup.

Build a Snapchat follower tracker

A tracker is a sequence of dated snapshots. You do not need private access to calculate public follower growth.

async function collectSnapchatSnapshot(handle) {
  const url = new URL('https://api.scrapecreators.com/v1/snapchat/profile');
  url.searchParams.set('handle', handle);

  const response = await fetch(url, {
    headers: { 'x-api-key': process.env.SCRAPE_CREATORS_API_KEY }
  });

  if (!response.ok) {
    throw new Error(`Lookup failed with ${response.status}`);
  }

  const body = await response.json();
  const rawCount = body.userProfile?.subscriberCount;

  return {
    handle: body.userProfile?.username ?? handle,
    followerCount: rawCount == null ? null : Number(rawCount),
    collectedAt: new Date().toISOString(),
    hasPublicStory: body.userProfile?.hasStory ?? null
  };
}

function compareSnapshots(previous, current) {
  if (previous.followerCount == null || current.followerCount == null) {
    return { change: null, reason: 'missing_count' };
  }

  return {
    change: current.followerCount - previous.followerCount,
    changePercent: previous.followerCount === 0
      ? null
      : ((current.followerCount - previous.followerCount) /
          previous.followerCount) * 100
  };
}

In production, use a fixed collection schedule and store the response status too. Daily snapshots collected at random times can exaggerate or hide short-term changes. Retries should update the failed collection attempt, not create several fake observations for the same period.

Do not call a drop an “unfollow” count unless your data proves that. Net change combines new followers, unfollows, removed accounts, and platform adjustments. Public counts show the result, not every event behind it.

Work with Stories, highlights, and Spotlights

Snap’s Public Profile API overview separates three public content types:

• Stories are temporary and can remain viewable for up to 24 hours.
• Saved Stories stay on a Public Profile.
• Spotlights are permanent video Snaps distributed through Spotlight.

ScrapeCreators returns matching public data in separate parts of the profile response. Check the current Snapchat endpoint documentation before you lock a production schema.

Handle each content group independently. A profile can have a follower count and old Spotlights but no current Story. It can also expose metadata for one public content type and not another.

Media URLs should be treated as source URLs, not permanent storage. If your product needs a durable archive and you have the right to keep the media, copy it under your own retention policy. Do not assume a CDN URL will remain valid forever.

For a manual Story check, the Snapchat Story Viewer is faster than setting up code. For a wider social-data stack, the social media scraping API guide compares the product models you will run into. The Instagram scraping API guide is useful if the same creator-monitoring workflow also needs Instagram profiles, posts, and comments.

Official Snap API or public-data API?

Snap’s official route is more capable when you have the relationship and permissions it expects. Its documentation says the Public Profile API supports creator discovery and content management. It also distinguishes public endpoints from authorized endpoints that expose richer data after creator OAuth or opt-in sharing.

The setup is the catch. On September 5, 2026, Snap’s getting-started page said the API was allowlist-only. It required a Snap business account, an OAuth app, an access token, and coordination with a Snap contact.

Choose the official API if you need to:

• publish or manage content for an authorized profile;
• use owner-authorized analytics;
• build a formal partner workflow around creator consent;
• stay entirely inside Snap’s official partner program.

Choose a public-data API if you need to:

• look up public profiles without asking every creator to connect an account;
• save public follower-count snapshots;
• enrich a creator database with public profile and Spotlight fields;
• use one API alongside other public social platforms.

Choose neither if the product promise depends on private Stories, messages, a complete follower list, or covert account monitoring.

Pricing, credits, and practical limits

ScrapeCreators pricing was verified against the current site source on September 5, 2026:

• New accounts receive 100 free credits without a credit card.
• The Freelance pack lists 25,000 credits for $47, or $1.88 per 1,000 one-credit requests.
• The Business pack lists 500,000 credits for $497, or $0.99 per 1,000 one-credit requests.
• Purchases are pay as you go, not a monthly subscription, and credits do not expire.

The three live profile checks in this guide each reported credits_charged: 1. Check current pricing and the endpoint docs before buying around a fixed estimate. Prices and endpoint costs can change.

The bigger operational limit is data availability. Public profiles can hide fields, have no active Story, remove posts, or disappear. Your integration needs a state for “not available” that is different from 0 and different from an HTTP failure.

Common mistakes

Promising follower identities

A count does not reveal a complete list of users. Keep the field name in your UI honest: “public subscriber count,” not “people we found following this account.”

Mixing friends, followers, Following, and Story viewers

These are different groups. A public profile with 200 followers and 20 friends is not inconsistent. Public audience size should not be reconciled against a private friends list.

Treating every empty content array as an error

A creator may have no current public Story. Return the valid profile and an empty Story collection instead of throwing away useful follower and profile data.

Turning missing data into zero

Zero is a measured value. Missing is an unavailable value. Store them differently or your growth charts will invent crashes and rebounds.

Claiming anonymous access to private content

Public Story tools can read public content. They cannot make friends-only content public. That boundary was one of the most common questions in the Reddit Story-viewer discussions reviewed for this update, and it is also where unsafe marketing claims tend to start.

Forgetting the verification date

Follower counts, prices, public content, and access rules can all change. Record when you checked them. For a tracker, the timestamp is part of the data, not decoration.

If the public field set fits your product, start with the Snapchat API docs and test a few real profiles. If you need owner-authorized analytics or posting, start with Snap’s official application path instead.