Does Snapchat Have a Public API for Profiles, Stories and Spotlight?

Published October 1, 2026 · UpdatedOctober 16, 2026

If the Snapchat column in your listening stack is still a headless browser, you are already on the before. GET snapchat.com/@handle, regex the subscriber string out of a hero block, screenshot the Story tray, paste a Spotlight share URL into Playwright. That sheet fills until a wrapper class moves, a Story media URL expires mid-download, or the Spotlight page serves a login wall to the datacenter IP. The public profile did not vanish. The HTML contract did. A TikTok scrape can often be patched after a class rename. Snapchat's public pages are less forgiving on datacenter egress: one login wall and the whole column goes mute.

Snapchat still has no official read API for an arbitrary public profile, today's Story, a Spotlight clip, or the Lens catalog. Login kits and ads APIs write into the app or manage your own campaigns; they do not export someone else's public card. The after is not a sturdier CSS parser. It is GET on the Snapchat Content API: a username in, JSON out, and flags that say which follow-ups are worth paying for. Opening this page or copying a snippet does not send those GETs.

Sign in, copy an authorized key from the dashboard, and read it from OPENDATA_API_KEY on the server. Curl examples keep YOUR_API_KEY as a dead placeholder. The key rides in the query string, so those URLs do not belong in tickets, screenshots, or browser JavaScript.

The gap a TikTok-only monitor still has

TikTok, Instagram, and YouTube already sit in most creator tables. Snapchat is the blank column because teams still treat the app as private chat. The public surface is larger than that: profiles with subscriber counts, 24-hour public Stories, pinned Highlights, Spotlight clips with views and comments, and an AR Lens catalog. The before is a TikTok-only monitor that reports "this creator is quiet" on a week they posted three Stories and a Spotlight. That is a coverage hole, not a quiet week.

The naive patch is to scrape those pages the way the TikTok HTML job already scrapes. The correct patch is the same job — a watchlist of handles, a daily profile poll, a Story archive, Spotlight comments into review — over REST, not over CSS. All calls are GET to https://api.opendata-api.com/api/project/snapchat-content/<operation>. HTTP 4xx/5xx is transport, auth, or quota: check the key and the balance. HTTP 200 is not a found profile. The body still carries success and data, and an unknown handle commonly comes back HTTP 200 with success: false. Treat that as a miss. Do not retry it as if the account were flaky. If the gateway wraps another {code, message, data} layer, require code 200 before you read success.

Username is the handle, not a phone

The before on this project is treating every spreadsheet cell as a phone. Every profile-scoped operation takes username without @. It does not take a phone, an email, or a user id you borrowed from another product. Feeding a number into get-profile does not become a registration check. That job lives on a different project — Snapchat number lookup.

The documented handle for the lightweight card is brentrivera. The URL below does nothing until you replace the placeholder and run it.

curl "https://api.opendata-api.com/api/project/snapchat-content/get-profile?username=brentrivera&key=YOUR_API_KEY"

On a hit, data.info holds username, title (display name), bio, websiteUrl, subscriberCount (a string — cast it before you sort), profilePictureUrl, snapcodeImageUrl, and three booleans: hasStory, hasCuratedHighlights, hasSpotlightHighlights. Those flags are the after. The before is calling get-user-story and get-user-curated-highlights on every row "to be sure." Empty polls still spend credits. success: false means the handle did not resolve. hasStory: false means it resolved and nothing is live. Do not collapse those two into one "no data" cell. Store subscriberCount from this call; do not buy a full footprint just to refresh a count.

get-full-profile is the one-shot — profile, story, curatedHighlights, spotlightHighlights, lenses — when you already know you want the footprint. It is not the default for a daily watchlist of hundreds of handles. If you only have a keyword, get-search with keyword=music (or another documented term) returns mixed sections: Spotlight, Lenses, creators, places. Search hits are candidates. Confirm the handle with get-profile before you archive anything.

Stories, Spotlight, then Lenses

The before is one column named "Snapchat content." Stories expire in 24 hours. Highlights do not. Spotlight is a short-video object with views and a comment thread. Lenses are AR effects, not posts. Folding those four into one blob is how archives stop meaning anything.

Correct order after the profile card:

  1. If hasStory, call get-user-story. A live Story is an object with snap media URLs. Nothing live is {success: true, data: null} — a real answer, not a crash. Poll a few times per day if you archive; skip the call when the flag is false.
  2. If hasCuratedHighlights, call get-user-curated-highlights for pinned albums that outlive the 24-hour window.
  3. A Spotlight share URL goes to get-spotlight-by-link and, if you need the thread, get-spotlight-comments-by-link. A username is the wrong input for those two. URL-encode the full link; do not strip query characters.
  4. Lenses are a catalog. get-trending-lenses returns data.topLenses (about 24 entries: lensId, name, creatorName, creatorIsOffical, iconUrl, deeplinkUrl). A hashtag such as halloween is a different probe.
import os

import requests

BASE = "https://api.opendata-api.com/api/project/snapchat-content"
KEY = os.environ["OPENDATA_API_KEY"].strip()


def call(operation, **params):
    resp = requests.get(
        f"{BASE}/{operation}",
        params={"key": KEY, **params},
        timeout=60,
    )
    if not resp.ok:
        raise RuntimeError(f"HTTP {resp.status_code}")
    body = resp.json()
    # Unwrap gateway {code, data}; HTTP 200 is not business success
    while isinstance(body, dict) and "code" in body and isinstance(
        body.get("data"), (dict, list)
    ):
        if str(body.get("code")) != "200":
            raise RuntimeError(body.get("message"))
        body = body["data"]
    return body


# After: card first, then flags. Before would call get-user-story on every row.
payload = call("get-profile", username="snoopdogg")
if not payload.get("success"):
    raise SystemExit("handle did not resolve")
info = (payload.get("data") or {}).get("info") or {}
if info.get("hasStory"):
    story = call("get-user-story", username="snoopdogg")
    live = story.get("data") is not None

link = (
    "https://www.snapchat.com/spotlight/"
    "W7_EDlXWTBiXAEEniNoMPwAAYa3F2d2VwcG5uAY336_EbAY3368kUAAAAAQ"
)
spot = call("get-spotlight-by-link", spotlight_link=link)
comments = call("get-spotlight-comments-by-link", spotlight_link=link)

The snoopdogg handle is the documented Story example, not a promised live Story. data: null after a true success means "nothing to archive right now," not "retry until it fills." The share link is a different object from a username: keep metadata.videoMetadata.contentUrl as media when present, cast metadata.engagementStats.viewCount (a string) before you chart it, and leave comments on their own call. llmTitle / llmKeywords are labels for tagging, not a claim the clip performed. Running this block spends credits; copying it does not.

This is not a Snapchat number check

This project does not ask whether a phone is on Snapchat. It does not take number, it does not return registered, and it will not mint a session. If the spreadsheet cell is a phone, stop and use Snapchat number lookup. Feeding a phone into username is not a fallback.

Do not scrape snapchat.com HTML as the integration. Do not treat HTTP 200 as a hit — read success, and treat data: null on a live-Story call as an empty day. Do not fire Story, Highlights, and Spotlight on every handle "to be complete"; the three booleans exist so you skip empty polls. Do not send a username to get-spotlight-by-link, or a Spotlight URL to get-profile. Do not expect DMs, private Stories, a friend graph, live location, or a send API. Do not put key in a frontend bundle. Do not treat subscriberCount as KYC.

public-profile on the lookup project is a handle-existence card (display name, snapcode). It is not Stories, Spotlight, or Lenses — different project, different envelope. Product page: Snapchat Content API.