Get a Threads user profile by username · Threads API
Return a Threads user's public profile by username, including display name, bio, follower count, and verification status. Useful as the entry point for any account-level research.
Try it without an API key: Threads viewer.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/threads/users/{username} \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- usernamepathrequired
This operation is part of the Threads API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Threads public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Resolve a public Threads identity into structured profile metadata for enrichment agents.
- Refresh creator, company, or account snapshots without managing source-specific response shapes.
- Give an AI agent a stable Threads data source without building a per-platform integration.
- Normalize Threads responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields in the data object
A successful Get a Threads user profile by username call returns one data object with these fields.
- idstring
- Threads URL slug (`username`).
- user_idstring
- Numeric Threads pk; surfaced for callers that want to skip the gateway-side username → pk stitch.
- usernamestring
- full_namestring
- biographystring
- profile_pic_urlstring
- follower_countnumber
- is_verifiedboolean
- is_privateboolean
Agents & Skills built on Threads
You rarely call Get a Threads user profile by username by hand. These prebuilt agents and skills already read Threads data inside Claude or Codex — start from one of them, or call this endpoint yourself.
Try it free in the browser
More Threads operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Search top Threads posts
Search Threads posts by keyword, ranked by engagement, returning the top matches as a cursor-paginated list. Useful for surfacing the most resonant content on a topic.
List Threads posts authored by a user
Return the posts authored by a Threads user, by username, as a cursor-paginated list. Useful for profiling a creator's content, monitoring a brand, or building an archive.
List Threads replies authored by a user
Return the replies a Threads user has authored, by username, as a cursor-paginated list. Useful for understanding how an account engages in conversation beyond its own posts.
List Threads reposts by a user
Return the posts a Threads user has reposted, by username, as a cursor-paginated list. Useful for inferring an account's interests and the content it amplifies.
Get a Threads post by URL
Returns one Threads post by URL with its author, media, counts, the rest of its thread, replies and related posts. Returns `not_found` when the post does not exist.
Resolve a Threads post URL into its numeric media ID
Convert a public Threads post URL into its post code and numeric `media_id`. Accepts threads.com and threads.net links. Useful for normalizing saved links and matching identifiers across datasets. This identifier conversion does not verify that the post still exists or is publicly accessible.