SocialCrawl

LinkBio data API

Read link-in-bio pages from LinkBio with one key and one response shape.

lnk.bio is a link-in-bio service common among creators who want a lighter page than Linktree offers. Its page carries the same thing every link-in-bio page carries and no social profile does: an explicit, ordered list of where the creator wants their audience to go next.

Your first call

1. Read the page

The page below is lnk.bio's own account.

cURL
curl "https://www.socialcrawl.dev/v1/linkbio/page?url=https%3A%2F%2Flnk.bio%2Flnkbio" \
  -H "x-api-key: sc_your_key_here"
TypeScript
const url = new URL("https://www.socialcrawl.dev/v1/linkbio/page");
url.searchParams.set("url", "https://lnk.bio/lnkbio");
const res = await fetch(url, { headers: { "x-api-key": process.env.SOCIALCRAWL_API_KEY! } });
const { data } = await res.json();
console.log(data.author.display_name, data.author.ext?.links ?? []);
Python
import os
import requests

res = requests.get(
    "https://www.socialcrawl.dev/v1/linkbio/page",
    params={"url": "https://lnk.bio/lnkbio"},
    headers={"x-api-key": os.environ["SOCIALCRAWL_API_KEY"]},
)
author = res.json()["data"]["author"]
print(author["display_name"], author.get("ext", {}).get("links", []))

Measured on 22/11/2026: this call returned the page's id, username and display name for 1 credit. That response carried no bio and no author.ext.links, so read the link list defensively as the code above does.

When a page lists social accounts, they turn one handle into the creator's full account set. A link that points at instagram.com/nasa gives you the handle to feed into that platform's profile endpoint.

cURL
curl "https://www.socialcrawl.dev/v1/instagram/profile?handle=nasa" \
  -H "x-api-key: sc_your_key_here"

What it covers

What you wantCall
A page's display name, bio and avatarGET /v1/linkbio/page
The links on the page, when it lists themGET /v1/linkbio/page
The creator's other social accountsGET /v1/linkbio/page, then that platform's profile call

What it does not cover

  • Finding a page. There is no search over LinkBio pages, and no way to list a creator's page from their social handle. You need the page URL.
  • Page visitors, click counts and earnings. Those belong to the page owner's account.
  • A link list on every page. A page that publishes no links comes back without one, as the recorded call above did.
  • Final destinations behind a shortener or tracking redirect. Links come back as published.

Read a page

GET /v1/linkbio/page takes the full page URL and returns the display name, bio and avatar, plus every link with its title and destination where the page lists them.

The link list is the part most callers read, when the page has one. It is a creator's own declaration of where their audience should go next. It usually includes the shops they sell through, the affiliate networks they run, the newsletter they own, and the social accounts they actually maintain rather than the ones they merely registered.

The list has two common uses. For creator vetting, the destinations reveal commercial relationships that a profile bio does not: an affiliate subdomain or a brand-specific landing page is a disclosed partnership. For cross-platform resolution, the outbound social links turn one handle into the creator's full account set.

All endpoints

1 endpoint available.

EndpointPathCredit Tier
Get Linkbio page/v1/linkbio/pagestandard (1cr)

Platform notes

  • Destinations are as-published, not resolved. A link that points at a shortener or a tracking redirect comes back as that URL. Follow it yourself if you need the final destination, and expect UTM parameters to survive.
  • You need the page URL. It usually comes from a social profile's bio link (author.ext.bio_link where a platform exposes one) or from the bio text itself.
  • A page with no links returns an empty link list rather than an error.
  • The url must be the public page URL, including the scheme.

Each link-in-bio service has its own endpoint. They return the same shape, so one parser handles all of them. Only the base path changes.

ServicePage URL looks likeCall
Linktreehttps://linktr.ee/handleGET /v1/linktree/page
lnk.biohttps://lnk.bio/handleGET /v1/linkbio/page
LinkMehttps://link.me/handleGET /v1/linkme/page
Komihttps://handle.komi.io/GET /v1/komi/page
Pillarhttps://pillar.io/handleGET /v1/pillar/page

Next steps

On this page