LinkMe APIFetch public LinkMe 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 link.me pages. Returns a rich Author card (identity, bio, verified, totalLinks as posts_count). The singular page route does not expose a public link array. Data API only. No page editing or private dashboards.
/v1/linkme/pagePublic link.me page by full URL. Returns a rich Author card: username, display name, bio, avatar path, verified flag, followers when present, and totalLinks mapped to posts_count. The singular page route does not expose a public link array. author._links is null on this endpoint.
url
Returns a Linkme page's display name, bio, avatar, and every link on the page with its title and destination URL.
Use it for link.me pages; Linktree, lnk.bio, Komi, and Pillar pages each have their own endpoint.
1 credit
url · Full URL of the Linkme page
$ curl https://www.socialcrawl.dev/v1/linkme/page?url=https%3A%2F%2Flink.me%2Fexample \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responseLinkMe is a normal SocialCrawl social surface. You call GET /v1/linkme/page with an API key, spend credits on live misses, and get a single JSON envelope back. No LinkMe OAuth. No second SDK.
Send your key in the x-api-key header. No LinkMe login cookie, no partner portal. The same key works for TikTok, Instagram, Reddit, and the rest of the catalog.
Pass the full public link.me 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 the Author identity card (including totalLinks).
GET /v1/linkme/page?url=https://link.me/…Author-shaped profile: name, bio, verified, totalLinks as posts_count
Use when you need the LinkMe identity card. Do not expect _links on this route.
GET /v1/linkme/page
?url=https://link.me/example
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here{
"success": true,
"data": {
"id": "c29a6af10782b58ae65eddd8333e40c0",
"username": "example",
"display_name": "Example Creator",
"avatar_url": "default/profile/avatar-1.png",
"bio": "Creator bio",
"verified": true,
"followers": null,
"posts_count": 105,
"url": "https://link.me/example",
"_links": null
},
"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, verified, followers, posts_count (totalLinks), url; _links is null on page
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 linkme/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
LinkMe 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 profiles on link.me. Read-only surface for research, monitoring, and product jobs. No page edit or private dashboard access.
GET /v1/linkme/page fetches the public page URL you pass, live on request, and normalizes profile.* fields into Author.
A unified JSON envelope with an Author-shaped data object. totalLinks becomes posts_count. The public link array is not on this singular route.
No write endpoints. No private analytics. No public links list on page. Avatar may be a relative path until postmap absolute URL handling applies.
The jobs this API is most often used for.
link.me creator identity enrichment
Callers use page for profile identity and link counts. They do not get per-link destinations from this singular route. Richer LinkMe profile metadata (verified, totalLinks, followers when present) as Author JSON for 1 credit. Honest gap: no public link array on page.
Page reads are typically a few seconds on live miss. Cache hits return immediately.
Common ways teams put this data to work, and the stack each one tends to run.
Resolve link.me URLs into verified identity and link-count signals without scraping HTML.
Track rival LinkMe profiles for bio and verification changes. Pair with other hosts when you need link destinations.
Attach a LinkMe Author card to a creator record. Cache hits keep recurring reads cheap.
Standard tier is one credit per live call. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/linkme/page?url=https://link.me/example" \
-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 LinkMe 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 Linkme 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