linktree-api/profile

Linktree API — the link list, in the owner's order

Link in bio: the profile here is the LIST OF LINKS, in the order the owner chose. The first route where items comes back full.

Parameters

Name	What it is
`handle`	The Linktree username.

Handle format and anchor

Handle: username
Anchor: username + id

What this endpoint does not return.

socialLinksLeft out. It is a different object from the link list the owner arranged, and merging the two would change the order the owner chose.

A field we cannot read comes back null, never 0. A zero would be a claim about the account; null is a fact about our collection.

Where this goes wrong.

position is derived from arrival order, never from the platform's own position field. The seven links on comedycentral carry position 1, 28, 33, 34, 35, 41 and 60 — a sparse key, not a rank. Reading it as a rank would report six missing links that were never there.

Cost

1 credit per call. A call that finds nothing costs nothing.

Is position the platform's position field?

No. The platform's field is a sparse key — 1, 28, 33, 34, 35, 41, 60 for seven links. Ours is the arrival order.

Why is this the only route where items is full?

Because on Linktree the list of links is the profile. On the other networks the profile is a set of counters.

← linktree-api