# Snapchat (/docs/snapchat)

Read a public Snapchat account's display name, Bitmoji avatar, subscriber count, and bio, plus Spotlight comments

Two public reads on Snapchat: the account card, and the comment thread on a Spotlight snap you already hold a URL for. Both are 1 credit.

Base URL: `/v1/snapchat/...`

  Snapchat publishes no public feed of posts or stories, so there is no
  `snapchat/post` to crawl. The account card and Spotlight comments are the
  whole surface.

## Quickstart

### 1. Fetch a profile

```bash title="cURL"
curl "https://www.socialcrawl.dev/v1/snapchat/profile?handle=djkhaled305" \
  -H "x-api-key: YOUR_API_KEY"
```

### 2. Fetch their content

```bash title="cURL"
curl "https://www.socialcrawl.dev/v1/snapchat/spotlight/comments?url=https://www.snapchat.com/@lilah4823/spotlight/W7_EDlXWTBiXAEEniNoMPwAAYY2pvZnd0ZXVmAZ8fgG8pAZ8ff-_IAAAAAQ" \
  -H "x-api-key: YOUR_API_KEY"
```

### 3. Read 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](/docs/computed-fields.md) for formulas, clamping rules, and null semantics. Where an endpoint supports them, list rows also carry judged labels (`computed.labels`, `computed.relevance`) by default at no extra credits; see [Labels](/docs/labels.md).

## Accounts and Spotlight

| Endpoint                              | Credits | What it returns                                             | Key parameters  |
| ------------------------------------- | ------- | ----------------------------------------------------------- | --------------- |
| `GET /v1/snapchat/profile`            | 1       | Display name, Bitmoji avatar URL, subscriber count, and bio | `handle`        |
| `GET /v1/snapchat/spotlight/comments` | 1       | The comment thread on one Spotlight snap                    | `url`, `cursor` |

`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 and handle pairs in one call, and Snapchat is one of its supported platforms, which beats calling each platform's profile endpoint in a loop.

`spotlight/comments` is the content read. Pass a Spotlight URL and page with `cursor`.

## All endpoints

## Platform notes

**There is no Spotlight detail endpoint.** The upstream returns an empty body for the snap itself, so only its comments are readable.

**The `handle` is the Snapchat username, without an `@`.**

**A handle with no public account returns `404` and is refunded automatically.**

## Next steps

- [Pagination](/docs/pagination.md): Cursor and page walks, and what has_more actually means.
- [Credits](/docs/credits.md): What each tier costs and when a call is refunded.
- [API reference](/docs/api-reference.md): Every parameter and response field, endpoint by endpoint.
- [TikTok](/docs/tiktok.md): The short-form surface most Snapchat handle checks run beside.
- [Instagram](/docs/instagram.md): Stories and highlights, where Snapchat exposes none.