Linktree APIFetch public Linktree page data as structured JSON with one SocialCrawl API key. Same Author schema as every other platform. Reads are priced in credits.
1 active endpoint. Author-shaped page card.
One live read endpoint for public linktr.ee pages. Display identity, bio when present, avatar when present, and the link stack when the host exposes it. Data API only. No page editing or private dashboards.
/v1/linktree/pagePublic linktr.ee page by full URL. Returns Author identity (username, display name, bio, avatar when present) and every link as author._links with id, type, title, and url. No follower counters on this surface.
url
Returns a Linktree page's display name, bio, avatar, and every link on the page with its title and destination URL.
Use it for linktr.ee pages; lnk.bio, Linkme, Komi, and Pillar pages each have their own endpoint.
1 credit
url · Full URL of the Linktree page
$ curl https://www.socialcrawl.dev/v1/linktree/page?url=https%3A%2F%2Flinktr.ee%2Fcharlidamelio \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responseLinktree is a normal SocialCrawl social surface. You call GET /v1/linktree/page with an API key, spend credits on live misses, and get a single JSON envelope back. No Linktree OAuth. No second SDK.
Send your key in the x-api-key header. No Linktree login cookie, no partner portal. The same key works for TikTok, Instagram, Reddit, and the rest of the catalog.
Pass the full public linktr.ee URL in the url query param. We validate the format before charging.
Standard reads cost 1 credit. Cache hits cost 0. Empty or hard failures refund.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. The page lands as a canonical Author object.
Most products resolve one public page URL, then store or compare the Author card and link list.
GET /v1/linktree/page?url=https://linktr.ee/…Author-shaped page: username, bio, avatar, _links[]
One URL in, structured page card out. No host HTML parsing in your app.
GET /v1/linktree/page
?url=https://linktr.ee/charlidamelio
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here{
"success": true,
"data": {
"id": "2323354",
"username": "example",
"display_name": "example",
"avatar_url": null,
"bio": null,
"url": "https://linktr.ee/example",
"_links": [
{
"id": 1,
"type": "CLASSIC",
"title": "Latest drop",
"url": "https://example.com/drop"
}
]
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl. If you already parse other Author cards, you parse this the same way.
id, username, display_name, avatar_url, bio, url, _links[] (id, type, title, url)
Same request lifecycle as every other /v1 platform endpoint. Link-in-bio hosts are not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds linktree/page. Required url format checks run first. Invalid input returns 400 with no charge. Valid calls debit 1 credit before upstream work.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public page is fetched live. Retries on 5xx/network with a circuit breaker if the source is unhealthy.
Upstream JSON is mapped to Author (plus _links when the host exposes a public link array), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Linktree is public-read creator page data. We normalize it into the SocialCrawl Author schema so your code does not learn a second host-specific layout.
Public creator landing pages on linktr.ee. Read-only surface for research, monitoring, and product jobs. No page edit, analytics login, or private dashboard access.
GET /v1/linktree/page fetches the public page URL you pass, live on request, and normalizes the payload before it reaches you.
A unified JSON envelope: success, data, credits_used, request_id, cached. The page becomes an Author object. Link rows land under author._links.
No write endpoints. No private analytics or click dashboards. No guaranteed follower or verification fields when Linktree does not expose them on the public page.
The jobs this API is most often used for.
Creator link-stack monitoring and competitive bio audits
Callers concentrate on one page URL at a time: resolve the creator card, then store or diff the ordered link list. Public Linktree page as Author JSON for 1 credit. Same key and envelope as the rest of SocialCrawl. No Linktree OAuth.
Page reads are typically a few seconds on live miss. Cache hits return immediately.
The jobs Linktree data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Common ways teams put this data to work, and the stack each one tends to run.
Poll fixed linktr.ee URLs and alert when titles or destinations change. page is the only route.
Capture rival link stacks as structured Author cards and track drops, shops, and affiliate destinations over time.
Enrich a creator profile with the public bio link card. Cache hits keep recurring reads cheap. Same key as the rest of SocialCrawl.
Standard tier is one credit per live call. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/linktree/page?url=https://linktr.ee/charlidamelio" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Same Linktree data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | DIY scraping |
|---|---|---|
| Setup | One GET request with your API key, first page data in minutes | Headless browser, proxy pool, and HTML parser to build and host |
| Authentication | Single x-api-key header, the same key across all 51 platforms | None to manage, but IP blocks and bot detection are your problem |
| Response schema | Unified JSON shared with 50 other platforms: links, bio, avatar in stable fields | Raw HTML that changes whenever Linktree ships a redesign |
| Pricing | 1 credit per page; 100 free credits on signup, no credit card | Proxy and server costs plus engineering hours, hard to predict |
| Maintenance | Upstream layout changes are absorbed behind the stable schema | Your parser breaks silently on every UI update |
Setup
Authentication
Response schema
Pricing
Maintenance
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl