Linktree scraper API
Resolve a public Linktree profile by handle — presentation fields, link list, and social accounts — over REST with the same JSON envelope as TikTok and Instagram.
1 endpointWhy teams use Social Fetch for Linktree
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.
Homegrown Linktree scrapers chase markup and CDN changes for one more fragile HTML parser beside the social scrapers you already babysit. Social Fetch exposes one GET: public profile by handle. Pass `linktr.ee/{handle}`'s username (with or without `@`) and read the shared `{ data, meta }` envelope — `data.lookupStatus`, links, socials, `meta.requestId`, and `meta.creditsCharged`.
Coverage is public Linktree profiles only. Private or missing handles resolve as typed `not_found`, not an empty 200 that looks like a blank page. Use Linktree's own product when you need to edit a tree or manage a creator account; use this route when Linktree is one enrichment source beside social networks on a shared marketplace key.
What Linktree data can you get?
- Public Linktree profile by handle — display name, bio, avatar, and presentation fields when present.
- Ordered public links with titles and destination URLs.
- Social account pointers listed on the tree when the page exposes them.
- `data.lookupStatus` of `found` or `not_found` so misses stay typed.
- Same Social Fetch API key and `{ data, meta }` envelope as the rest of the marketplace.
Linktree API endpoints
Routes from the live API catalog. Open an endpoint for parameters and examples — credit notes come from OpenAPI pricing extensions.
How to call the Linktree API
1. Create an API key
Sign up at Social Fetch and copy a key (`sfk_…`). New accounts get 100 free credits — enough to smoke-test several live Linktree handles before you wire batch jobs.
2. Call the profile route
Send `GET /v1/linktree/profiles/{handle}` with `x-api-key`. Pass the public username with or without `@`. Use the playground for one-offs; use the TypeScript SDK or curl in production.
3. Join links to social rows
Branch on `data.lookupStatus` before writing. Persist destinations and social pointers on the same person record as TikTok or Instagram handles. Log `meta.requestId`; bill from `meta.creditsCharged`.
How much does the Linktree API cost?
The Linktree profile route charges 1 credit per successful completed lookup. Credits never expire on pay-as-you-go packs. Confirm every response with `meta.creditsCharged` — that field is the billing source of truth.
Social Fetch vs the official Linktree API
Linktree's own product and partner APIs (when available) are the right path for creators editing trees, analytics dashboards, or account management. Social Fetch is public-profile enrichment only: handle in, structured JSON out, no Linktree login and no creator OAuth. Choose Linktree first-party tools for write and account workflows; choose Social Fetch when you already meter multi-network enrichment on one REST key.
Linktree API FAQ
Is there a Linktree scraper API / Linktree data API?
Yes. Social Fetch provides `GET /v1/linktree/profiles/{handle}` for public Linktree profiles. Authenticate with a Social Fetch API key (`x-api-key`). You do not need a Linktree creator login for these public lookups.
What Linktree data does Social Fetch return?
On `lookupStatus: found`, the response includes profile presentation fields plus public links and social pointers when the page exposes them. Exact fields live under `/docs/api` and on this hub's endpoint page. Missing handles return `not_found`.
What handle format does the route accept?
Pass the public Linktree username used on `linktr.ee/{handle}` — letters, numbers, dots, underscores, and hyphens — with or without a leading `@`. The API normalizes casing for the lookup.
How much does the Linktree API cost?
You buy credit packs (or use the 100 free signup credits). The profile lookup costs 1 credit per successful completed request. Always check `meta.creditsCharged`. There is no required monthly subscription for pay-as-you-go packs.
Can I access private or unpublished Linktree pages?
No. Only publicly visible profiles. Restricted or missing trees resolve through `data.lookupStatus` (for example `not_found`) rather than inventing empty link lists.
Does HTTP 200 always mean the profile was found?
No. HTTP 200 means the request finished. Check `data.lookupStatus`: `found` means you got profile data; `not_found` means the handle did not resolve. Persist `meta.requestId` when you need to debug a miss.
Can I use Linktree routes from agents or MCP?
Yes. The same operation appears as a typed MCP tool and can be reached via Ask (`POST /v1/ask`) for plain-English exploration. For production jobs, pin `GET /v1/linktree/profiles/{handle}` so routing stays explicit.
Is scraping Linktree data legal?
Social Fetch returns publicly visible data. You are responsible for how you use it under Linktree's terms, applicable law, and your own compliance review. We do not give legal advice.
Start with Linktree data
Create an account, spend the 100 free credits on live Linktree routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.