Threads Profiles
Threads profiles are public account pages with usernames, display names, biographies, profile images, websites, and visible follower, following, and post counts. These identity fields and account signals support profile enrichment, public account comparison, and time-based monitoring.
Features
- Supported profile URL batchesProcess one or more threads.com or threads.net profile URLs that use the /@username path while rejecting post links and unrelated paths.
- Normalized profile identityReturn profile ID, URL, username, display name, biography, profile image, and linked website in a consistent profile record.
- Visible account snapshotsKeep available follower, following, and post counts together with collected_at so each set of public metrics has an observation time.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Required list of public Threads profile URLs on threads.com or threads.net. Each path must use the /@username format; bare usernames, post URLs, and unrelated paths are rejected. |
How to Use
Submit known public profile URLs, follow the asynchronous task, and read normalized profile records with cursor pagination.
- Prepare one or more public Threads profile URLs using the /@username path on threads.com or threads.net.
- Submit the links as urls to /v1/threads/profiles and store the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
- Read data.results.items, then request the returned next_cursor while has_more remains true.
curl -X POST "https://api.socq.ai/v1/threads/profiles" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.threads.com/@example"]}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Public profile enrichment: Add username, display name, biography, profile image, website, and source URL to records connected to known Threads profiles.
- Account footprint comparison: Compare visible follower, following, and post counts across a selected set of public profiles.
- Public profile monitoring: Store identity fields and visible metrics with collected_at to compare profile presentation and account signals across collection times.
Pro Tips
- Validate each URL against the /@username path on threads.com or threads.net before submission so post links and unrelated paths do not fail the request.
- Normalize submitted URLs and deduplicate returned profiles by id when available, using url as the fallback stable key.
- Treat biography, profile image, website, and individual account metrics as optional fields so partial public records remain usable.
- Keep collected_at beside follower, following, and post counts so later runs remain distinguishable as separate public snapshots.
Related APIs
Use these APIs when you need a different type of public Threads data.
- Threads Posts API — Collect public post text, author context, media, timestamps, and visible engagement from supported Threads post URLs.
- Threads User Posts API — Discover public posts from Threads profile URLs with a per-profile limit, normalized content, authors, media, timestamps, visible engagement, and source context.