Threads User Posts API

Threads User Posts

Features

• Bounded profile-based discoveryAccept one or more public Threads profile URLs and apply results_limit separately to each profile, with a default of 100 and an accepted range from 1 through 2,000.
• Normalized post, author, and media recordsReturn post identifiers, source URLs, text, available author identity, and public media references in a consistent result shape.
• Engagement and discovery contextKeep visible like, comment, repost, and share counts with publication time, collected_at, and submitted profile context when supplied by the source record.

Parameters

How to Use

Submit public Threads profile URLs with a per-profile result limit, follow the asynchronous task, and read normalized posts with cursor pagination.

1. Prepare one or more public Threads profile URLs using the /@username path on threads.com or threads.net.
2. POST urls and an optional results_limit to /v1/threads/user-posts, then store the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
4. Read data.results.items, then request the returned next_cursor while has_more remains true.

curl -X POST "https://api.socq.ai/v1/threads/user-posts" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.threads.com/@example"],"results_limit":100}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Selected-profile post datasets: Retain post IDs, source URLs, text, author fields, media references, timestamps, and submitted profile context for a defined set of public profiles.
• Content and format research: Use post text, public media references, author attribution, and publication times to examine recurring subjects and content formats across selected profiles.
• Public engagement comparison: Compare visible like, comment, repost, and share counts across profile collections while using collected_at to anchor each observation.

Pro Tips

• Validate each input as a threads.com or threads.net /@username profile URL before submission so bare usernames, post links, and unrelated paths do not fail the request.
• Plan requested depth and the pre-request credit estimate as the number of urls multiplied by results_limit because the limit applies separately to every profile.
• Store discovery_input, input_url, and collected_at with each result so downstream records retain the submitted profile and observation time.
• Handle text, author fields, media, created_at, and individual metrics as optional, and do not infer whether a record is an original post, reply, quote, or repost because no subtype is exposed.

Related APIs