SocialCrawl

Pillar data API

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

Pillar is a link-in-bio service. One endpoint takes a pillar.io page URL and returns what is on it: display name, bio, avatar, and every link with its title and destination.

Your first call

1. Read the page

The page below is Pillar's own demo creator.

cURL
curl "https://www.socialcrawl.dev/v1/pillar/page?url=https://pillar.io/example" \
  -H "x-api-key: sc_your_key_here"
TypeScript
const url = new URL("https://www.socialcrawl.dev/v1/pillar/page");
url.searchParams.set("url", "https://pillar.io/example");
const res = await fetch(url, { headers: { "x-api-key": process.env.SOCIALCRAWL_API_KEY! } });
const { data } = await res.json();
for (const link of data.author.ext.links) console.log(link.title, link.url, link.clicks);
Python
import os
import requests

res = requests.get(
    "https://www.socialcrawl.dev/v1/pillar/page",
    params={"url": "https://pillar.io/example"},
    headers={"x-api-key": os.environ["SOCIALCRAWL_API_KEY"]},
)
for link in res.json()["data"]["author"]["ext"]["links"]:
    print(link["title"], link["url"], link["clicks"])

Measured on 22/11/2026: this call returned the page's display name, bio, avatar and 2 links for 1 credit. Each link in author.ext.links carries a title, its destination, its click count and its order on the page.

The outbound social links turn one handle into the creator's full account set. A link that points at an Instagram profile, for example 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"

3. Read computed fields

When an endpoint supports a computed field and the required source inputs are present, the unified response includes that optional field. Depending on the endpoint, optional fields can include engagement_rate, language, content_category, and estimated_reach. See Computed fields for formulas, clamping rules, and null semantics. Where an endpoint supports them, list rows also carry judged labels (computed.labels, computed.relevance) by default at no extra credits; see Labels.

What it covers

What you wantCall
A creator's display name, bio and avatarGET /v1/pillar/page
Every link with its title and destinationGET /v1/pillar/page
How often each link was clickedGET /v1/pillar/page (clicks on each link)
The creator's other social accountsGET /v1/pillar/page, then that platform's profile call

What it does not cover

  • Finding a page. There is no search over Pillar pages, and no way to list a creator's page from their social handle. You need the page URL.
  • Visitors and earnings. Those belong to the page owner's account.
  • Follower counts. The page carries none, so those fields are null.
  • Final destinations behind a shortener or tracking redirect. Links come back as published.

Read a page

GET /v1/pillar/page takes the full page URL, which is the only required parameter.

Link-in-bio pages are where a creator's other accounts are actually listed. This endpoint is usually a step rather than a destination: resolve the page, take the outbound links, and feed the handles you find into the platform endpoints that hold the real data. The endpoint GET /v1/prism/creator-card takes a handle and returns that person's profile across several networks at once, which pairs well with the link list.

All endpoints

1 endpoint available.

EndpointPathCredit Tier
Get Pillar page/v1/pillar/pagestandard (1cr)

Platform notes

  • A page that does not exist returns 404 and is refunded automatically.
  • The url must be the public page URL, including the scheme.

Each link-in-bio service has its own endpoint, because their page structures differ. A Pillar URL will not resolve on any of the others.

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