Snapchat

GET /v1/snapchat/profile takes a handle and returns a public Snapchat account's display name, Bitmoji avatar URL, subscriber count, and bio. GET /v1/snapchat/spotlight/comments takes a Spotlight url and returns that snap's comments. Both are 1 credit.

Base URL: /v1/snapchat/...

Getting Started

curl "https://www.socialcrawl.dev/v1/snapchat/profile?handle=djkhaled305" \
  -H "x-api-key: sc_your_api_key_here"

Profile vs Spotlight comments

Snapchat still publishes no public feed of posts or stories, so there is no snapchat/post to crawl. What exists publicly is the account card and, when you already have a Spotlight URL, the comment thread on that snap.

/v1/snapchat/profile is the identity lookup: confirm an account exists and read its subscriber count. That makes it a useful leg in handle vetting rather than a content source. If you are checking a name across several networks, POST /v1/prism/profiles takes up to 50 (platform, handle) pairs in one call and Snapchat is one of its supported platforms, which beats calling each platform's profile endpoint in a loop.

/v1/snapchat/spotlight/comments is the content read: pass a Spotlight URL, page with cursor. There is no Spotlight detail endpoint yet, because the upstream returns an empty body for the snap itself.

Computed fields

When an endpoint supports a computed field and the required source inputs are present, the unified response includes that optional field. Depending on the endpoint, optional fields can include engagement_rate, language, content_category, and estimated_reach. See Computed fields for formulas, clamping rules, and null semantics.

Endpoints

2 endpoints available.

Notes

• GET with query parameters
• Authentication via x-api-key header
• Responses follow the unified SocialCrawl schema
• The handle is the Snapchat username, without an @
• A handle with no public account returns 404 and is refunded automatically