Profile
1 credit/v1/snapchat/profileGet Snapchat user profile.
handle
Snapchat APIFetch public Snapchat profile data with one API
Fetch public Snapchat data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.
/v1/snapchat
1 active endpoint
- GET /v1/snapchat/profile
What Snapchat endpoints does SocialCrawl ship?
1 live read endpoint for public Snapchat profile data. Data API only.
Snapchat API2 endpoints supported
View docsReturns a Snapchat account's public profile: display name, Bitmoji avatar URL, subscriber count, and bio.
Use it to confirm a Snapchat account exists and read its public details.
1 credit
GET/v1/snapchat/profile?handle=djkhaled305
handle · Snapchat username
$ curl https://www.socialcrawl.dev/v1/snapchat/profile?handle=djkhaled305 \
-H "x-api-key: sc_YOUR_API_KEY"idle
// Running this live needs your own API key. Hit "Try it" to see an example responseHow the Snapchat API works
Snapchat is a normal SocialCrawl social surface. You call GET /v1/snapchat/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.
Authenticate every call
Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.
GET with query params
Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.
Pay in credits, not seats
Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.
The usual integration chain
Most callers resolve a public Snapchat handle to a profile card.
01Handle
GET /v1/snapchat/profilePublic handle string
Start from the username without the @.
02Profile
GET /v1/snapchat/profileAuthor-shaped public profile
One standard credit read on live miss.
03Cache
GET /v1/snapchat/profileSame envelope with credits_used 0 on hit
Recurring lookups stay cheap.
04Pipeline
GET /v1/snapchat/profileShared Author fields for downstream jobs
Same schema as other platforms.
request
GET /v1/snapchat/profile
?handle=djkhaled305
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_hereresponse envelope
{
"success": true,
"data": { "/* Author | Post | PostList | CommentList | … */": true },
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}What lands in data
Field names match the rest of SocialCrawl where archetypes align.
Authorprofile
id, username, display_name, avatar_url, bio, followers, url, ext
PostList / Postprofile
items[].post with id, url, content, engagement, author, published_at, ext
CommentListprofile
items[] with author, content.text, engagement, published_at when comments ship
Search / Mediaprofile
search hits, media metadata, or transcripts depending on route
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint.
- 01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.
- 02
Validate, then debit
Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.
- 03
Cache or fetch
A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.
- 04
Normalize and return
Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.
Billing rules that matter in production
- Standard live miss: tier cost (often 1 credit)
- Advanced reads: typically 5 credits
- Premium reads: typically 10 credits
- Metered routes: min floor when documented
- Cache hit: 0 credits
- Empty / hard fail: auto-refund
- Bad params: 400, never charged
- No credits: 402, never charged
- Disabled routes: 503, never charged
How we get the data
Snapchat is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.
What Snapchat is for this API
Public Snapchat surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.
How SocialCrawl reaches it
Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.
What leaves our edge
Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.
What we do not ship live
No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.
field map sketch
public profile / channel→ author.*profile identity and counters
public item payload→ data.*post content and engagement
list / search page→ items[] or hitscomments or search hits when present
What this API is used for
The jobs this API is most often used for.
1active Snapchat endpoints in the registry
1credits per live profile miss
Snapchat monitoring and content intelligence
Callers concentrate on profile, content lists, search, and deepen paths on Snapchat. Structured Snapchat JSON on the shared schema with one SocialCrawl API key.
Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.
Use case examples
Common ways teams put this data to work, and the stack each one tends to run.
Monitoring jobs
Python, cron, Slack botsPoll profiles and feeds on Snapchat. Alert when engagement velocity jumps.
Research and VoC
Node, notebooks, BI loadsSearch and expand posts for brand, product, and competitor language on Snapchat.
Backend product jobs
Go, workers, ExplorerWire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.
Call it in two lines
Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.
curl "https://www.socialcrawl.dev/v1/snapchat/profile?handle=djkhaled305" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/snapchat/profile?handle=djkhaled305" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Endpoints
What data does the Snapchat API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Comparison
How does SocialCrawl compare to DIY scraping for Snapchat data?
Same Snapchat data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | DIY scraping |
|---|---|---|
| Authentication | One x-api-key header | None: you manage proxies and request fingerprints yourself |
| Setup / approval | Sign up and call immediately | Build a scraper, proxy pool, and parsing layer first |
| Rate limits | Credit-based, pay per request | Whatever your proxies survive before blocks |
| Response schema | Unified JSON shared across 51 platforms | Raw HTML you parse and re-parse after layout changes |
| Pricing | 1 credit per profile; 100 free credits on signup | Proxy, server, and engineering costs scale with volume |
| Data coverage | Public profile fields: name, Bitmoji, subscribers, bio | Anything you can extract, at your own legal and technical risk |
| Maintenance | Schema stays stable when Snapchat changes its markup | Every Snapchat redesign breaks your selectors |
Authentication
SocialCrawl
One x-api-key header
DIY scraping
None: you manage proxies and request fingerprints yourself
Setup / approval
SocialCrawl
Sign up and call immediately
DIY scraping
Build a scraper, proxy pool, and parsing layer first
Rate limits
SocialCrawl
Credit-based, pay per request
DIY scraping
Whatever your proxies survive before blocks
Response schema
SocialCrawl
Unified JSON shared across 51 platforms
DIY scraping
Raw HTML you parse and re-parse after layout changes
Pricing
SocialCrawl
1 credit per profile; 100 free credits on signup
DIY scraping
Proxy, server, and engineering costs scale with volume
Data coverage
SocialCrawl
Public profile fields: name, Bitmoji, subscribers, bio
DIY scraping
Anything you can extract, at your own legal and technical risk
Maintenance
SocialCrawl
Schema stays stable when Snapchat changes its markup
DIY scraping
Every Snapchat redesign breaks your selectors
FAQ
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usDoes Snapchat have a public API?
Snapchat only publishes a Marketing API (for ad buying), a Conversions API, and the Snap Kit developer platform. None of those give you public profile data. SocialCrawl fills that gap with one profile endpoint you can call with x-api-key, no Snap developer account required.
How do I scrape Snapchat data with an API?
Send a GET request to /v1/snapchat/profile with a Snapchat handle in the handle parameter. SocialCrawl returns the user's display name, Bitmoji avatar URL, subscriber count, and bio description in a unified JSON schema shared with every other SocialCrawl platform.
What data can I pull from Snapchat?
Public profile fields only: display name, Bitmoji avatar URL, subscriber count (followers), and bio. Snapchat does not publicly expose Stories, Spotlight, or friend lists, so those fields are not returned. If you need ad data, use the official Snap Marketing API directly.
How much does the Snapchat API cost?
The Snapchat profile endpoint costs 1 credit per request on the standard tier. New accounts get 100 free credits with no credit card required, enough to pull around 100 Snapchat profiles while you prototype before committing to a paid plan.
Is scraping Snapchat profiles legal?
SocialCrawl accesses only publicly visible Snapchat profile pages, the same data anyone can see on snapchat.com/add/handle without logging in. You are responsible for complying with Snapchat's Terms of Service and applicable data protection regulations based on your specific use case. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.
Why isn't the official Snap Kit API enough for my use case?
Snap Kit only returns data about users who have explicitly logged in to your own app and granted permission. It cannot fetch a third-party user's public profile. SocialCrawl's endpoint works for any public Snapchat handle without consent flows or app review.
What is the best Snapchat scraper API?
SocialCrawl is one of the few APIs that returns public Snapchat profile data at all. Snapchat publishes no official read API for profiles. One GET with a handle returns display name, Bitmoji avatar, subscriber count, and bio for 1 credit. New accounts get 100 free credits, no credit card required.
Is there a Snapchat data API for public profiles?
Yes: SocialCrawl is a Snapchat data API for public profile data. Snapchat itself ships only the Marketing, Conversions, and Snap Kit developer platforms, none of which read a third-party public profile, so there is no official public content API to fall back on. One GET with a handle returns display name, Bitmoji avatar, subscriber count, and bio as unified JSON, at 1 credit per request with 100 free credits on signup and no Snap developer account.
Ask AI about SocialCrawl