Threads Bio Links API - Public Profile & Published Links

Provide a required Threads username to retrieve the public profile variant that includes optional bio-link information. The response includes status, request_id and data.user. Observed fields include string pk and id, username, full_name, is_verified, follower_count, biography, profile_pic_url and bio_links. The tested zuck profile returned the expected account identity and an empty bio_links array. No nonempty bio-link item schema was established by that result. Treat bio links as optional: an empty array is valid, not an instruction to infer a website or contact address. Preserve any returned links as supplied and review destinations before using them. Public links do not establish contact permission, email availability or account ownership. This operation does not expose private profile activity, and its public follower count is not a follower list.

API Features

Link-aware profile variant Request the username-based public profile operation that includes bio_links alongside the observed identity and biography fields.

Valid empty bio-link arrays Keep bio_links:[] as a legitimate outcome; the verified example had no links and does not establish a populated link-item schema.

Links tied to profile context Review any returned public links together with username, full_name, biography and string account identifiers rather than as unverified standalone destinations.

No inferred contact destination Use only links actually supplied in the response; an absent link does not authorize guessing a website, email address or outreach permission.

Live API Demo

GET /api/project/threads-scraper/get-user-details-with-bio-link

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/threads-scraper/get-user-details-with-bio-link?key=<API_KEY>&username=zuck'

curl -X GET 'https://api.opendata-api.com/api/project/threads-scraper/get-user-details-with-bio-link?key=<API_KEY>&username=zuck'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Creator portfolio references: add explicitly published websites or portfolio links to a selected creator record when the response supplies them.
Partner-link change review: compare your own timestamped bio-link observations and flag changed destinations for manual review.
Campaign landing-page research: inspect publicly listed product or campaign links in profile context without inferring account ownership or contact consent.
Optional-link directory handling: distinguish a profile with an empty bio_links array from a populated link record and avoid manufacturing a fallback destination.

Frequently asked questions

How is this different from the standard profile lookup?

This profile variant includes optional bio_links information alongside public identity and biography fields. Use it when published profile links matter; the standard profile operation is suitable for general identity and follower-count lookup.

Does bio_links:[] mean the profile request failed?

No. The tested zuck profile returned the expected identity with bio_links:[]. An empty array is a valid optional-link result; do not replace it with an invented website or interpret it as an account error.

What fields are guaranteed inside each bio-link item?

The observed successful example contained an empty array, so it did not establish a nonempty item schema. Inspect links actually returned for your requested public profile and tolerate optional or unavailable data instead of assuming a particular link-object shape.

Can a bio link be used as proof of ownership or permission to contact someone?

No. It is a publicly listed destination, not proof of legal ownership, an email address or permission for outreach. Review the destination and account context separately, and preserve an empty result when no link is supplied.

Related operations

Guides

View Subscription Plans →

Get a Threads Profile with Optional Bio Links