Linktree Profile API
Resolve a public Linktree handle to presentation fields, link list, and social pointers — without a Linktree login.
GET /v1/linktree/profiles/{handle}1 credit per successful request.
About this endpoint
Link-in-bio pages are often the only place a creator lists every outbound destination: shop, newsletter, booking link, and secondary socials. TikTok and Instagram bios truncate that graph to a single URL. Enrichment jobs that stop at the social profile miss the destinations teams actually need for outreach, brand safety, and affiliate mapping.
`GET /v1/linktree/profiles/{handle}` is the dedicated lookup. Pass the public username from `linktr.ee/{handle}` (with or without a leading `@`), send `x-api-key`, and read `data.lookupStatus` before you write a row. On `found`, `data.profile` carries handle, display name, bio, avatar, profile URL, and verification when present; `data.links` is the ordered public link list; `data.socials` holds social account pointers the page exposes. `not_found` returns null profile with empty links and socials; HTTP 200 still means the request finished.
Credit pricing for this operation comes from the API registry and appears on this page, and `meta.creditsCharged` is the billing source of truth. Coverage is public Linktree profiles only — use Linktree's own product when you need to edit a tree or manage a creator account.
Linktree Profile API FAQ
How do I fetch a Linktree profile by handle?
Call GET /v1/linktree/profiles/{handle} with your Social Fetch API key in the x-api-key header. Pass the public Linktree username used on linktr.ee/{handle}, with or without a leading @. Full parameters and examples are in the API docs linked from this page.
How many credits does a Linktree profile lookup cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.
Do I need a Linktree creator login or OAuth?
No. Social Fetch authenticates with your Social Fetch API key only. You do not sign into Linktree or pass creator credentials for this public profile route.
What does lookupStatus mean?
found means data.profile is populated and links/socials may contain rows. not_found means the handle did not resolve to a public page. Always branch on lookupStatus before treating the payload as a found profile.
What fields does the Linktree profile response include?
On found, the envelope includes a profile object (handle, displayName, bio, avatarUrl, profileUrl, verified when present), an ordered links array (title, url, type, thumbnail, position), and socials (platform plus url) when the page exposes them. Exact field lists live in the OpenAPI schema for this route.
Can I access private or unpublished Linktree pages?
No. Only publicly visible profiles. Restricted or missing trees resolve as lookupStatus not_found rather than inventing empty link lists.
Can I use this for enrichment or outreach jobs?
Yes. Teams use the profile route to hydrate CRM or creator records, join outbound destinations to TikTok or Instagram handles, and refresh public link lists on a schedule. Persist meta.requestId when you need to debug a miss.