# Pillar (/docs/pillar)

Resolve a pillar.io creator page into its display name, bio, avatar, and every outbound link

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

### 1. Read the page

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

### 2. Follow the links you found

The outbound social links turn one handle into the creator's full account set. Feed each handle into its platform's profile endpoint.

```bash title="cURL"
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](/docs/computed-fields.md) for formulas, clamping rules, and null semantics.

## Read a page

| Endpoint              | Credits | What it returns                                                                      | Key parameters                          |
| --------------------- | ------- | ------------------------------------------------------------------------------------ | --------------------------------------- |
| `GET /v1/pillar/page` | 1       | Display name, bio, avatar, and every link on the page with its title and destination | `url` (the full page URL, the only one) |

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

## Platform notes

- **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.
- 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

- [Prism creator card](/docs/prism.md): One handle to profiles across several networks in a single call.
- [Author schema](/docs/schema/author.md): The unified shape a resolved handle comes back in.
- [Credits](/docs/credits.md): How billing, caching, and refunds work.