Threads Posts API

Threads Posts

Features

• Direct post URL resolutionResolve public threads.com or threads.net /@username/post/{post_id} URLs into records for the exact submitted posts rather than a profile feed.
• Post content and author attributionReturn post identifiers, source URLs, text, and available author IDs, usernames, display names, and profile URLs for traceable records.
• Media and visible engagement snapshotKeep normalized media references, publication and collection times, and visible like, comment, repost, and share counts together for each post.

Parameters

How to Use

Submit the public Threads posts you already know, follow the asynchronous task, and read normalized results with cursor pagination.

1. Prepare one or more public Threads post URLs using the /@username/post/{post_id} path on threads.com or threads.net.
2. Submit the links as urls to /v1/threads/posts and 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/posts" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.threads.com/@example/post/POST_ID"]}'

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

Best Use Cases

• Enrich a selected post list: Convert known post URLs into records with IDs, text, author fields, media, timestamps, and source links for a defined dataset.
• Review public content and attribution: Use text, media references, author identity, and the original URL to examine selected publications while retaining their public source.
• Compare engagement snapshots: Pair likes_count, comments_count, reposts_count, and shares_count with collected_at to compare observations captured at different times.

Pro Tips

• Validate each URL against the /@username/post/{post_id} path before submission so profile pages and unrelated Threads paths do not fail the request.
• Deduplicate submitted links by their post path before batching so alternate supported hostnames do not create repeated work for the same post.
• Use this endpoint only for known post URLs; omit results_limit because it does not discover a profile feed or expand a post into replies.
• Handle text, author fields, media, publication time, and individual metrics as optional so a partially exposed public post does not break result processing.
• Store collected_at with the visible engagement fields to preserve when each snapshot was observed.

Related APIs