# Linktree (/docs/linktree)

Read a Linktree link-in-bio page. Display name, bio, avatar, and every outbound link with its title and destination

Linktree is the largest link-in-bio service, and for most creators its page is the closest thing to a public site map of their business: the shops, the affiliate links, the booking form, and every other social account they list. One endpoint reads the whole page.

Base URL: `/v1/linktree/...`

## Quickstart

### 1. Read the page

```bash title="cURL"
curl "https://www.socialcrawl.dev/v1/linktree/page?url=https://linktr.ee/charlidamelio" \
  -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/tiktok/profile?handle=charlidamelio" \
  -H "x-api-key: YOUR_API_KEY"
```

## Read a page

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

The link list is the valuable part. It is a creator's own declaration of where their audience should go next, which 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.

Two ways that is used in practice. 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

## 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.
- **One page per call, and no discovery.** There is no way to search Linktree pages or list a creator's page from their social handle. 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.
- **Each link-in-bio service has its own endpoint.** [lnk.bio](/docs/linkbio.md), [Linkme](/docs/linkme.md), [Komi](/docs/komi.md) and [Pillar](/docs/pillar.md) are separate paths that return the same shape, so one parser handles all of them. Only the base path changes.
- 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.

## Next steps

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