Pillar

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.

Base URL: /v1/pillar/...

Quickstart

curl "https://www.socialcrawl.dev/v1/pillar/page?url=https://pillar.io/example" \
  -H "x-api-key: YOUR_API_KEY"

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

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.

Read a page

Link-in-bio pages are where a creator's other accounts are actually listed, so 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. 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.

Platform notes

• Each link-in-bio service has its own endpoint, because their page structures differ: Linktree, lnk.bio, Linkme, and Komi. A Pillar URL will not resolve on any of the others.
• A page that does not exist returns 404 and is refunded automatically.
• The url must be the public page URL, including the scheme.

Next steps