snapchat/
profile

Use the Snapchat Profile API to look up one public Snapchat profile by username and receive normalized identity, biography, profile media, website, account flags, location, and available profile counts.

Snapchat Profile API

Username lookup
Public profile
Normalized account
0.19 credits / request
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Snapchat Profile

A Snapchat public profile can expose a username, display name, biography, avatar, cover, website, account flags, location, and visible profile counts. This focused lookup turns one known username into a normalized account snapshot for enrichment, review, or later comparison.

Snapchat Profile API Features

  • Exact username lookupResolve one known Snapchat username per task, with or without a single leading @, instead of searching for accounts.
  • Normalized profile identityThe Snapchat Profile API returns available username, display name, biography, public URL, and stable source identifier in an AccountItem record.
  • Profile media and contextKeep available avatar, cover, website, and location fields separate for display, indexing, and enrichment workflows.
  • Visible account signalsCapture available verification and privacy flags plus follower, following, and post counts at collection time.

Snapchat Profile API Parameters

ParametersRequiredDescription
usernameRequiredRequired Snapchat username. Supply one optional leading @ followed by 1–64 ASCII letters, digits, periods, underscores, or hyphens; spaces, profile URLs, and other characters are rejected.

How to Use the Snapchat Profile API

Submit one accepted username to the Snapchat Profile API, wait for the asynchronous task, then read its normalized profile result.

  1. Choose one known Snapchat username using letters, digits, periods, underscores, or hyphens; one leading @ is optional.
  2. Send username to /v1/snapchat/profile and retain the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task reaches succeeded or failed.
  4. After success, read data.results.items; this detail lookup normally returns one profile or an empty list.
curl -X POST "https://api.socq.ai/v1/snapchat/profile" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"username":"zane"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items after the task succeeds

Snapchat Profile API Use Cases

  • Known-account enrichment: Add public identity, biography, profile media, website, and available counts to a record that already contains a Snapchat username.
  • Selected profile review: Present one public account in a consistent profile card or review queue without mixing in Stories, Spotlights, or account-management actions.
  • Public snapshot comparison: Store collected_at with successive results to compare public profile text, account flags, media, or visible counts over time.

Snapchat Profile API Pro Tips

  • Use the same canonical username form in your own records even though the request accepts one leading @.
  • Submit exactly one username per task; batching, profile URLs, and results_limit are outside this endpoint contract.
  • Treat accepted syntax as input validation, not proof that the username resolves to an accessible public profile.
  • Handle website, location, profile media, account flags, and individual metrics as optional fields.
  • Keep collected_at with every stored result because profile text and visible counts are point-in-time values.

Beyond the Snapchat Profile API, use these APIs when you need a different type of public Snapchat data.

Explore other platforms

Combine Snapchat data with public data from other supported social platforms.

Snapchat Profile API — FAQ

Snapchat Profile API is a programmatic interface for looking up one public Snapchat profile by username and returning its available fields as a normalized account record.

Use an optional single @ followed by 1–64 ASCII letters, digits, periods, underscores, or hyphens. Spaces, profile URLs, and other punctuation do not pass the request validator.

The AccountItem schema includes identity, public URL, biography text, avatar, cover, website, verification and privacy flags, location, collection time, and available follower, following, and post counts.

Yes. Valid username syntax does not guarantee a publicly accessible provider result, so a successful task can store zero items.

No. The provider performs one profile-detail request and returns at most one profile record. The shared task-results route is cursor-paginated, but this endpoint has no results_limit and normally fits in the first page.

A successful task uses a fixed 0.19 SocQ credits, independent of whether the stored result count is one or zero. Failed tasks follow the platform's task refund behavior.