# Pillar (/docs/pillar)



Pillar [#pillar]

Pillar is a link-in-bio page. `GET /v1/pillar/page` takes one and returns what is on it: display name, bio, avatar, and **every link with its title and destination URL**. One endpoint, 1 credit.

Base URL: `/v1/pillar/...`

Getting Started [#getting-started]

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

The `url` parameter is the full page URL, and it is the only parameter.

What this is for [#what-this-is-for]

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.

Each link-in-bio service has its own endpoint, because their page structures differ: [Linktree](/docs/linktree.md), [lnk.bio](/docs/linkbio.md), [Linkme](/docs/linkme.md), and [Komi](/docs/komi.md). A Pillar URL will not resolve on any of the others.

3\. Read computed fields [#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](/docs/computed-fields.md) for formulas, clamping rules, and null semantics.

Endpoints [#endpoints]

<PlatformEndpoints platform="pillar" />

Notes [#notes]

* `GET` with query parameters
* Authentication via `x-api-key` header
* Responses follow the unified SocialCrawl schema
* A page that does not exist returns `404` and is refunded automatically