Linktree scraper API. One link, every account.
Pull any public Linktree by handle: profile, every link and connected social accounts, as JSON in one request. One call finds someone's Instagram, TikTok and YouTube.
- Connected social accounts
- One call per profile
- Failed lookups aren't charged
Teams running monitoring, research, and enrichment pipelines
Why Social Fetch
We run the Linktree scrapers. You build the product.
Live Linktree data as JSON — proxies, platform changes and consistent output handled for you.
Linktree, plus every other network
One key and one response envelope for Linktree and 24 more platforms — profiles, posts, search, comments and transcripts.
Pricing you can reason about
One request, one credit. Know how far your balance will go before you run your next batch.
Live data on every request
Fetch public data when you ask for it — not from a shared cache.
No scraper maintenance
We handle proxies, browser changes, and platform breakages.
Built for production jobs
Run concurrent workloads with explicit statuses and request IDs.
Regular jobs. Better rates.
Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.
What Linktree data can you get?
1 endpoints, one API key. Every response comes back as live JSON in the same envelope.
Profiles & channels
Look up a Linktree account by handle or URL — bio, counts and metadata.
Browse all 1 Linktree endpoints
What teams build with Linktree data
Monitoring, enrichment, research and content workflows on Linktree data — the same API as every other platform.
How it works
Your first request in three steps.
Use TypeScript or your automation tool of choice.
Sources
+ 19 more platforms
One request
GET/v1/tiktok/profiles/
x-api-key: sk_live_••••••••
Same JSON shape
{
"data": {
"lookupStatus": "found",
"profile": {
"platform": "tiktok",
"handle": "charlidamelio",
"displayName": "charli d’amelio",
"verified": true
},
"metrics": {
"followers": 160263648
}
}
}Step 1
Create your free account
Get an API key with 100 requests included.
Step 2
Choose an endpoint
Pass a username, URL, keyword, or post ID.
Step 3
Get clean JSON
Use the response immediately or send it into your pipeline.
Works with your stack
Code, automate, or connect your AI.
TypeScript
n8n
- Make
- Apify
- MCP
- AI clients
Pricing
Social data, priced simply.
Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.
Starter
18,000credits
$1.61 per 1k · $0.00161 per request
- Top up from $1.61 / 1k if you run out
- Up to 25 monitors
Growth
50,000credits
$1.58 per 1k · $0.00158 per request
- Top up from $1.58 / 1k if you run out
- 5 team seats
- Up to 100 monitors
Scale
150,000credits
$1.50 per 1k · $0.00150 per request
- Top up from $1.50 / 1k if you run out
- 25 team seats
- Up to 250 monitors
- Cancel anytime
- 30-day money-back guarantee
- Price locked while you stay
Need 1M+ credits, invoicing, or volume rates? Talk to us
Trust signals
DevHunt
Product Hunt
Uneed
Customers
Teams building on Social Fetch.
“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”
“Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”
“Live profile data on every request. We never flag accounts from a stale cache.”
“Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”
Linktree API: common questions
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.
The Linktree API in detailHow the Linktree routes work, what they cost, and how they differ from the official API.
Why teams use Social Fetch for Linktree
Link-in-bio pages list shop, newsletter, and secondary social links that TikTok and Instagram bios truncate. Social Fetch exposes one GET: public profile by handle. Pass the linktr.ee/{handle} username (with or without @) and read { data, meta } with data.lookupStatus, links, socials, meta.requestId, and meta.creditsCharged.
Public profiles only. Missing handles return typed not_found. Use Linktree's product to edit a tree; use this route for enrichment beside social networks on one marketplace key.
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}withx-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.lookupStatusbefore writing. Persist destinations and social pointers on the same person record as TikTok or Instagram handles. Logmeta.requestId; bill frommeta.creditsCharged.
What each Linktree route returns
- 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.lookupStatusoffoundornot_foundso misses stay typed.- Same Social Fetch API key and
{ data, meta }envelope as the rest of the marketplace.
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 product and partner APIs are for creators editing trees and account management. Social Fetch is public-profile enrichment: handle in, JSON out, no Linktree login.
Pull your first Linktree data.
Run a live Linktree request in the playground. 100 free credits, no card, JSON back in seconds.
No credit cardSign up in 30 seconds withGoogleGitHub