Snapchat Spotlight Comments
Snapchat Spotlight comments are public responses associated with one specified Spotlight item. SocQ stores each returned response as a CommentItem with source identity, comment text, available author context, parent and post references, publication and collection times, and visible like or reply counts.
Features
- One Spotlight URL per taskSubmit one non-empty url on snapchat.com or a Snapchat subdomain; the provider requests one source page for that target.
- Normalized comment recordsRead comment IDs, text, source URLs, timestamps, and available author identity in the stable CommentItem 1.0 result shape.
- Thread and engagement contextKeep parent_id, post_id, likes_count, and replies_count when the source exposes them, without treating missing fields as zero or complete thread coverage.
Parameters
| Parameters | Required | Description |
|---|---|---|
url | Required | Required non-empty Snapchat URL. Runtime validation accepts snapchat.com and its subdomains; use a canonical public /@username/spotlight/{spotlight_id} URL so the provider receives the intended Spotlight resource. |
How to Use
Submit a public Snapchat Spotlight URL, follow the asynchronous task, and read its stored normalized comments with task-result pagination.
- Copy the canonical public Snapchat Spotlight URL you want to inspect.
- POST url to /v1/snapchat/spotlight-comments and save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
- Read data.results.items; if the stored task result spans API response pages, continue with next_cursor while has_more is true.
curl -X POST "https://api.socq.ai/v1/snapchat/spotlight-comments" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.snapchat.com/@queenhaley_13/spotlight/W7_EDlXWTBiXAEEniNoMPwAAYY2pnZnF0bG52AZslQsUdAZslQoRQAAAAAQ"}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Qualitative response review: Review returned public comment text and available author context for questions, reactions, and recurring themes around a selected Spotlight.
- Source-linked comment archives: Preserve comment IDs, source URLs, post_id, parent_id, published_at, and collected_at so every stored response retains its available provenance.
- Visible engagement snapshots: Compare available likes_count and replies_count across returned comments while anchoring each observation to collected_at.
Pro Tips
- Use the canonical public /@username/spotlight/{spotlight_id} URL even though runtime validation checks the Snapchat host rather than enforcing that exact path.
- Do not send cursor or results_limit in the submit payload; this endpoint owns only url and collects one provider page.
- Treat parent_id and replies_count as available context, not proof that the returned records contain a complete reply tree.
- Allow IDs, URLs, text, author fields, published_at, parent_id, post_id, and metrics to be null when the source does not provide them.
- Keep provider collection depth separate from GET /v1/tasks/{task_id} pagination, whose cursor only pages through results already stored by the completed task.
Related APIs
Use these APIs when you need a different type of public Snapchat data.
- Snapchat Profile API
- Snapchat Spotlight API — Retrieve one known public Snapchat Spotlight with normalized creator, caption, media, audio, timestamp, duration, and visible engagement fields when available.